ofir Posted March 25, 2014 Share Posted March 25, 2014 I setup port monitoring on port 443 localhost and I get a red blob. Â Web monitoring works on same. Link to comment Share on other sites More sharing options...
Staff Mark Posted March 25, 2014 Staff Share Posted March 25, 2014 Hi, Thanks for reporting! Is the error persistent (you get the error all the time) ? What service is running on 443? I'll try to match your environment to replicate the issue. Regards, Mark Mark and ofir 2 Link to comment Share on other sites More sharing options...
ofir Posted March 27, 2014 Author Share Posted March 27, 2014 I setup port monitors on Mac for port 443 (web server) and ports 4280 (CrashPlan).  https://www.dropbox.com/s/ogn71zdbyqnjiz4/Screen%20Shot%202014-03-26%20at%2023.58.38.PNG Link to comment Share on other sites More sharing options...
Staff Mark Posted March 27, 2014 Staff Share Posted March 27, 2014 So, you have web server running on 443 and you setup port monitor and web monitoring to monitor port 443. Web monitoring working and port monitor not. It's that correct? Â Mark Link to comment Share on other sites More sharing options...
ofir Posted March 27, 2014 Author Share Posted March 27, 2014 So, you have web server running on 443 and you setup port monitor and web monitoring to monitor port 443. Web monitoring working and port monitor not. It's that correct? Â Mark Exactly. Link to comment Share on other sites More sharing options...
ofir Posted April 13, 2014 Author Share Posted April 13, 2014 So, you have web server running on 443 and you setup port monitor and web monitoring to monitor port 443. Web monitoring working and port monitor not. It's that correct?  Mark  Any news on that? Link to comment Share on other sites More sharing options...
Staff Mark Posted April 14, 2014 Staff Share Posted April 14, 2014 Any news on that?  Hi,  I replicate same env with apache running on 443 and port monitor and web monitor set up and I have no issues. Can you, please, try this: 1. close PCMonitor ('Hide' option from context menu)2. open Terminal and type: sudo launchctl remove com.mobilepcmonitor.PCMonitorHelper3. open Console and clear it4. open PCMonitor agent. 6. copy and send Console output (check as well if any PCMonitor .crash file under Diagnosis and Usage Information) to support@pulseway.com.  Thanks!  Mark Link to comment Share on other sites More sharing options...
ofir Posted April 14, 2014 Author Share Posted April 14, 2014 Sorry about the duplication: OK, here's the log: https://www.dropbox....98uu/system.log  This is happening on all the systems I tried. Link to comment Share on other sites More sharing options...
Staff Mark Posted April 15, 2014 Staff Share Posted April 15, 2014 Hi,  According to your log looks like you have some local issues:  servermgrd[70165]: Got error -9805 for SSLHandshake  remote address is 127.0.0.1:44765 Server[39262]: NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9812) servermgrd[70165]: Exception in SessionController threadListen: Socket: Connect failed com.mobilepcmonitor.PCMonitorHelper[8566]: NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9812) PCMonitorHelper[8566]: --> port:443 on hostname:localhost is closed  pcmonitor throw same kCFStreamErrorDomainSSL error like servermgrd(ServerAdmin) and Server processes. Port monitor corectly response back with "close" port status.  Can you, please send us screenshots (from mobile device) with port monitor and web site monitor ?  Regards, Mark Link to comment Share on other sites More sharing options...
ofir Posted April 15, 2014 Author Share Posted April 15, 2014  Hi,  According to your log looks like you have some local issues:  servermgrd[70165]: Got error -9805 for SSLHandshake  remote address is 127.0.0.1:44765 Server[39262]: NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9812) servermgrd[70165]: Exception in SessionController threadListen: Socket: Connect failed com.mobilepcmonitor.PCMonitorHelper[8566]: NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9812) PCMonitorHelper[8566]: --> port:443 on hostname:localhost is closed  pcmonitor throw same kCFStreamErrorDomainSSL error like servermgrd(ServerAdmin) and Server processes. Port monitor corectly response back with "close" port status.  Can you, please send us screenshots (from mobile device) with port monitor and web site monitor ?  Regards, Mark   No local issues, the server works fine. It uses a self generated SSL certificate, but the same test on a 'proper' SSL certificate also fails.  https://www.dropbox.com/s/xo54ev2qio1azx0/IMG_4312.PNG https://www.dropbox.com/s/uc7g7c5sz3wajqg/IMG_4311.PNG  You also see that the 2nd web test fails in a different way. By the way, the reason it's localhost in one and odmaster.iefiles.co.uk in the other is because I tried both options. The results were the same. Link to comment Share on other sites More sharing options...
Staff Mark Posted April 16, 2014 Staff Share Posted April 16, 2014 That's strange. Â Just to rule out any local issues: Â - Kill the web server on 443 - Make it listen on port 80 - Start the web server again - Check the logs and make sure there are no issues - Do a telnet localhost 80 to be sure that the port is open - Change pcmonitor to monitor port 80 - Check if port is correctly displayed as open. - Change pcmonitor to monitor website on localhost port 80 - Check if webpage response is 200 - If everything ok change the web server to port 443 and repeat these steps. Â Regards, Mark Link to comment Share on other sites More sharing options...
ofir Posted April 23, 2014 Author Share Posted April 23, 2014 That's strange.  Just to rule out any local issues:  - Kill the web server on 443 - Make it listen on port 80 - Start the web server again - Check the logs and make sure there are no issues - Do a telnet localhost 80 to be sure that the port is open - Change pcmonitor to monitor port 80 - Check if port is correctly displayed as open. - Change pcmonitor to monitor website on localhost port 80 - Check if webpage response is 200 - If everything ok change the web server to port 443 and repeat these steps.  Regards, Mark  I've done all that - on 3 Macs - still doesn't work and now my demo has run out. The web servers I tried all work perfectly and respond to other monitoring software. This looks like a bug. I also haven't had any response regarding the Mac update. As it stands the Mac version is seriously lacking in features and in my case, doesn't really work.  Not sure how to proceed now, I was pretty excited a month  ago… Link to comment Share on other sites More sharing options...
Administrators Marius Posted April 23, 2014 Administrators Share Posted April 23, 2014 Could you please upgrade to version 4.3 released on the 22nd of April? Please uninstall the current agent, download the latest Mac agent and test again. Let us know if it works.  Thank you. Link to comment Share on other sites More sharing options...
ofir Posted April 23, 2014 Author Share Posted April 23, 2014 I would but my demo ran out. I complained about this problem a month ago. Link to comment Share on other sites More sharing options...
Administrators Marius Posted April 24, 2014 Administrators Share Posted April 24, 2014 You can still use it for up to 5 systems. Please email us with your account username and we will be happy to extend the trial. Link to comment Share on other sites More sharing options...
ofir Posted April 24, 2014 Author Share Posted April 24, 2014 You can still use it for up to 5 systems. Please email us with your account username and we will be happy to extend the trial. Â Thanks for extending trial. I'm afraid I'm getting the same results. Port scan says port is down, but web scan says web site is up. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now