Jump to content


  • Posts

  • Joined

  • Last visited

Posts posted by Chris

  1. Hi,

    Thank you for contacting us. This error indicates that the Pulseway agent can not connect to the Pulseway server or that the system to which it connects is not the Pulseway server.

    Please check the following:

    1) Can you please check if you are using any forward or reverse proxy?
    2). Can you resolve url (instance name) on your system?
    3. Please make sure that port 443 is open on the firewall.
    4. Also make sure that the Pulseways network traffic is not blocked by the UTM.

  2. Hi Mxj280,

    Thanks for contacting Pulseway support. Please send us the screenshot showing the error messages which are related to the Pulseway from the Syslog  and send Syslog from the affected machine.

    cat /var/log/syslog | grep pulseway

  3. Hi George,

    Thanks for contacting Pulseway support. Please send us the screenshot showing the error messages which are related to the Pulseway from the Syslog  and send Syslog from the affected machine.

    cat /var/log/syslog | grep pulseway

  4. Hi Mats123,

    Thanks for contacting Pulseway support. I would suggest reinstalling Pulseway agent, but before that,  you should stop the "PC Monitor Service", delete the same using the below commands ((Please use these commands as the administrator through the elevated terminal to stop and un-register the Pulseway service:))
    net stop "PC Monitor"
    sc delete "PC Monitor"

    And then delete Pulseway folder exists in the C:\Program files\Pulseway and then opens the registry by using Regedit command in the search tab and check whether MMSOFT or Pulseway folder is present under Computer\HKEY_LOCAL_MACHINE\SOFTWARE, if the Pulseway or MMSOFT registry entry is found then please delete the entries, and then reboot the system and install Pulseway.

    Please note-After uninstallation, please use a fresh Pulseway installer, in order to download installer, check this "https://www.pulseway.com/downloads"

  5. Hi Eder,

    Thanks for contacting Pulseway support.Yes, by default all Linux agents are placed in Legacy group. Currently, the Legacy group is used for the systems which are registered using the Cloud API or the REST API. These systems don't use the Token to authenticate with your Pulseway server, therefore these systems are placed into the legacy group.You can rename the legacy group or the system can be moved from one group to another using the Pulseway WebApp ->Systems-> Systems -> Configuration -> select the Organization-Site-Group in which this system is currently located -> Systems and click on edit -> button 'Move Out' -> select the new Organization-Site-Group and save the changes. For more details about this, please check the following:


  6. Hello,

    Thanks for contacting Pulseway support.Unfortunately, this functionality is not supported at this time.However, I will put this forward as the feature request so our developers can consider the possibility to introduce this functionality into the future release.

  7. Hi @BartB,

    Thank you for your suggestion, we will consider the possibility to add this functionality into the future release. As per current designe advanced reporting support only Windows systems and in order to get data from MAC and Linux systems you will need to generate Legacy reports.

  8. Hi @racerx,

    It will take about 1 minute to apply Pulseway group policy on the remote system. After that it will take another minute to trigger notification if your system is not in Maintenance mode (no notifications are sent).

    Regarding offline notifications - for Pro plan these notifications are sent after 15 minutes.

  9. Hi @tolcheen,

    Pulseway can monitor network devices via SNMP from Windows system if this option is supported on the network device.

    For more details on how to configure SNMP monitoring please check out the following link. 

  10. Hi @tolcheen,

    In order to monitor hardware on the same system via SNMP you will need to install SNMP service on your system and then configure Pulseway to monitor these SNMP variables via SNMP.

    For more details on how to configure this please checkout the following link.

    Also, we will check if OpenHardware monitor has an update in which support for these motherboards is added.

  11. Hi @tolcheen,

    In order to configure SNMP you will need to verify the following:

    1. Does that device support SNMP monitoring.

    2. Verify that SNMP is enabled on the interface to which you are connecting.

    3. If are you using SNMP V3, then you need to verify that that user is created on network device and configured so you can access SNMP.

    4. Make sure that port on which SNMP is available is open (usually port 161)

    5. If you have made multiple unsuccessful connections, then it is possible that Pulseway has blocked this connection and in order to clear this blocking you will need to restart Pulseway service on the device from which are you trying to connect.


    Regarding SNMP service - for Windows servers, it is required if you try to config SNMP monitoring on the same device on which Pulseway agent is installed, however if it is remote device, then it is not required.

  • Create New...