Solved IP not URL

[Shane Farmer]

Not sure when this start exactly, but when trying to start a Webmeeting from the Windows client, it's open the webpage using the IP and NOT the URL, so I get a certificate error, because it's expecting the URL. It is connecting to our LOCAL IP. Where would I fix this, or is this correct behavior? I thought it went through 3CX servers.

I did do a restore several months ago due to another issue. Maybe it's been going on since then. If I type the URL in, it doesn't connect to anything else. Not sure what is going on here.

 

[VasilisV_3CX]

Hi @Shane Farmer,

With the upgrade to V18, we moved the WebMeeting Portal to be bundled within your 3CX installation.
We did this for privacy reasons, because now all meeting and participant information is stored on the server you maintain.

This also means though that now, in order for a participant to connect to a meeting you have created, they need to be able to 'talk' to your 3CX.

For external participants joining, you will need to allow access to the HTTPS port you have installed 3CX with (default is 5001) and they will use the FQDN, which is mandatory during the installation process.
For internal participants though, this depends on whether you used an internal FQDN or not during the installation.

You from the sounds of it did not, that is why your local participants get the Local IP, because there is not local FQDN to use.


TL;DR, if you want this error to go away, you need to configure Split DNS, so your FQDN can resolve to the Local IP of the 3CX Server from within your network.

After doing this, I recommend also:

1. Take a Full backup of your 3CX and store somewhere safe
2. Uninstall 3CX
3. Re-install 3CX and restore backup
4. Proceed through the installation normally, but when you get asked in you have an Internal DNS Server, select that you do and fill in the FQDN when asked.
5. Finish the installation

Now your 3CX will also be aware of this, and adjust everything from this point onward and send only the FQDN and you will get rid of the Cert Warning.

 

[Shane Farmer]

Good to know. I didn't notice that change with v18. I'll look into the Split DNS. I have heard of it, but not really dealt with it that I know of. I do have a guy that is helping support us locally and deals with 3CX more, as well. I'll talk to him and see what we can do. Thanks for the help!

 

[VasilisV_3CX]

Sure thing @Shane Farmer, feel free to open a new thread if you require any further assistance or information.