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.
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)