Exit with STRG+X and type Y then press enter to save the file.
Launch the setup.
./discourse-setup
Now answer some questions.
Hostname for your Discourse? [discourse.example.com]:forum.domain.tld Email address for admin account(s)? [me@example.com,you@example.com]:mail@domain.tld SMTP server address? [smtp.example.com]:Plesk(Yeah write Plesk in the line) SMTP port? [587]: 25(The Port from the Mailserver in Plesk is 25) SMTP user name? [user@example.com]:mail@domain.tld SMTP password? [pa$$word]:password123 Let's Encrypt account email? (ENTER to skip) [me@example.com]:(to skip this press enter)
It takes a while, wait until you get back to the command line. The Docker container fails to start. It doesn’t matter. Now we change the app.yml to work with Plesk.
I now use Plesk Obsidian on Ubuntu 20 and the only setting I need to tweak to allow Discourse to work along other web applications is to add a proxy rule that redirects the port 80 to another (8060 in my case) - and of course, the redirections as well of the port 8060 → 80 and 9443 → 443 in app.yml.
Also, the SSL certificate is automatically renewed without any additional action.
It’s way simpler than before.
Those lines tell discourse to ignore your proxy servers address and report the address of the actual computer making the request.
The let’s encrypt issue, is because you need not to pass that request to discourse but to the let’s encrypt client that the reverse proxy is running. You could probably add some stuff to tell it to handle that /well-known request itself. Perhaps you’re friends W can help figure that out
Unfortunately I’m not receiving the email to activate.
When I use all email settings on Outlook it’s functional but when I use the same settings I don’t receive anything.
I did exactly what you wrote but there aren’t even mail data in logs.
