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
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 years 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?)

    • LordChaos82@fosstodon.org
      link
      fedilink
      arrow-up
      1
      ·
      2 years ago

      @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 :(

      • hello_world
        link
        fedilink
        arrow-up
        2
        ·
        2 years ago

        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!