Error SSL after installation

AI-generated summary

User cmdntd encountered SSL and connectivity errors after installing Discourse via Docker on Google Cloud with Plesk, redirecting to port 3000. Initial errors included 502 Bad Gateway and ERR_CONNECTION_REFUSED, with nginx failing to load the certificate due to PEM format issues. Community members gerhard and Stephen noted that non-standard ports like 3000 are unsupported, as Discourse requires standard ports per official docs. neounix pointed to a meta guide on Plesk installation, which helped resolve initial setup. After successful installation, cmdntd reported mixed content issues — SSL appeared active but pages redirected to HTTP, showing “Not secure”. JimPas identified the issue as mixed HTTP resources. neounix suggested enabling “force HTTPS” in site settings, which improved frontend behavior. Despite lingering “not secure” warnings for logged-in users, cmdntd later confirmed HTTPS was working perfectly, possibly due to DNS propagation. neounix advised rebuilding the app and verifying Let’s Encrypt, noting their limited Plesk experience but encouraging continued progress.

I have this error after discourse installation
I install by docker, google cloud, plesk to port 3000

Browser:

On subdomain:

502 Bad Gateway

nginx

On ip with port 3000
ERR_CONNECTION_REFUSED

App root (ssh):
nginx: [emerg] cannot load certificate “/shared/ssl/wiki.cmdgroups.com.cer”: PEM_read_bio_X509_AU
X() failed (SSL: error:0909006C:PEM routines:get_name:no start line:Expecting: TRUSTED CERTIFICAT
E)

That doesn’t sound like you followed the official installation instructions.

I done it, but I change to port 3000
Because I have many port use for others, and I change discourse to port 3000 before map to subdomain

Discourse has to be installed on standard ports. What you’re doing isn’t supported.

See this meta install post for additional clues:

Yes, that’s exactly what I need
Thank you very much

You are welcome @cmdntd

Glad to help you enjoy your weekend.


Do not try and bend the spoon , that’s impossible. Instead, only try to realize the truth… there is no spoon . Then you’ll see that it is not the spoon that bends, it is only yourself. - The Matrix (1999)

Hi, it’s install successful now
But its url is just http. It seems Let’s Engypt done, but not working for https

When I refresh, at first it is https. But it redirect to http at last.
It’s like having SSL, but “Not secure”?

Do you have any idea?

Your icons and images are all http, so you have mixed content. You have to change the http to https.

How could I do for https?
I got Let’s encrypt active but it has this problem

Hey ya go, @cmdntd

Give this setting a try:

Wow, it seems be alright at front
But I see it be “not secure” in logined user. Although, user’s images are alright now

Hey @cmdntd

You may want to consider rebuilding your app and insuring your LetsEncrypt is installed properly.

Frankly, I have never used Plesk and always work directly on the OS like Ubuntu or macOS, so I’m not the best person to help you with Plesk.

Looks like you are making progress; so stay encouraged and you will have it all worked out (working) soon.

I don’t know if my dns has not complete
Today, I loggined and see https is perfect