ERROR 525 SSL handshake failed

hi thanks for replying , now i got the ssl from the panel and have enabled the full strict mode in cloudflare but still the website shows error 525
Edit : i had to install it in the vpanel also, that was the step i was missing ! now everything works fine .

hi there me again,
after getting the new ssl the previous made folders are loaded in ssl green lock but the new ones are saying "connection not secure : some parts like images are not secured " while i have literally nothing on the index.html page but it is still saying i have untrusted source links !!
i tried switching from full strict to full ssl mode in cloudflare but that didn’t work !!

You need to change the resources URL on your files to have HTTPS URLs.

That error means that some of the links to images, scripts and/or stylesheets on your page do not use secure URLs. This could be URLs to your own website or to other websites.

If you open your browser’s developer tools menu and check the Console, you’ll usually see warnings or errors there indicating which URLs are not secure. If you can change those URLs to also use HTTPS, that should give your website a green lock.

2 Likes

thanks for replying, i have forced https through .htaccess but i see this error in my firefox console [see attached image] , it says that i have attached my 404 error link but that is not true i don’t get it i have only one h1 heading on the page nothing else no image no js no css ?

Because it means the file you’ve attached doesn’t exist and it returns your 404 file. (seems to be a caching issue)

Looking at your files. They’re forced by http and not https. Have you tried to change it?

I do not see why urls should be censored. Letting us to visit them will help us to understand the actual problem easily :slight_smile:

2 Likes

i have literally nothing except h1 heading and all the error redirect pages are already forced https i checked them. this is the [link was removed as issue was resolved]
edit – and i custom purged everything from cloudflare so i don’t think it to be caching(maybe)

I can see error page also forced to https. Some browsers have ssl caching sorage, So that’s possible that problem is due this if you do not see the error page is forced to https:

2 Likes

For me it has a valid SSL & no error at all.

1 Like

sorry for late reply (i had exams), and a big thanks it was a great advice now everything works fine .thank you.

1 Like

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