161–170 of 307 posts
Earlier quoted context omitted.
My problem is that I have never been able to purchase residential internet that allowed me to open port 443 or port 80.
Why do ISPs do this? Is there a legitimate reason or they just feel that their clients don’t host these services so they might as well block the ports for safety?
Earlier quoted context omitted.
You can move ssh to a different port.
Anyone who thinks they need to move ssh to a different port likely doesn’t have their ssh security configuration setup optimally.
One thing to be mindful of is security. The last you want is for your setup to be compromised, be used to send spam/botnets and then getting perma-banned from your ISP. I would argue it's a lot less risky just to put your static site on S3/Github etc.
You don’t get perma-banned from your ISP for getting malware. That’s pure FUD. Far more people (at least 2 orders of magnitude) end up infected with malware and become members of botnets from just clicking dumb shit. They don’t get banned from the ISP either.
I know of friends who have been banned for doing exactly this.
If you don't need all that cloud operations/deployment infrastructure, self hosting a website from home in 2023 is as easy as it was in 2003. Get a DDNS, do the NAT port forwarding, run some apache/nginx/whatever and push your files with sftp or similar to the server. In contrast to 2003, upstreams got better -- even Germany has average upstream speeds of 20mbit/second nowadays [1]. With 20mbit/sec you can do quite s…
My problem is that I have never been able to purchase residential internet that allowed me to open port 443 or port 80.
I'm still not convinced that self hosting is cheaper though. Where I live, both the electric grid and Fibre connections are unreliable, and the ISP charges about $3/month for a static IP. Assuming 2.5W for a RPi, it takes 1.8kWh a month, costing around $0.25 for electricity. This also has the downside of using residential IPs, having to deal with CGNAT/NAT if the ISP has no static IPs, exposing your home IP, slow dis…
Anyway I'm not paying in/out costs or costs for static hosting. Looking at hetzner's offerings it apears to be 536.58 euros/month for 10tb of storage? That's block storage on SSD, maybe they have cheaper HDD storage somewhere?
Point is I think my server setup may have "paid for itself" (not that it makes me money) after one month. And that's for 38TB total of RAIDZ1 space, I'm only filling 20TB so far of it. In actually it's like 60 something TB of space lol I just wanted RAID so I could lose a drive. I've got plenty of room to grow and swap components as needed.
It's just one command.
I'm all for self-hosting and run a few services on my LAN, but would never allow HTTP traffic from the internet to enter my network. If you've ever seen a public nginx log, you'll know it constantly gets hit by all kinds of bots and vulnerability scanners. No matter how secure and isolated I make the web server, I just don't want to see that traffic, nor expose my home IP to further scrutiny. It's trivial to host a s…
The security aspect is a struggle. Something like shellshock [1] needs to be patched immediately, which really requires automation. With shellshock, even self-hosted static hosting could be impacted. Similar vulnerabilities be discovered in the future.
I'd want to isolate anything external facing from the rest of my home network for that reason.
[1] https://en.m.wikipedia.org/wiki/Shellshock_(software_bug)
If you don't need all that cloud operations/deployment infrastructure, self hosting a website from home in 2023 is as easy as it was in 2003. Get a DDNS, do the NAT port forwarding, run some apache/nginx/whatever and push your files with sftp or similar to the server. In contrast to 2003, upstreams got better -- even Germany has average upstream speeds of 20mbit/second nowadays [1]. With 20mbit/sec you can do quite s…
My problem is that I have never been able to purchase residential internet that allowed me to open port 443 or port 80.
You can still use NextJS - just get it to prerender the entire site statically. Then you get the plus sides of using NextJS, but can take your static ZIP file of files to any host you like, or self host.
You then get, for example, an HTML file, with all the elements ready on page load, which can be 'rehydrated' when React kicks in for deep functionality and interactivity.