6
cannot open port 443
(lemmy.one)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 15 Jun 2023
6 points (100.0% liked)
Selfhosted
60644 readers
600 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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
To me this seems like a routing issue. Some things to check:
jellyfin.mydomain.comto your jellyfin server's LAN IP?jellyfin.mydomain.comon 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!
Is it normal i cannot access the jellyfin service from the internal network using the Jellyfin.domain.om
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)
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 @fixmycode@feddit.cl 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.comto your jellyfin servers LAN IP and test the connection works.