3 ms·
This is always my area of interest, and I rarely see it covered. Maybe all the people who do it just understand it so well that's it just an after thought for t
by Shawnecy 3y ago
This is always my area of interest, and I rarely see it covered. Maybe all the people who do it just understand it so well that's it just an after thought for them?
I've tried on numerous occasions to host my own services at home and use dynamic DNS to map to an IP, but when things don't work, it's hard to know if it's the hardware (consumer modems, routers, etc.), dirty ISPs who want to force you into a business tier to open up anything, some combination of the two, or something else altogether. Are the problems so one-off and specific that they all require bespoke problem-solving?
I would love it if anyone could share foolproof resources on the subject.
- treflop 3y agoI think it is because most of those things are just regular sysadmin things and homelab more refers to setting up hardware or software that you wouldn’t normally find at work. As for your actual problem, a lot of ports are blocked by ISPs because a LOT of computer worms have used them to spread malware in the past. However you usually can test to see if the port is open as well as try alternative uncommon ports like 47364 to see if they work. Some ISPs, although I believe mostly mobile ones, also use something called CGNAT where your Internet IP is actually an internal network IP within a part of the ISP, and you can usually test for this by checking if your IP is in a private range.
- bazmattaz 3y agoDid you try r/self hosted on Reddit. Thats where you’ll get support for something like that