4 ms·

Isn't self-hosting usually forbidden by most ISPs? I've read countless times in the ToS of ISPs that running your own server is against their terms. Also: if y

Isn't self-hosting usually forbidden by most ISPs? I've read countless times in the ToS of ISPs that running your own server is against their terms. Also: if you suffer from frequent power outages, you have to have a server that 'bounces back' and survives the outage, with all the necessary services up and running after a reboot. Good luck writing scripts for that scenario.

hellbannedguy 5y ago
I have heard the same for years. I have a feeling they forbid it in tos, but don't enforce it in most areas? Does anyone know for sure if Xfinity in Marin County, Ca allows self-hosting?
- hoppyhoppy2 5y ago
  >[You may not] use or run dedicated, stand-alone equipment or servers from the Premises that provide network content or any other services to anyone outside of your Premises local area network (“Premises LAN”), also commonly referred to as public services or servers. Examples of prohibited equipment and servers include, but are not limited to, email, web hosting, file sharing, and proxy services and servers https://www.xfinity.com/Corporate/Customers/Policies/HighSpeedInternetAUP https://www.xfinity.com/Corporate/Customers/Policies/HighSpe... This applies to Comcast's (at least residential) customers nationwide. But I, like you, get the sense that it's there so they can shut down excessive bandwidth use; I haven't heard about them trying to shut down a low-traffic webserver or self-hosted stuff for one's own personal use (though I probably wouldn't try to run a gaming server or anything high-traffic). Just be aware that it is technically against Comcast's Acceptable Use Policy, and try to switch to a better internet provider if you have the option.
alamortsubite 5y ago
> if you suffer from frequent power outages, you have to have a server that 'bounces back' and survives the outage In my experience self-hosting a number of services, it's really no more challenging than managing the services themselves. A BIOS that supports wake-on-power is obviously a key hardware requirement. On the software side, I find systemd and DuckDNS to be very helpful and easy to use. One of my sites is a remote cabin that suffers blackouts all the time. It has the burden of an LTE connection, which means it requires an ssh tunnel to get around the ISP's firewall. This makes autossh an additional, if simple and reliable component.

hellbannedguy 5y ago

I have heard the same for years. I have a feeling they forbid it in tos, but don't enforce it in most areas? Does anyone know for sure if Xfinity in Marin County, Ca allows self-hosting?

hoppyhoppy2 5y ago
>[You may not] use or run dedicated, stand-alone equipment or servers from the Premises that provide network content or any other services to anyone outside of your Premises local area network (“Premises LAN”), also commonly referred to as public services or servers. Examples of prohibited equipment and servers include, but are not limited to, email, web hosting, file sharing, and proxy services and servers https://www.xfinity.com/Corporate/Customers/Policies/HighSpeedInternetAUP https://www.xfinity.com/Corporate/Customers/Policies/HighSpe... This applies to Comcast's (at least residential) customers nationwide. But I, like you, get the sense that it's there so they can shut down excessive bandwidth use; I haven't heard about them trying to shut down a low-traffic webserver or self-hosted stuff for one's own personal use (though I probably wouldn't try to run a gaming server or anything high-traffic). Just be aware that it is technically against Comcast's Acceptable Use Policy, and try to switch to a better internet provider if you have the option.

alamortsubite 5y ago

> if you suffer from frequent power outages, you have to have a server that 'bounces back' and survives the outage In my experience self-hosting a number of services, it's really no more challenging than managing the services themselves. A BIOS that supports wake-on-power is obviously a key hardware requirement. On the software side, I find systemd and DuckDNS to be very helpful and easy to use. One of my sites is a remote cabin that suffers blackouts all the time. It has the burden of an LTE connection, which means it requires an ssh tunnel to get around the ISP's firewall. This makes autossh an additional, if simple and reliable component.