hi all
I am also getting the error even after using the reolution provided by @surajshetty.
After some research I have found, I used “https” where I had only an “http”. Hope this lesson learned the hard way will help someone else.
You’re right, the issue is related to using HTTPS on a custom domain like .dev. The .dev TLD is now owned by Google and enforces HTTPS via HSTS in modern browsers like Chrome. That’s why trying to access https://meeting.dev:8000 causes a Secure Connection Failed or ERR_SSL_PROTOCOL_ERROR even if you didn’t configure HTTPS.
To fix it, change the domain to something like meeting. local or meeting. test, and access your app via HTTP instead, like http://meeting.local:8000. No need to install SSL for local development unless required. Glad it worked in Firefox after the change! It arises when Firefox cannot establish a secure connection with a website. This error is also known as this site can’t provide a secure connection, typically caused by an issue with the website’s SSL certificate or a mismatch in encryption algorithms and protocols. There are different ways to fix the error; you need to understand them properly in detail. Hope it helps!