gsakola Posted August 3, 2023 Share Posted August 3, 2023 I'm getting below error. I tried to update certificate, then also same error is received How to resolve it? Link to comment Share on other sites More sharing options...
wolstech Posted August 3, 2023 Share Posted August 3, 2023 After you renew/issue the certificate, it can take up to two hours before it starts working. As long as Plesk says you have a valid certificate for the domain, it should take effect the next Apache restart. Link to comment Share on other sites More sharing options...
gsakola Posted August 4, 2023 Author Share Posted August 4, 2023 13 hours ago, wolstech said: After you renew/issue the certificate, it can take up to two hours before it starts working. As long as Plesk says you have a valid certificate for the domain, it should take effect the next Apache restart. I'm still getting this error Link to comment Share on other sites More sharing options...
nox Posted August 4, 2023 Share Posted August 4, 2023 Hello all! Sorry to hijack gsakola's post, but since I'm experiencing the same issue, I figured I'd write here instead of creating a duplicate ticket. The difference is that my certificate is still valid until October 2023 (the dashboard states that my domain is secured) and I didn't change anything in the Plesk settings. Is this something that's maybe linked to the recent server changes and will fix itself over some time? My account is nox (nox.heliohost.org). If I need to create a new ticket, just let me know and I'll do that, sorry if I didn't do the right thing. Link to comment Share on other sites More sharing options...
wolstech Posted August 4, 2023 Share Posted August 4, 2023 (edited) Several people are seeing this it seems. I'm guessing it's related to nginx breaking yesterday...escalating so Krydos can check. Edit: try reinstalling or reissuing it even though it's not expired, then waiting 2 hours. It looks like that may have solved it for a few others. Edited August 4, 2023 by wolstech Try reinstalling first Link to comment Share on other sites More sharing options...
nox Posted August 4, 2023 Share Posted August 4, 2023 Thanks wolsteck, I will do that and report the results here. Link to comment Share on other sites More sharing options...
nox Posted August 4, 2023 Share Posted August 4, 2023 That fixed it wolstech, thanks. 👍 Link to comment Share on other sites More sharing options...
gsakola Posted August 5, 2023 Author Share Posted August 5, 2023 On 8/4/2023 at 7:38 PM, wolstech said: Several people are seeing this it seems. I'm guessing it's related to nginx breaking yesterday...escalating so Krydos can check. Edit: try reinstalling or reissuing it even though it's not expired, then waiting 2 hours. It looks like that may have solved it for a few others. I already did this. Problem is still there Please help Link to comment Share on other sites More sharing options...
nox Posted August 5, 2023 Share Posted August 5, 2023 Hey there gsakola! I checked your domain on my end and both https://gsakola.com and https://www.gsakola.com return as correctly secured. I feel this is a bad cache issue on your end, maybe? Try browsing your website in incognito mode or in a different browser, do you get the same result? Link to comment Share on other sites More sharing options...
wolstech Posted August 5, 2023 Share Posted August 5, 2023 Yep. These domains are working properly for me as well. Please clear your cache. If you still have an issue, please try another browser or a different internet connection (e.g. try on mobile with wifi turned off). Link to comment Share on other sites More sharing options...
gsakola Posted August 7, 2023 Author Share Posted August 7, 2023 Its working now Thanks for help Link to comment Share on other sites More sharing options...
Recommended Posts