this post was submitted on 16 Jan 2025
7 points (76.9% liked)

Self Hosted - Self-hosting your services.

11811 readers
1 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

Important

Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!

Cross-posting

If you see a rule-breaker please DM the mods!

founded 3 years ago
MODERATORS
 

I'm new to self-hosting and struggling to get my services accessible externally. I'm using Traefik as a reverse proxy on a Raspberry Pi 500 running Stormux (Arch Linux ARM-based). My public IP resolves correctly via Dynu DNS, and ports 80 and 8444 are forwarded in my router. I've configured Traefik to use port 8444 for HTTPS, but external connections time out. I’ve tried:
• Forwarding ports 80 and 8444 in my router
• Allowing ports in iptables and FirewallD
• Setting my router's firewall to low security
• Verifying Traefik is listening on port 8444 locally (works with curl)
• Using Authelia for authentication (middleware configured in Traefik)
Internal access works fine, but external access fails. Could this be an ISP block or something I’m missing? Any advice is appreciated! 🙏
#SelfHosting #Traefik #RaspberryPi #DynuDNS #ReverseProxy #Networking #Help #Tech #Technology #Linux
@selfhost @selfhosting @selfhosted @linux

top 18 comments
sorted by: hot top controversial new old
[–] bravemonkey 2 points 2 weeks ago (1 children)

Do you have any service listening on port 80? If not, I'd close it in the firewall and disable the forwarding in the router. Also sounds like a bad idea to set your router security to 'low', whatever that means for your router.

You can use a tool like this to check if your ports are accessible from the internet: https://www.yougetsignal.com/tools/open-ports/

[–] [email protected] 1 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

@bravemonkey The plan was to set it to low temporarily. The choices were high, medium, low, or off. One of the ports Traefik listens on is 80. I used portchecktool.com and it told me the connection was timing out.

[–] bravemonkey 1 points 2 weeks ago

So that means the router isn't forwarding the ports to your devices. As others have said, it could be the ISP blocking it or it could be a configuration issue in the port fowarding.

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

Maybe your ISP has you on CGNAT? If your public IP is between 100.64.0.0 and 100.127.255.255 you're on CGNAT.

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

@MangoPenguin Nope, public IP starts with 69.58.

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

Since you're using a non-standard HTTPS port, check your browser network log in dev tools and make sure your app isn't redirecting you to the standard port 443. With non-standard ports you often will need to customize the config of apps so they know what you're using.

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

@RareBird15
Most ISPs do block incomming traffic by default. You should contact them and request to enable it.
@selfhost @selfhosting @selfhosted @linux

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

@geillescas @selfhost @selfhosting @selfhosted @linux I'll have to see about this. I'm not the account holder and the one who is, my stepdad, isn't exactly tech-savvy. My router did have a firewall blocking traffic, but I changed its security level and looked at the rules, so that shouldn't be an issue anymore.

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

@RareBird15 @selfhost @selfhosting @selfhosted @linux ISP block is quite possible, some will restrict certain ports to business accounts only or make you call to unlock them.

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

@jyarbrough @selfhost
@bravemonkey @selfhosting @selfhosted @linux @MangoPenguin @geillescas Yeah, I'm very tempted to go back to the way I had things, which allowed me to access services with my Raspberry Pi's IP and a port number. Since I don't leave home much and I'm not the ISP account holder, this is starting to seem like more trouble than it's worth.

[–] [email protected] 2 points 2 weeks ago

Your ISP doesn't allow port or 443. Change those to something else, or reverse proxy 80 to 8080 or whatever.

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

Why 8444? Just forward 443. try if you can connect to your ip through a certain port from outside your network

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

@MaggiWuerze I thought 443 might have been blocked by my ISP at first because I tried it and had the same issues with it.

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

Can you try to connect to certain ports on your ip? Gotta try it from a friends house or mobile https://superuser.com/questions/621870/test-if-a-port-on-a-remote-system-is-reachable-without-telnet

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

Even easier is to turn off wifi on your cell phone and connect with that instead. No leaving the house necessary!

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

Yeah, that's what I meant with mobile

[–] [email protected] 1 points 1 week ago

Sorry, I quit reading before the end of the sentence.

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

Are your clients using port 8444 for https? 443 is the standard