TLS certificate inconsistency

Support
,
1

I’m having issues with the SSL certificate acting inconsistent on different networks and between refreshes.

Site url: للبيع | منصة بيع الكتروني مصممة خصيصا لك

On one network the site works perfectly, always HTTPS with no issues

On a different network however sometimes the site randomly shows as HTTP only, after a refresh it returns to being HTTPS then some time later the issue repeats.

What I’ve tried so far:

  • Removed custom domain from site and re-added it
  • Renewed SSL cert
  • Completely removed custom domain from Netlify Domains and re-added it
  • Cleared browser cache for both networks

Any assistance would be much appreciated, thanks.

2

Hi @nasser

I’m not experiencing the issues you have described. I’ve tried multiple browsers, refreshed, reloaded, etc.

On another (completely unrelated) note the <html> tag contains lang="en" however I’m fairly certain the site or at least the homepage (but not /en/terms) isn’t in English. lang="ar" is possibly more appropriate.

1 Like
3

Nice catch, I’ll update the lang attribute.

That’s the issue, it’s hard to reproduce but it does sometimes revert to being HTTP only, sometimes on the www. version and sometimes on the bare domain.

4

By default when SSL is enabled on a site, http:// automatically redirects to https://. I’ve never seen any Netlify site load with http://.

If you observe this behaviour again, could you get the nf-request-id (see [Support Guide] Netlify Support asked for the 'x-nf-request-id' header? What is it and how do I find it?) so the support team can look into it further.

5

Hi, @nasser. If possible a HAR recording of the issue would will us more about what is happening.

If a HAR recording isn’t possible, we need to be able to track the HTTP response with this issue. The fastest way to do this is to send us the x-nf-request-id header which we send with every HTTP response.

There more information about this header here:

If that header isn’t available for any reason, please send the information it replaces (or as many of these details as possible). Those details are:

  • the complete URL requested
  • the IP address for the system making the request
  • the IP address for the CDN node that responded
  • the day and time of the request (with the timezone the time is in)