I was working on another issue with Sangoma Talk and Sangoma Desk Phones and I changed most of the ports used by FreePBX http(s) services.
After this I encountered another issue with my Sangoma Talk and I decided I had to re-provision my app. I discovered I can’t anymore provision new users. Existing users can still use the app.
Clicking on the link in the email I receive the error Socket Hang up and/or Invalid authentication.
I already tried uninstall/reinstall the app, disable/enable Sangoma Talk, to re-run domain action and stop/restart Cloud Connect agent, restart freepbx, upgrade modules…
Hey @unlikely without seeing logs it’s hard to say what’s going on , may be please raise support ticket and DM me the ticket number so I can check internally.
The issue was caused by a port conflict preventing sangoma connect service to start.
I configured Sangoma Connect on port 8443 but was already used by something else configured elsewhere.
On the LAN, I connect to FreePBX http(s) service through a firewall and a reverse proxy and, from outside, by cloudflare tunnel proxy. Cloudflare tunnels/proxies just allow a couple of fixed ports for https.
I don’t understand if I have to completely wipe my own Cloundflare/firewall/proxy setup and expose FreePBX directly. It doesn’t seems easy/possible to keep as is.