Problem with ssl certificates for root domains.

[rmalheiro]

I'm having an issue with SSL certificates for my domains that I can't seem to understand. When I type| https://longb.com.br |, the correct certificate opens normally. However, when I type | https://longb.com.br. | with a period at the end of the domain, the server's certificate loads instead of the domain's certificate. Although this might seem okay, it prevents some requests to my domain. Has anyone encountered this before? I've searched everywhere, but I don't know what else to do. If anyone can help, I would appreciate it. Thank you.

 

[johannes]

For me the domainname with dot at the end doesnt load any certificate, it simple shows the standard message "
Your connection is not secure. The owner of longb.com.br. has configured their website improperly. (...)"

And why the heck would you put a dot at the end? Or is this maybe a new kind of linkspamming in this board?

 

[Richard G]

it prevents some requests to my domain

No not really, because domains do not end with a dot. Which is why the SSL certificate can't work.

Even without the dot at the end you have a certificate issue and it doesn't open as should be.

 

[rmalheiro]

Hello @johannes

Thank you for your response, but wouldn't it be a kind of spam I started to notice that after I began using DirectAdmin for my domains, I started having problems with Google PageSpeed Insights. When I contacted their support, they said that loading the domain with a "." at the end was causing an SSL error, hence the failure in PageSpeed Insights. In my tests here, I'm also getting errors when I simulate. However, on another host with a different solution, the error does not occur.

Thank you very much for your help.

 

[rmalheiro]

Hey @Richard G , yeah, I understand that it shouldn't be like that. However, when testing Google PageSpeed Insights, sometimes it works and sometimes it doesn't for my domain. When I contacted their support, they informed me about the "." at the end. What intrigues me is that I have other domains on another server, and when I simulate with the "." at the end, they redirect to the correct page. But with DirectAdmin, it calls the host's certificate instead of the virtual host's.

 

[Richard G]

However, on another host with a different solution, the error does not occur.

That's nonsense you're talking here. There is no certificate with a dot at the end. I also checked with cPanel sites and same error occurs.
Domains are just not used with a dot at the end.

Problem you are having is that your main domain SSL, so without the dot is having issues.

 

[Richard G]

and when I simulate with the "." at the end, they redirect to the correct page.

That is only done if you have a certain redirect active, not by default.

 

[rmalheiro]

Okay @Richard G , I'll delve deeper into why this might be happening. Thank you very much for your help.

 

[Richard G]

You're welcome. Fix your main domain first.
If that is working correctly, then you can make a redirect via .htaccess so when a dot is used after the domain name, the redirect will take the visitor to the main domain.