I know that this question asked before but really I couldn’t find the problem through the answers.
Problem is that users just can login from Chromium to UCP without any problem for XMPP and Webphone. But with Firefox for XMPP, it can’t connect to node server and phone can’t establish connection to server wss…
I have last version of FreePBX 14 and everything is updated.
The certificate has to match a FQDN host name, but that name doesn’t have to exist outside of your network. Let’s Encrypt requires a resolved FQDN, but other signing certs don’t necessarily. You should be able to accomplish this using a self-signed cert or an actual signed cert that you get for your local network host. Verisign (for example) has a section that allows you to download and store private keys on machines that are otherwise sequestered.
We’ve been over this multiple times with you over the last year. My best advice to you is do some research on certificates and ssl. You can do what you want eventually. This isn’t a restriction with freepbx. It’s a browser restriction. No you can’t use self signed certificates unless you trust them on all client machines. Yes you can use internal hosts if you just go out and buy a real certificate for a real domain (or sub domains). Internally at Sangoma we have a wildcard certificate and 30-40 internal hosts. All work over ssl with no issues. But again. You need to go out and do the research and look back on what we’ve said here and in other threads with you.
Thank you. Yes you’re right. I tried last year and now again I’m going to solve it for ever.
Also I searched before to rise a topic here and I can mention to many posts here that are not resolved and I couldn’t get the point.
There are some ticket that you told them remove node or disable UCP, and some others are about let’s certificate with same problem.
Although I asked this question because it is working on Chromium. I though there is a problem in my configuration.