this post was submitted on 15 Jun 2023
6 points (100.0% liked)

Selfhosted

39980 readers
808 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

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

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
6
cannot open port 443 (lemmy.one)
submitted 1 year ago by [email protected] to c/[email protected]
23 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] 3 points 1 year ago (1 children)

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!

[–] [email protected] 1 points 1 year ago (2 children)
  • Yes!
  • yes but it is 307 temporary redirect to router config page
  • i am not sure what you mean

Is it normal i cannot access the jellyfin service from the internal network using the Jellyfin.domain.om

[–] [email protected] 2 points 1 year ago

I feel you can't access because your router doesn't loop back connections to your own IP. To fix that you might need to run a local dns that routes traffic to that domain to your local machine, you can do that running a service like dnsmasq and pointing your router to that service instead of the default dns (and always set a secondary DNS in case your service fails)

[–] [email protected] 2 points 1 year ago

If you are seeing your routers config page, and you are sure you are connecting from outside your network, it sounds like the router's 443 page is overriding the port forwarding. Otherwise, it's like @[email protected] said and you just need a local DNS that points to the right spot locally, and let your public DNS point for external connections.

As for the hosts file, you can see a guide here for windows/linux/mac. Basically this is a override of any DNS entries. Here you can point jellyfin.domain.com to your jellyfin servers LAN IP and test the connection works.