I keep getting This site can’t be reached after using flexible for SSL

What is the name of the domain?

gdedaizadjemna.ovh

What is the error message?

This site can’t be reachedgdedaizadjemna.ovh refused to connect. Try: Checking the connection Checking the proxy and the firewall ERR_CONNECTION_REFUSED Check your Internet connection Check any cables and reboot any routers, modems, or other network devices you may be using. Allow Brave to access the network in your firewall or antivirus settings. If it is already listed as a program allowed to access the network, try removing it from the list and adding it again. If you use a proxy server… Check your proxy settings or contact your network administrator to make sure the proxy server is working. If you don’t believe you should be using a proxy server: Go to the Brave menu > Settings > Show advanced settings… > Change proxy settings… and make sure your configuration is set to “no proxy” or “direct.”

What is the issue you’re encountering

I cannot access my site with https, i could access it with http untill i enabled forcing https

What steps have you taken to resolve the issue?

I tried adding some dns manually, i tried changing up a bit my nginx conf, but it all did not work…

Screenshot of the error

Are you only getting that error in Brave?

If so, did you follow the directions to allow brave to access?

It works now, but now i get diffrent errors like “Mixed Content: The page at ‘https://www.gdedaizadjemna.ovh/’ was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint ‘http://www.gdedaizadjemna.ovh:8080/authenticate/google/userdetails’. This request has been blocked; the content must be served over HTTPS” and when ig o login with google it gives me 404 error even it worked fine as http

1 Like

Mixed content errors mean that your website is being loaded over HTTPS but some of the resources are being loaded over HTTP. To fix this you will need to edit your source code and change all resources to load over a relative path, or directly over HTTPS.

For example, if you load your images with a full URL:

<img src="http://example.com/image.jpg" />

You would want to change this to:

<img src="//example.com/image.jpg" />

By removing the http:, the browser will use whichever protocol the visitor is already using. An alternative option would be to enable the Automatic HTTPS Rewrites feature that can potentially fix these errors for you automatically. Do be aware that resources loaded by JavaScript or CSS will not be automatically rewritten and mixed content warnings will still appear.

See this Community Tip for further details

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.