403 Forbidden Nginx Feedback After Update

[giftyDLP]

I'm unable to reach two of our servers after a 3CX update.
We get a 403 Forbidden Nginx error every time I try to access either sites.
All 3CX services are running fine.
I've rebooted the server and restarted 3CX a few times. Same situation.

Only unusual thing I noticed is that the issuer and other details in the certificate details had changed.
The certificate file is as should be and referencing form 3cpbx site-enabled hasn't changed.

 

[NicholasP_3CX]

Can you browse to these sites from your phone or computer when connected OUTSIDE of your office network (5G hotspot for example). The certificate details being changed may be your firewll intercepting and putting its own certificate.

 

[giftyDLP]

Can you browse to these sites from your phone or computer when connected OUTSIDE of your office network (5G hotspot for example). The certificate details being changed may be your firewll intercepting and putting its own certificate.

Browse to the 3cx sites outside office network, no, I can't.
will crosscheck again with my firewall

 

[giftyDLP]

At my wits end. I've gone as far as disabling my firewall. Encountering same.

 

[giftyDLP]

Can you browse to these sites from your phone or computer when connected OUTSIDE of your office network (5G hotspot for example). The certificate details being changed may be your firewll intercepting and putting its own certificate.

Do you mind taking a look at it on my behalf?

 

[NicholasP_3CX]

We cannot do the troubleshooting of your network.

Disabling your firewall doesnt necessarily make things better though. You would need to do the port forwarding, AND open up the access control.

You need to know what youre doing on your firewall. Or use 3CX hosted which doesnt require you to do any firewall configuration.

You can find more information on the firewall configuration at https://www.3cx.com/docs/manual/firewall-router-configuration/

FYI, the FQDN that begins with spring is accessible but the one that begins with star is not.

 

[giftyDLP]

We cannot do the troubleshooting of your network.

Disabling your firewall doesnt necessarily make things better though. You would need to do the port forwarding, AND open up the access control.

You need to know what youre doing on your firewall. Or use 3CX hosted which doesnt require you to do any firewall configuration.

You can find more information on the firewall configuration at https://www.3cx.com/docs/manual/firewall-router-configuration/

FYI, the FQDN that begins with spring is accessible but the one that begins with star is not.

Well noted.
3CX Hosted is not available in my region
Star*** is deliberately off.

The issue is happening on both NFR instances
Thanks, will take a look