Hi, Alen!
I've tested your blog domain.
This is a really interesting situation.
Your main domain & www subdomain seems like pointing to Hashnode normally.
However, the certificate that has been given by Hashnode is valid only for www.devopsengage.com
Hard to say where you've made a mistake (or it is something from Hashnode side)
I can recommend you to create a special subdomain for Hashnode blog, like blog.devopsengage.com
And create a redirect from your main website devopsengage.com to blog.devopsengage.com (while you don't have any other content)
For example I am redirecting my domain *.theceman.dev to my Github page, and blog.therceman.dev is connected to hashnode
Alen Demirovic
Platform Engineer
Hi i manged to do this, and this is working perfectly fine, but when i want to access my blog without www prefix, i got a ERR_SSL_PROTOCOL_ERROR. I have already installed SSL previously, on my server, and this redirection is not working at this moment. I have also made www.mywebsite.com and mywebsite.com to point to same ip address in my DNS record, so should i just wait some more to be propagated or i made some mistake ? All this stuff was done on AWS Amazon Lighsail instace