3
I own a site that was hosted on firebase, with the option for HTTPS active. One day, I decided to host it in a resale of my own, with a certificate Let’s Encrypt issued for that domain.
In the new devices, there was no strange behavior, but in those who had already accessed the site under https, they notified an ssl error message. When clearing the cache the situation normalizes.
Is there any way to prevent this SSL error? The new hosting is advantageous to me but not with ssl error for old users.
I think that anyone who has already entered the site is accessing HTTP and not HTTPS, there is no protocol and error. I don’t know if I’ve ever tried, but you can try a Redirect 301 or Canonical Tag to forward anyone who logs in through HTTP to HTTPS. If you want I can write a more complete answer.
– hugocsl
So the problem lies exactly in those who have already accessed the site through HTTPS
– Weslley C X Sardinha
Could you tell exactly what error is occurring?
– Humberto Machado
You probably didn’t install the intermediate Cas, so the Let’s certificate is using legacy or cache stuff. Make sure you put the whole chain on the server (your LE site certificate + LE General Intermediary). To configure the complete string, then just reading the HTTP server manual used. Anyway, this does not seem to me a question about programming. As it is of support, it should be made in the [sf] or [su] in English.
– Bacco
This server is using Apache ? Sorry I’m layman with firebase
– Alex
Uses apache. It creates a proxy and points to a server port that runs Node.js
– Weslley C X Sardinha