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!

  • hello_world@feddit.ukEnglish
    1·
    1 year ago

    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.

    • encode8062@lemmy.oneOPEnglish
      0·
      1 year ago

      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

      • LordChaos82@fosstodon.org
        0·
        1 year ago

        @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.

        • hello_world@feddit.ukEnglish
          0·
          1 year ago

          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?

          • LordChaos82@fosstodon.org
            0·
            1 year ago

            @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.

            • hello_world@feddit.uk
              0·
              1 year ago

              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.

              • LordChaos82@fosstodon.org
                0·
                1 year ago

                @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.

                • hello_world@feddit.ukEnglish
                  1·
                  1 year ago

                  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?)

  • dudeami0@lemmy.dudeami.winEnglish
    1·
    1 year ago

    To me this seems like a routing issue. Some things to check:

    • Can a port checking service (like canyouseeme) see 443?
    • Can you connect to 443 from the internet (use a VPN or separate network)?
    • Can you edit your hosts file to point jellyfin.mydomain.com to your jellyfin server’s LAN IP?
    • After doing this, can you connect to jellyfin.mydomain.com on the LAN?

    My guess is the router is routing traffic to it’s external IP from the LAN back to itself, without following port forwarding rules. Good luck figuring it out though!