encode8062

cannot open port 443

https://lemmy.one/post/132139

cannot open port 443 - Lemmy.one

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 [http://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 [http://jellyfin.my] domain.com:8443 [http://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!

Jun 15, 2023 at 1:44pmWeb
Show threadTheButtonJustSpinsJun 15, 2023
Look into using a reverse proxy that owns 443 and serves your other applications.
Show threadhello_worldJun 15, 2023
I have nextcloud running just fine (with Apache) on a non-443 port. What issue are you seeing exactly? Once your webserver is listening on your port of choice, Nextcloud will show an "untrusted domain" warning if the domain/port have not been set in config.php properly. After that is done, it works perfectly for me.
Show threadencode8062Jun 15, 2023
I was running nextcloud in a docker (and was maybe thinking of running it in snap), how can i change the default 443 port. I have no experience with the docker from nextcloud
Show threadLordChaos82Jun 15, 2023
@encode8062 @hello_world Please try to avoid using nextcloud in snap. I started with nextcloud in snap and came a long way before I realized the performance and upgrade issues when using snap version of nextcloud. For me it was too late but now I try to ask people to avoid it at all costs.
Show threadencode8062Jun 15, 2023
Thanks you so much for the warning. I was already doubting if that would be a smart choice.
Show threadhello_worldJun 15, 2023
Not using Nextcloud in snap and not sure where I said I was using it inside snap? What installation method are you using at the moment?
Show threadLordChaos82Jun 15, 2023
@hello_world Sorry, my reply was meant for @encode8062 . Not sure how you got tagged.
If the question was for me, I am stuck with using it in snap as my family and I have too much invested in Nextcloud to try to attempt a migration to a non snap instance.
Show threadhello_worldJun 15, 2023

No worries :) Let me rephrase the question though - what installation method would you be using if you could?

So far I'm reasonably happy with a baremetal installation, but considering moving it into some kind of VM.

Show threadLordChaos82Jun 15, 2023
@hello_world I would be using it in a VM or bare metal if I could. I have heard good things about Nextcloud in docker but we are power users on Nextcloud in my house so not sure if docker instance of nextcloud could handle the load.
Show threadhello_worldJun 15, 2023
I'd hope for the exact same performance with Docker (or KVM) as on a baremetal host, unless you're doing userspace networking for ultra-low latency Nextcloud :D (and even that I suppose you could PCI-passthrough the network card?)
Show threadLordChaos82Jun 15, 2023
@hello_world I would agree. We have around 2 TB of data hosted on our snap nextcloud instance so I would not even know where to start if I ever wanted to migrate it to a separate instance on docker, VM or bare metal :(
Show threadhello_worldJun 15, 2023
My condolences! Copying the data around may be reasonably straightforward if you can get it out of the snap (it's just a directory, after all), but I have no idea how the database is setup for it. Good luck nevertheless!
Show threadr0ckrJun 15, 2023

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:

  • Request for jellyfin.mydomain.com comes in
  • 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.

    Show threadencode8062Jun 15, 2023
    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
    Show threadeddieJun 15, 2023
    If vising jellyfin.mydomain.com presents you with your routers config that means you don't have port forwarding working correctly for ports 443. You should google your router's name + "port forwarding".
    Show threadencode8062Jun 15, 2023

    I have:

    Show threadeddieJun 15, 2023

    I'd make sure your forwarding http (port 80) to that same internal host too. I'm assuming thats your jellyfin server.

    On your local network, does going to https://192.168.1.4 present you with what you actually want?

    Show threadencode8062Jun 15, 2023
    port 80 is also forwarded. I am not at home now, ill test tomorrow