6
cannot open port 443 (lemmy.one)
submitted 3 years ago by to c/selfhosted@lemmy.world
25 comments fedilink hide all child comments
 

Hi. I want to start selfhosting my data. I already have a jellyfin server running. I'd like to add a nextcloud instance. The setup of nextcloud says I should open up port 443 for using my own domain. Sadly I am not able to open up this port properly. It is open however when I visit jellyfin.mydomaim.com it is rerouted to the config of my router. To circumvent this problem I have set up a reverse proxy that accepts port 8443 instead of 443. For my jellyfin this seems to work. I can visit it with jellyfin.my domain.com:8443. I don't know how I can get this to work for nextcloud as it only accepts 443. Any advice on my setup is welcome! BTW I am running Debian on an old PC.
Thanks in advance for the help!

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 3 years ago* (1 child)

There seems to be a bit of a misunderstanding of what a reverse proxy does.

The proxy should accept requests on port 80 and 443 and on the basis of the requested website route you to the correct adress:

  1. Request for jellyfin.mydomain.com comes in
  2. Reverse proxy checks where it should reroute it -> host.of.jellyfin:8443

So your client thinks its talking to your jellyfin-instance over port 443 but in actuality your proxy reroutes the traffic to wherever your jellyfin needs it to arrive..

/Edit: Ah just saw that it redirects 443 requests to your router. Can you configure a DNS override on its config somewhere?

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
  • [–] [S] 1 point 3 years ago

    I get a 302 "temporary redirect" response, I do not know why my router does this. I'll check its config again. I have added a port mapping so that external 443 is mapped to my internal server 443

  • permalink
  • fedilink
  • source
  • parent