אזהרה: יציאה 443 של המחשב אינה נראית נגישה באמצעות שם מארח

Hey @Murto

FWIW, I find Discourse, as a back end Rails application, is much easier to set up if you configure Rails to use a unix domain socket versus a TCP/IP port; and set up the Discourse application behind a reverse proxy.

In that way, the TCP/IP ports are exposed via the reverse proxy only, and the Discourse application (and the container) is exposed via a unix domain socket; and you can run as many Discourse container instances you might want and not have to worry about conflicting TCP/IP sockets. In my view, this is a very clean way to run Discourse.

There are plenty of HOWTOs and tutorials on this site to guide you to set this up, if you get stuck and want to shift directions a bit. There is a “socket” template in the Discourse distribution you can use to set up the “Discourse part of the configuration”; and then you just set up the reverse proxy (countless tutorials on how to do that) and “away you go!”.

HTH.