Marius

Glad to hear that it worked - usually a Pulseway service restart should sort it out.

It must be the proxy. The Pulseway agent does not connect to any other servers whatsoever. Install Pulseway on a different computer that does not use any proxy to check this out.

You're very welcome! Thanks again for the suggestion.

Thank you for the suggestion - we will add this feature in a future release.

Use TCP View to view the connections: https://technet.microsoft.com/en-us/library/bb897437.aspx Direct Download: http://download.sysinternals.com/files/TCPView.zip

The only connection that belongs to PCMonitorSrv.exe is this one: TCP 192.168.1.100:61897 ip-69.65.49.8.servernap.net:https ESTABLISHED Pulseway can establish other connections only if you have some ping checks or web site checks defined in the Pulseway Manager.

Hi Rasmus, No news just yet, we are still working on it. We will release an update with the fix once ready. Thanks. Marius

Hi, Thank you, we'll consider it for a future release, no ETA at this time. Marius

Hi Remko, You can use the Pulseway Manager app -> Manage Devices to define access policies for each device. In this way you can block the access on certain systems from specific mobile devices. With an Enterprise Server, this can also be done by creating user accounts and grant access to only certain systems that are monitored using a system account - this can be done using the Associated Accounts feature. You can find more info about these two methods in this blog: http://www.pulseway.com/blog/configuring-mobile-device-access-policies-and-user-accounts Hope this helps. Best Regards, Marius

It hasn't been added to non-Enterprise Server version yet.

No plans for Mac either but we are working on a Web Dashboard.

We've received your email - thanks! We have resolved the issue and the fix will be available in the next release. Thanks again! Marius

Thank you Rasmus, Can you please send the same image to our support email address? We will work with you to better understand the context of the issue and to fix it. Thanks again. Marius

We don't have an ETA just yet, should be Q2 15.

We are considering adding this in a future release, it is not in place yet.

Michael, We have sent you an email exactly 2 days ago in reply to your email. Not sure why you haven't got it - please check your spam folder. Date: Tue, 10 Feb 2015 19:57:59 +0000: "Hi Michael, Thank you for contacting Pulseway support. Before you migrate the server you need to prepare the new server ... ... ... new server or simply swap the IP addresses between the two servers. Let us know if we can help you with the process."

We will consider it, thank you! Regards, Marius

Please email our support with your account username, we will help with this. Thanks

Hi, Please email our support with the error details and we will help you fix the issue. Thanks! Marius

Hi! This has been fixed and an update will be release shortly. Marius

Try opening https://myservername/server.svc in a web browser from that computer, what is the result?

No news yet. This is on our list but not as a high priority. It is not something we are consider critical and we will start the implementation at a later stage.

Hi, You can get a subscription here: http://www.pulseway.com/account/payment Marius

You can configure the "Do Not Disturb" feature on iOS to avoid the 3am notifications. The push notifications are sent by the Pulseway servers that might not know the device timezone.

Hello, Please read this, it will help you resolve the 2003 problem: http://forum.pulseway.com/topic/1250-windows-server-2003-could-not-establish-trust-relationship-for-the-ssltls-secure-channel-with-authority-error/