Solved 3CX V18 + Windows Desktop App V18.5.28 not provisioning

Status
Not open for further replies.

Andreas Ebinger

Trainee Partner
Basic Certified
Joined
Feb 6, 2020
Messages
18
Reaction score
3
Hi,
we upgraded our 3CX (Debian Based) to the latest V18 Build 237. When I try to install the new Desktop App everything seems to work fine (its installed and you can find it in the start menu and the tray Icon), but if I try to provision it nothing happens: no error just nothing:
- It makes no difference if the App is running while I Press the Provisioning Button in the Webclient
- Tried to lower the Security Settings in the WebBrowser
- Checked the Settings of Default Apps for the TCX+APP (is set to the Desktop App - as is TEL)
- Tried different App Versions .28 and .26
- nothing out of the ordenary in the windows event logs (as far as I can tell)
- tried the install as admin and tried the install for all users
- tried it with a pc which is not a domain member

The Desktops are all inside the domain-network and their firewalls are disabled. Only Security Software running is windows Defender.

Please help: is there a way to manually configure the desktop app oder how can we continue to troubleshoot the problem?
 
The Problem is solved: It had nothing to do with the Proxy at all. We have a special config of the Nginx-Webserver because we need it to use more than one SSL-Certificate. We have a setup similar to that one: see Multiple Internet gateways https://www.3cx.com/blog/docs/network-configurations-supported-3cx-phone-system/.
Because of that setup we need the webserver to react to hostname.internaldomain.com with an internal certificate from the local CA and to hostname.3cx.de with the certificate from 3cx. To achive this you have to dublicate the "server" part from nginx.conf and customize it for each case.
When we updated the 3cx I asumed that there where no big changes in the nginx.conf and just reused the one from v16. That was the mistake. After customizing the new nginx.conf analog to the old one provisioning of the desktop app works like a charm again.
 
This case is solved.
 
Status
Not open for further replies.