Kërkoni te Asistenca

Shmangni karremëzime gjoja asistence. S’do t’ju kërkojmë kurrë të bëni një thirrje apo të dërgoni tekst te një numër telefoni, apo të na jepni të dhëna personale. Ju lutemi, raportoni veprimtari të dyshimtë duke përdorur mundësinë “Raportoni Abuzim”.

Mësoni Më Tepër

Secure Site Not Available Message

  • 3 përgjigje
  • 2 e kanë hasur këtë problem
  • 1 parje
  • Përgjigjja më e re nga cor-el

more options

Why do I routinely receive the "Secure Site Not Available" message even when the site I am trying to log on to is in fact https? (I tried to attached a screen shot example that comes up when trying to go to news.google.com, which is an https site; but the image upload process did not work).

Why do I routinely receive the "Secure Site Not Available" message even when the site I am trying to log on to is in fact https? (I tried to attached a screen shot example that comes up when trying to go to news.google.com, which is an https site; but the image upload process did not work).

Krejt Përgjigjet (3)

more options

You can check the connection settings.

  • Settings -> General -> Network: Connection -> Settings

If you do not need to use a proxy to connect to internet then try to select "No Proxy" if "Use the system proxy settings" or one of the others do not work properly.

See "Firefox connection settings":

more options

I have the same issue. And I checked the network settings and in fact tried all of them and it makes no difference. Also I have no custom proxy.

Selecting 'Continue to HTTP site', takes you to an HTTPS connection. And this issue exists for many many sites; ZDNET, Nokia, etc. - - yet sites like CNET work. BTW there is no issue with Edge on these same sites.

This is quite frustrating, because of this issue you are now forced to consider is Firefox in error (which I believe it is) and due to this, how do I know Firefox is presenting the correct site security information? Firefox is losing credibility due to this issue.

more options

Try to rename the cert9.db file (cert9OLD.db) and remove the previously used cert8.db file in the Firefox profile folder with Firefox closed to remove intermediate certificates and exceptions that Firefox has cached.

If this has helped to solve the problem then you can remove the renamed cert9OLD.db file. Otherwise you can undo the rename and restore cert9.db.

You can use the button on the "Help -> More Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page (Root directory).