Selfhosted

39435 readers

5 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

[email protected]

cannot open port 443 (lemmy.one)

submitted 2 years ago by [email protected] to c/[email protected]

24 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

[–] [email protected] 1 points 2 years ago (1 children)

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

[–] [email protected] 1 points 2 years ago (1 children)

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.

[–] [email protected] 1 points 2 years ago (1 children)

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

[–] [email protected] 2 points 2 years ago (1 children)

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

[–] [email protected] 0 points 2 years ago (1 children)

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

[–] [email protected] 1 points 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!