Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Raspberry Pi as a local server for self hosting applications

cri.dev

Post reply on HN
Print view View original

131–140 of 321 posts

Re: Raspberry Pi as a local server for self hosting applications

#131

Post by cguess »

anderspitman wrote: post #82

The hardware is there (RPi + USB storage). The server software is there (NextCloud, Plex, n8n, etc). What isn't there is the plumbing. The next logical step after this blog post is making your services accessible to your phone over the public net. You'll immediately find yourself mired in domain name registration, VPS management, TLS cert management, dyndns, port forwarding, hole punching, etc etc. There are lots of…

> I think we need something like Namecheap + CloudFlare + ngrok, designed and marketed for self-hosters and federators. You simply register a domain and run a client tool on each of your machines that talks to a central server which tunnels HTTPS connections securely to the clients.

PageKite (https://www.pagekite.net) is what it sounds like you're looking for. It'll set you up with a url, SSL, and a tunnel in about 30 seconds. Highly configurable for your own domain if you'd like, multiple ports etc.

Re: Raspberry Pi as a local server for self hosting applications

#132

Post by milankragujevic »

devwastaken wrote: post #116
anderspitman wrote: post #82

The hardware is there (RPi + USB storage). The server software is there (NextCloud, Plex, n8n, etc). What isn't there is the plumbing. The next logical step after this blog post is making your services accessible to your phone over the public net. You'll immediately find yourself mired in domain name registration, VPS management, TLS cert management, dyndns, port forwarding, hole punching, etc etc. There are lots of…

It's against cloudflare tos to be doing mostly video/images for free. It would be a great idea as it would solve the problem of IP exposure but if it gained any traction it'd have to be shut down.

In my experience, you have to be way above 1 TB per day to get banned - I know because I pushed around 5000 simultaneous HD streams on my account back when I ran a pirate streaming service (Google my name if interested, it's on the Verge), and it lasted for a few days before I shut it down due to MPAA, but didn't get banned by CloudFlare. I still have the account that I did that on, it's from 2011. and still used for a few of my sites.

Re: Raspberry Pi as a local server for self hosting applications

#133

Post by fomine3 »

fao_ wrote: post #70
rjsw wrote: post #37

Earlier quoted context omitted.

Switch to a better ISP.

I don't see how this is seriously a suggestion. Not everyone lives in Silicon Valley and earns a >20k/yr paycheck. There are other things to consider like reliability, cost, that force your hand.

Anyway ISP that blocks port 80 or uses CGNAT is obviously not good a selection for such a user. So it's serious suggestion if you can choose ISP. There are many places where can choose ISP even not in SV (maybe outside US).

Re: Raspberry Pi as a local server for self hosting applications

#134

Post by chrios »

anderspitman wrote: post #82

The hardware is there (RPi + USB storage). The server software is there (NextCloud, Plex, n8n, etc). What isn't there is the plumbing. The next logical step after this blog post is making your services accessible to your phone over the public net. You'll immediately find yourself mired in domain name registration, VPS management, TLS cert management, dyndns, port forwarding, hole punching, etc etc. There are lots of…

Use IPv6.

It doesn't have the address exhaustion that caused providers to implement CGNAT, and dynamic IPv4 addresses.

No need for VPS management, DynDNS, port forwarding, hold punching. You still need public DNS, but you can use public DNS as your internal zone as well (no need for split DNS). You also still need PKI, so maybe setup a reverse proxy for SSL termination with a wildcard certificate.

Re: Raspberry Pi as a local server for self hosting applications

#135

Post by duskwuff »

anderspitman wrote: post #89
Aperocky wrote: post #85

Earlier quoted context omitted.

> Mapping X subdomain to Y port on Z machine should take a couple clicks from a web interface. route53 can work like that, it also has a cli version. (But you can't get the domain there).

Can it tunnel to local devices like a RPi or just AWS VMs?

No, it's just DNS. It doesn't provide any additional routing.

Re: Raspberry Pi as a local server for self hosting applications

#136

Post by an_opabinia »

Aperocky wrote: post #85
anderspitman wrote: post #82

The hardware is there (RPi + USB storage). The server software is there (NextCloud, Plex, n8n, etc). What isn't there is the plumbing. The next logical step after this blog post is making your services accessible to your phone over the public net. You'll immediately find yourself mired in domain name registration, VPS management, TLS cert management, dyndns, port forwarding, hole punching, etc etc. There are lots of…

> Mapping X subdomain to Y port on Z machine should take a couple clicks from a web interface. route53 can work like that, it also has a cli version. (But you can't get the domain there).

> (But you can't get the domain there)

There's Amazon Domains now.

Additionally, https://github.com/crazy-max/ddns-route53 works well as a dynamic DNS configurator for Route 53.

For most home users, a Docker-supporting server is the best option.

Traefik has ACME and labels-based configuration for Docker hosts. It is a good choice for multiplexing HTTPS services by subdomain names.

In my opinion the biggest limitation is that there is no universal API for network routing appliances, whether it is your $30 home combo WiFi/router or your $20,000 Cisco device.

An access-key-authorized version of UPnP would be sufficient for the vast majority of users. Or even iptables commands over public key authenticated SSH.

But giant corporations - Google, Microsoft, Apple, Amazon, Facebook - they are in the cloud business, Microsoft doesn't ship a home server technology really anymore.

The most popular home server software, like Plex, is really purposefully disruptive to giant software and media companies. By contrast you're going to have a bad time running your own Dropbox competitor from home, because that sort of technology is engineered around cloud computing.

Re: Raspberry Pi as a local server for self hosting applications

#137

Post by [deleted] »

daniellarusso wrote: post #121
ocdtrekkie wrote: post #60

Earlier quoted context omitted.

I've been using a RasPi for a Pihole for years and this is a constant peeve. No matter how many precautions it takes, it eventually dives. RasPi is neat for a lot of things but I'm not convinced it's an ideal selfhosting platform. By the time you invest in the necessary addons, you might as well have gotten a used actual server.

This is where I am at right now. I have wasted alot of time and lost a not insignificant amount of external data. I am about to buy a FreeNAS mini tower.

[deleted]

Re: Raspberry Pi as a local server for self hosting applications

#140

Post by sorenjan »

mqus wrote: post #123
z3t4 wrote: post #107

Earlier quoted context omitted.

Most home routers have functionality to do port forwarding and dyndns. Certbot for TLS/cert. Just get a free domain from the dyndns service. No VPS needed if you got your own hardware/Rasbery. Make sure you have backups. Just Dont expect a $30 PC to be without issues.

For me its not the 30$ pc that has issues but the 10$ microsd card the os is on. I had to replace it for the third time in about 6 years now. But this is not something new of course, everybody will tell you to either use good uSD cards or put the os somewhere else, like an external hdd or so.

This is purely an anecdote, but I had to replace a few SD cards in my Pi until I changed power supply. It's not even the official, it's just one that's rated for 5.0 V, 2.5 A. I've used the same card for a few years now.
Post reply on HN