Solved Unable to access webclient via https using non-3cx-acquired FQDN

[giftyDLP]

Hello Forum,

To use our own sub-domain/fqdn for our 3cx server, I added both origin certificate and private key files as requested by 3CX during the installation.
Installation was successful and I can reach the 3cx web client but it always shows or redirects to http instead of https.
I haven't configured anything on the backend or frontend in regards to the license.
Is there something I failed to do?


I get a reply with the IP when I ping my FQDN alright. MyFQDN:443 redirects to http://myfqdn
Port forwarding is just fine on my router and all the necessary ports are enabled on my 3cx server.
I came by an ssl stapling issue and thought that might be contributing. I fixed that but the http issue persists.
Unfortunately this is affecting my extensions' ability to receive calls (I think) because notification permission on my browser can only be set for https (referencing https://www.3cx.com/community/threads/v20-0-new-remote-users-are-showing-as-not-registered.124599/ ).

Kindly assist.

 

[SnakeRiverWebDevelopment]

This might be a browser issue, sometimes the browser will continue the redirect even after the issue has been fixed, try using a Incognito window, and see if that works.

 

[giftyDLP]

This might be a browser issue, sometimes the browser will continue the redirect even after the issue has been fixed, try using a Incognito window, and see if that works.

I tried. still doesn't work.

 

[giftyDLP]

It's resolved now. It wasn't proxied to my issuer.
Thank you so much

This might be a browser issue, sometimes the browser will continue the redirect even after the issue has been fixed, try using a Incognito window, and see if that works.