3CX Version 20 requires a secure connection to use the Web Client. You are not using an FQDN or HTTPS to connect to 3CX.

[cgmsolutions]

I just created a new version 20 on Azure. Installation went well. VM seem to be running on Azure, but for some reason I can't access the website using the FQDN I created during the install

The domain is in the form: XYZ.3cx.us.

I can get to the site if I don't use https

What am I missing?

 

[OlegR_3CX]

Hi there.
Are you able to access the server by IP?
Can you see if the services on the OS are running?

 

[kjtmp]

Hi Oleg,

I am having the same issue after migrating my windows on-prem via a backup to Linux v20 on-prem.

I followed the V20 Upgrade Checklist & FAQ. I tried system owner with the password I set just prior to backing up my windows on-prem install. And I tried the previous system owner password. Neither is being accepted.

The process was successful as show from the message received.

Congratulations
Your 3CX Installation xxx.3cx.us is ready
Login to 3CX:

Go to: https://falsedomain.3cx.us:5001 or via IP: https://111:5001

Username: [email protected]

Public IP: My public IP

FQDN: falsedomain.3cx.us

License key is: My License key

The web browser says my Let's Encrypt SSL certificate for my FQDN is valid. But it is telling me the password is wrong.

If I try to hit it from the internal IP There is a red banner on the screen that says: 3CX Version 20 requires a secure connection to use the Web Client. You are not using an FQDN or HTTPS to connect to 3CX.

Can someone tell me what is going on. The system owner username and password I am using is correct.

 

[SteveITS]

You need the system owner extension or email, there is no username anymore.

That’s unrelated to the message about HTTPS though. Is the cert valid when you browse Tobit, or maybe try ssllabs’ test?

 

[kjtmp]

Thanks Steve,

Reading another post let me know that I needed to change the password for the web client. After the upgrade the regular web console is not what comes up when you click the link, It's the web client. So I clicked "forgot password" and I reset the web client password as well. I then was able to log in.

Everything restored very well, and all is working well. The admin section of the web client is not as robust as the old console; but I'll adjust. Now on to setting up splitDNS so I can log in from the internal network.