so once you have a web server on the phone how are you able to make it available publicly on the internet? don't ISPs detect these and ban? are you using wireguard or something like that?

ive been looking to build and serve my own servers and i have been considering to use old android phones to outright racks but the part I am still struggling to figure out is how to serve it publicly without ISP catching on as they require business plans for that and its not cheap

A CloudFlare tunnel?

https://developers.cloudflare.com/cloudflare-one/networks/co...

Although, you may also go with a 5$ virtual host (e.g. Linode Nanode 1 GB) and wireguard to build your own tunnel (or just the 5$ virtual host to run your server)

> don't ISPs detect these and ban

No. No ISP who desperately tries to grow marketshare at all costs and lock their customers into a year-long contract will intentionally ban users. I'm not even sure where this misconception comes from, it's not like ISPs led a massive PR campaign warning people of the dangers of running a server.

The only way you will get banned is if you cause disproportionate strain on their network, which means you'd need to exceed the usage of the typical gamer (downloading games worth hundreds of gigs regularly), streamer (streaming 4k video for hours at a time), cloud backup customer (uploading gigabytes regularly), Windows user (in its default configuration Windows can use P2P to share updates), torrenter (sustained full-duplex bandwidth usage), and unlucky idiot with a compromised device spewing DoS traffic at line-rate.

Saturate the pipe consistently for several days by hosting video? Yeah sure you could get a warning and eventually disconnected, assuming they don't already have traffic shaping solutions in place to just silently throttle you to an acceptable level and leave it up to you to move your homebrew YouTube clone elsewhere when you realize it's too slow.

Hosting a website which will have a few mbps worth of traffic with the occasional spike? That's a rounding error compared to your normal legitimate usage, so totally fine.

The reason most consumer ISPs have a clause against running servers (not even defining what counts as a server) is to preempt a potential business starting a data center off a collection of consumer connections and then bitching about it or demanding compensation when it goes down or they get cut off. Nobody cares about a technical user playing around and hosting a blog at home.

Many ISP don't care.

Some may block port 80 and 443 "For Security", but you can sometimes contact the support and they'll open it, even if you're not a business.

I have a webserver running at home and use the free dynamic dns from noip.com.

> don't ISPs detect these and ban

No? I mean, I'm sure there are ISPs out there that do it, but that's a ridiculous thing to do.

It used to be easier to get a web server up and running in the past. I remember the 1990s fondly.

Not sure what changed, but things got more complex - and more expensive, too.

Other folks have given general answers, but I'm wondering, what ISP do you have, and where?

(I'm lucky to have Sonic, in the SF Bay Area. A local ISP that actively campaigned for net neutrality and has 1Gps symmetric as the standard basic fiber plan. Pretty sure they're not shutting down anybody's servers.)

ISPs don't care, actually. They care about operational problems, but you serving a constant stream of web traffic is probably not going to matter to them; web traffic for even a pretty successful blog is going to be a tiny volume compared to you streaming 4k movies from Netflix.

ISPs will have rules (maximum data volume per month) and restrictions (ISP equipment auto-drops all sending/receiving packets on port 25, 80, 443, or 456), but within those limits the ISPs do not care as long as you cause no problems for them.

Also, one of the easiest ways to expose e.g. port 80 of your in-house server is to just have your local server do an SSH port-forward to a remote server like a cheap VPS. Note that by default it'll bind to a localhost port on the remote, so on the remote you'd need to have an HTTP server reverse proxying to the remote localhost:8080, or you need to enable `GatewayPorts: yes` in sshd on the remote. Assuming you turn on GatewayPorts on remote.example.com, here's how you could expose port 80 of localhost:

    # Run this on in-your-house-computer to allow folks on public internet to visit
    # remote.example.com:80 but have the traffic served by in-your-house-computer:80
    ssh -R :80:localhost:80 username@remote.example.com

A Wireguard tunnel via a free tier or dirt cheap VPS, or a VPN provider that lets you forward ports like Proton

Why would your ISP ban you?