Your ISP doesn't allow port or 443. Change those to something else, or reverse proxy 80 to 8080 or whatever.
this post was submitted on 16 Jan 2025
8 points (78.6% liked)
Self Hosted - Self-hosting your services.
11598 readers
2 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
- No harassment
- crossposts from c/Open Source & c/docker & related may be allowed, depending on context
- Video Promoting is allowed if is within the topic.
- No spamming.
- Stay friendly.
- Follow the lemmy.ml instance rules.
- Tag your post. (Read under)
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!
- Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate.
Cross-posting
- [email protected] is allowed!
- [email protected] is allowed!
- [email protected] is allowed!
- [email protected] is allowed if topic has to do with selfhosting.
- [email protected] is allowed!
If you see a rule-breaker please DM the mods!
founded 3 years ago
MODERATORS
@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.
@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.
@RareBird15
Most ISPs do block incomming traffic by default. You should contact them and request to enable it.
@selfhost @selfhosting @selfhosted @linux
@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.
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.
@MangoPenguin Nope, public IP starts with 69.58.
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.
Why 8444? Just forward 443. try if you can connect to your ip through a certain port from outside your network
@MaggiWuerze I thought 443 might have been blocked by my ISP at first because I tried it and had the same issues with it.
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
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/
@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.
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.
Are your clients using port 8444 for https? 443 is the standard
@Jimbabwe Yes. I originally tried 443 but when it didn't work, I thought it might have been blocked by my ISP.