WARNING: Port 443 of computer does not appear to be accessible, but web page is ok

[dalu]

@ghassan

I think you have multiple option how to handle such deployament, because typically wordpress come shipped with its own proxy server, as well as discourse. So your option could be:

sorry for late reply, i was off the grid and forums for a while, feels good, but i tried to fix email problems before i left, but i still got error 502 while acessing the forum.

sorry I explained wrongly, i don’t need worpress on same server, it was just to take an example of what you couldn’t do.
In fact I just have 4 domains that points to simple web site on this server.
the discourse doctor doesn’t seem to have errors
but i still get error 502 on the forum domain
do i need to instal haProxy like they say here? Thanks

How to set up Discourse on a server with existing Apache sites

It’s not as daunting as it sounds! While this may sound a bit intimidating at first, it’s really not all that bad. You basically need to do two things: Install HAProxy (or an alternative) which will take over port 80 and then divert your Discourse traffic to your docker container, and all your other sites to your usual Apache set-up. Let Apache know which port to listen for. While this is only a rough guide, it should do a good job of pointing you in the right direction. Let’s get star…