Solved 3CX URL doesn't seem to work anymore?

[brianoakes]

In the past few weeks we noticed the URL for 3CX doesn't seem to work internal or external, but only on the console of the server.

URLs is the https://xxxxxx.3cx.us:5001/ - I added the x's for security.

We are running 15.5.15502.6.

The error from another server on the LAN using Chrome was Connection Refused

Any idea what to check?

 

[YiannisH_3CX]

Hello @brianoakes

Please make sure that your maintenance is active and that port 5001 is open on the firewall and correctly forwarded. Also try an nslookup and see if the FQDN resolves to the correct IP. You could also check your costumer portal and see if the FQDN is bound to the licence key.

 

[Sand]

Same issue here...

We just had a power out-take and after the power was restored, we cannot get access to our 3CX webpanel internally or externally on our network using the https://xxxxxxx.3cx.xx:5001 address, and not using the local IP either like: https://123.123.123.123:5001. I've tried locally on the server or from another machine on the network.

Nothing network-wise has changed since before.

 

[Sand]

Just to add:
And the services are running when checking the task manager in Windows.

 

[YiannisH_3CX]

@Sand

From the PBX machine try using http://127.0.0.1:5004 and see if that works.

 

[brianoakes]

Hello @brianoakes

Please make sure that your maintenance is active and that port 5001 is open on the firewall and correctly forwarded. Also try an nslookup and see if the FQDN resolves to the correct IP. You could also check your costumer portal and see if the FQDN is bound to the licence key.

Our Maintenance expires on 10/30/2018 according to the portal.

Nslookup does show the correct ip address

Name: xxxxxx.3cx.us
Address: 173.6x.2xx.xx

Firewall (Sonicwall) is configured to forward the 5000 and 5001 (and all the others). 5001 I get connection refused. 5000 I get a 403 Forbidden error. Server is nginx/1.12.1.

 

[Sand]

@Sand

From the PBX machine try using http://127.0.0.1:5004 and see if that works.

I've now tried this, and this works...

But I still cannot access it using the FQDN or the IP of the machine. I cannot see why. I've checked firewall settings on the machine and the router.

 

[YiannisH_3CX]

Firewall (Sonicwall) is configured to forward the 5000 and 5001 (and all the others). 5001 I get connection refused. 5000 I get a 403 Forbidden error. Server is nginx/1.12.1.

Check if the nginx and the management console service is running on the machine and try again.

 

[YiannisH_3CX]

I've now tried this, and this works...

But I still cannot access it using the FQDN or the IP of the machine. I cannot see why. I've checked firewall settings on the machine and the router.

Make sure that nothing has changed and that everything is working normally. Is the local IP of the machine the same? Do the phones register normally? Try restarting the server also to see if that helps.

 

[Sand]

For some reason the NGINX server didn't start. By starting it manually from the Windows Services panel, solved the problem...

 

[Sand]

Make sure that nothing has changed and that everything is working normally. Is the local IP of the machine the same? Do the phones register normally? Try restarting the server also to see if that helps.

By the way, I ran the firewall test from the dashboard in the bottom of the PBX Status pane, and it was reported that ports 10000-10999 failed. Are they necessary? We only use the VoIP functionality for calls, and not the webmeeting or video conferencing - at the moment.

 

[Sand]

Or rather it is the test of ports 10600-10998 that fails the full cone test.

 

[YiannisH_3CX]

You need to open the entire range of ports to avoid having audio issues. The PBX will try to use them as the ports are available to it so when it reaches those ports if they are not open on the firewall you will have one way audio.

 

[YiannisH_3CX]

For some reason the NGINX server didn't start. By starting it manually from the Windows Services panel, solved the problem...

Glad to see the issue has been resolved.

 

[brianoakes]

Glad to see the issue has been resolved.

I orignally posted the question. I'm not fixed. My Nginx service is running. I have rebooted, and I still get the same issue. Any other suggestions?

 

[YiannisH_3CX]

Can you access the management console directly from the machine using the local IP and the FQDN?

 

[brianoakes]

Good Morning, as I typed up the response I went ahead and looked at the config any my notes. Long story short... problem found on my end. Thanks for the follow up, you can close out the thread!!!

 

[YiannisH_3CX]

Glad to see the issue has been resolved.