Unable to Access WebMeeting – Error 50014 (The WMR/Platform is down)

[Eder Coser]

Hello everyone,

I'm currently unable to access 3CX WebMeeting and keep getting the following error:

50014 - The WMR/Platform is down.

I have already checked the steps mentioned in this thread: https://www.3cx.com/community/threads/error-50014-wmr-platform-down.127873/ but none of them resolved the issue.

Has anyone else faced this problem or found a solution? Any help would be greatly appreciated.

Thanks!

 

[Charles_3CX]

Regarding your question, ensure that your system's HTTPS port (TCP 5001) is properly port-forwarded to the 3CX system in question.

 

[Eder Coser]

Regarding your question, ensure that your system's HTTPS port (TCP 5001) is properly port-forwarded to the 3CX system in question.

"I have already checked this, and the HTTPS port (TCP 5001) is properly forwarded to the 3CX system."

 

[Charles_3CX]

We can see that the system's FQDN was a 3cx FQDN and now points to one that uses a custom FQDN. What changes have you made?

 

[Eder Coser]

I made a change to the WEBMEETING_FQDN parameter for testing purposes, but I have already reverted it to the original value.

We can see that the system's FQDN was a 3cx FQDN and now points to one that uses a custom FQDN. What changes have you made?

 

[MarcelloV]

Hello @Eder Coser , please check from your PBX if you can reach this URL:

https://wmr.3cx.net/webmeeting

If you can't reach it, Webmeeting won't work for your PBX.

You can check from command line (both Windows and Linux) with

curl https://wmr.3cx.net/webmeeting

 

[Eder Coser]

Hello @Eder Coser , please check from your PBX if you can reach this URL:

https://wmr.3cx.net/webmeeting

If you can't reach it, Webmeeting won't work for your PBX.

You can check from command line (both Windows and Linux) with

curl https://wmr.3cx.net/webmeeting

Yes, I can reach this URL normally from within the 3CX server. It returns WMR and the instance ID.

 

[MarcelloV]

Yes, I can reach this URL normally from within the 3CX server. It returns WMR and the instance ID.

Looks like you misconfigured some PBX parameters and WMR is now rejecting your PBX authentication. Please send me a PM with you PBX FQDN so I can verify what's wrong.

 

[Eder Coser]

Looks like you misconfigured some PBX parameters and WMR is now rejecting your PBX authentication. Please send me a PM with you PBX FQDN so I can verify what's wrong.

OK

 

[MarcelloV]

Issue is related to the manual change of WEBMEETING_FQDN and WEB_ROOT_EXT_SEC parameters. If these parameters aren't matching your license, WebMeeting feature does not work. You cannot change manually the FQDN associated to your license like this.

If you are in this situation, you have 2 options:
- restore original parameters then restart gateway service
- make a backup of your PBX without including license key and FQDN, release your current FQDN from customer portal, reinstall the PBX with same license and your new custom FQDN, then restore your backup. More details here: https://www.3cx.com/docs/backup-restore-command-line/