Blocked port 443

drewt

Bronze Partner
Advanced Certified
Joined
Jul 18, 2011
Messages
129
Reaction score
27
Hi, I have an issue with port 443 access from pbxmonitor.net. I have:

Version 20.0 Update 8 (Build 1109 Release) 4 sim pro
Amazon light sail hosted
I have country code restrictions set to north america.
I have console restrictions enabled.
I have my monitoring service’s web site whitelisted in the firewall and console restrictions.
My audit logs do not show unknown ip connections
Anti hacking enabled with Automatic global ip blacklist enabled.
System is fully functional, 2 trunks to skyetel and vitelity.
Console access no problem.

My monitoring service’s web site, pbxmonitor.net can not connect to my instance and generates this error message. TCP Connection Failed, Management Console Port Incorrect, Port Not Open, or we are blocked by a Firewall!

In my system health_report.txt I can see my office ip connected to port 443, can anyone suggest where to look to see what may be blocking the pbxmonitor.net access to my port 443? I have verified the admin password is correct as entered at pbxmonitor.net. I have about 20 other instances being monitored at pbxmonitor.net and they have no issues. For some reason I can not select the system in the drop down box at the bottom of this thread posting interface so I have selected a similar system. Thanks in advance for any help.
 
Any chance the monitoring service's IP is blocked on the Amazon level? Any chance they use multiple IPs, perhaps geo dependant and this machine is getting a request form a different, not whitelisted one?
 
I accessed my Lightsail control panel and I can confirm that my Lightsail instance has HTTPS TCP 443 set to "Any IPv4 address".
 
I have a firewall checker at pbxmonitor.net. These are the results I get when I test my instances IP from pbxmonitor.net. I set logs to verbose and run the firwall test and I can see the pbxmonitor.net IP in my logs, when I run a connection test from my pbxmonitor control panel the pbxmonitor IP does not appear.

3CX Port Test Results
If ping fails the MTU Test will also fail!

80 | CLOSEDNginX Webserver (Legacy)
443 | OPENNginx Webserver SSL
5060 | OPEN3CX PBX SIP Protocol
5061 | OPEN3CX PBX SIP TLS (Optional)
5090 | OPEN3CX Tunnel Protocol
4516 | CLOSED3CX Wallboard (Optional)


MTU Detection Test
Test requires ICMP(ping) to be enabled on Remote Gateway. Test will send packets with DF bit set
starting at 1500 size and dropping by 1 untill the remote system answers back.


Packet sizeHeaderActual MTU & Result
147228 bitWAN MTU of 1500 failed!
147128 bitWAN MTU of 1499 failed!
147028 bitWAN MTU of 1498 failed!
146928 bitWAN MTU of 1497 failed!
146828 bitWAN MTU of 1496 failed!
146728 bitWAN MTU of 1495 failed!
146628 bitWAN MTU of 1494 failed!
146528 bitWAN MTU of 1493 failed!
146428 bitWAN MTU of 1492 failed!
146228 bitWAN MTU of 1491 failed!
146128 bitWAN MTU of 1490 failed!
146028 bitWAN MTU of 1489 failed!





Anyone looking for remote monitoring check it pbxmonitor.net, excellent value and functionality.
 
Last edited:
You'd be better off contacting support @ pbxmonitor.net for troubleshooting this one IMO.
 
Issue was credentials, fixed with help from pbxmonitor.com Great service, I highly recommend them.
 

Latest Posts

Forum statistics

Threads
112,283
Messages
591,681
Members
165,403
Latest member
saw-nick