Connection Problems after reinstall with Firefox and Smartphone App after switching from 5001 to 443

[fc_sys]

Hello,

first my old thread wich was closed: https://www.3cx.com/community/threa...v18-webmeeting-change-port-5001-to-443.86477/

I made a full backup, uninstalled 3CX on Windows Server 2016, reinstalled with the newest Exe file (then there was an error that my backup is newer as the installation)

There is no new v18 version to download available and in my license portal I don't even have a v18 Download for Windows.. only v16.

So I did basic configuration, updatet the instance and then did a recover.

Then I created a temporary port redirect on windows from 5001 to 443 and 5000 to 80. Provisioned all Sip Phones which have now the correkt http provision link.

A day before I already allowed port 80 and 443 in the firewall rules and set up the dnat rules to the 3cx Server.

Everything is working as expected.. first.

In testing we had issues with the meeting app on iOS and Android, it will stuck on "Authenticating". Then I also found out that Firefox is unable to connect, while Edge and Chrome work fine.

There are websocket errors like this in the dev console after trying to connect:


Now this is a London UK location .. which is fully allowed by our sophos configuration.

Now the funny thing, I go to Conferencing Settings in the 3CX Administartion and switch the Region from Europe to United Kingdom.. THEN it works on the App and on Firefox..

I tried to switch back to Europe.. the error happens again..


Do you have a clue why its not working on Europe Region after switching from https://... :5001 to https: 443 ??

And why is there still a connection to your servers as I host the webmeeting now since v18?

Is it possible that some old configuration or things I can not know are still wrong configured (on port 5001) ? I dont know exactly how the webservers work.. Fun fact #2, when I uninstalled 3CX Server my collegues where still in a working webmeeting, until I installed the new instance, then it shut down.

What is happening in the webmeeting .. ?

 

[NickD_3CX]

Hi!

This looks to be the V16 WM Server still trying to make a connection to your system, because that is how it used to work in V16.
Now of course that you are on V18, this is no longer required.

This also explains why it is contacting you on the 'old' port.

There is not a lot we can do about it now, but on the 30th of March when the V16 servers are turned off, you should see this stop happening:
https://www.3cx.com/blog/news/v16-web-meeting-eol/

As this is the V16 server, it should in no way affect you being able to have and create new meetings.

 

[fc_sys]

Hi!

This looks to be the V16 WM Server still trying to make a connection to your system, because that is how it used to work in V16.
Now of course that you are on V18, this is no longer required.

This also explains why it is contacting you on the 'old' port.

There is not a lot we can do about it now, but on the 30th of March when the V16 servers are turned off, you should see this stop happening:
https://www.3cx.com/blog/news/v16-web-meeting-eol/

As this is the V16 server, it should in no way affect you being able to have and create new meetings.

Ok but we already upgraded to v18 in November 2021. There are still strange connections that I have probably eliminated with the region change?

For what reason is this setting still in the config?


So there is no disadvantage to just leaving this on UK?

Thanks for the quick response.

 

[NickD_3CX]

For what reason is this setting still in the config?

It's not something in your config, it's just the V16 hosted server by us that is trying to reach out to your system and failing.
This though is a server from the old V16 infrastructure that you don't care about any more because you have upgraded to V18.
The V16 infrastructure will be shut down at the end of March, so then you will stop seeing this message.

So there is no disadvantage to just leaving this on UK?

No, you can choose which ever region you want, note though that users you invite to your Meeting will be using MCU servers hosted in the region you choose, so it is usually recommended to choose a region, not necessarily close to where your server is hosted, but where the most of your users that frequently use WM are located.

 

[fc_sys]

It's not something in your config, it's just the V16 hosted server by us that is trying to reach out to your system and failing.
This though is a server from the old V16 infrastructure that you don't care about any more because you have upgraded to V18.
The V16 infrastructure will be shut down at the end of March, so then you will stop seeing this message.


No, you can choose which ever region you want, note though that users you invite to your Meeting will be using MCU servers hosted in the region you choose, so it is usually recommended to choose a region, not necessarily close to where your server is hosted, but where the most of your users that frequently use WM are located.

But Europe doesn't work correctly as I mentioned. The Android and iOS Apps can't connect anymore and Firefox gets an error too.
All our users and customers are located in germany, so it would make sense to use Europe again.

Is it possible that there is some missconfiguration / cache problems on the MCU? I had to made a fresh installation and do the init setup (because of update to 314 to import my backup)

 

[NickD_3CX]

You mentioned that you have a Sophos Firewall I think, are you blocking any specific traffic on it that could be affecting?

If possible, could you create a Test Extension on your 3CX installation and send me the credentials in a PM so that I can access the WebClient?
I can then run a few tests to try and see what is happening.

Leave the region selected to Europe.

 

[fc_sys]

You mentioned that you have a Sophos Firewall I think, are you blocking any specific traffic on it that could be affecting?

If possible, could you create a Test Extension on your 3CX installation and send me the credentials in a PM so that I can access the WebClient?
I can then run a few tests to try and see what is happening.

Leave the region selected to Europe.

Thanks, I scheduled the change at 12:15 for our employees (as running webmeetings disconnecting)

I have indeed some blocking rules on the Sophos FW and I disabled them temporarly on saturday in case its their fault, but it didn't changed anything. (3CX Firewall test is green btw)

I'll send you additional configuration details and your account via PM.

 

[fc_sys]

I have now set Europe as the region. It seems that the MCU connection has healed itself, seems to have been a cache problem indeed.

I'm still running more tests, but the Android app is also working again.
There are still errors in Firefox, but no more weird connection to London.... and no websocket error



If you still want to get a login let me know.

but from IT guy to IT guy... we better not question why it works instead enjoy the moment

 

[NickD_3CX]

but from IT guy to IT guy... we better not question why it works instead enjoy the moment

The computer gods have spoken!