Can't load site in Safari

[A5AA]

Hi everyone. Sorry for my silly question

I set up discourse at the subdomain name www.pila.cc. I use a CNAME record and redirect pila.cc to www.pila.cc. Here are all the records:

I can’t load my site in Safari. The page keeps showing loading. However, it opens in Chrome. After opening the website in Chrome, I can also open it using Safari.

I guess this is a problem with DNS parsing. Is it because I added CNAME records to the naked domain? If so, is there any way to redirect www.pila.cc to pila.cc without the CNAME?

Sorry for my poor expression, because I’m not a native English speaker

[Arkshine]

Hi, welcome!

@A5AA

I use a CNAME record and redirect pila.cc to www.pila.cc

@A5AA

is there any way to redirect www.pila.cc to pila.cc

This is a little confusing on what you really want to do.

If you want to redirect www.pila.cc → pila.cc, I believe it would make sense to do this way:

@     A        8.219.210.255
www   CNAME    pila.cc.

[A5AA]

I’m sorry that I made a typo. I want to redirect pila.cc to www.pila.cc, since the discourse is set up at www.pila.cc, and I hope users can also open the forum when entering pila.cc.

[A5AA]

Still waiting for help

It says: “Safari browser cannot open this page because it is unable to establish a secure connection with the server.”

[jericson (Jon Ericson)]

@A5AA

“Safari browser cannot open this page because it is unable to establish a secure connection with the server.”

I’m not getting this error.

However, I do see an error running this online SSL certificate check:

Certificate name mismatch

I believe that’s because the certificate only covers www.pila.cc.

[A5AA]

Thank you for your reply! How can I add certificate for the naked domain pila.cc?

[jericson (Jon Ericson)]

I think it depends on your SSL certificate provider. For Let’s Encrypt these instructions ought to do the trick:

Set up Let’s Encrypt with multiple domains / redirects

This is to address the problem where you get certificate errors with any redirects or CNAME DNS entries which point to your actual installed Discourse (sub)domain. If you do not have https configured already (you do if you have done a standard install recently) see Setting up Let’s Encrypt as your first step. Add something like the following to your app.yml hooks section (towards the end of the file): after_ssl: - replace: filename: "/etc/runit/1.d/letsencrypt" from: /-d…

[A5AA]

Thank you for the advice!

I am using Let’s Encrypt. I will try to update app.yml late tonight in my timezone.