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

191–200 of 321 posts

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

#191

Post by choward »

coronadisaster wrote: post #163
gonehome wrote: post #26

How do people access these servers off of their home network (or do they not?). That seems like most of the value to me, hosting some service you can access from anywhere without having to use Digital Ocean. It seems like most residential ISPs don't provide a static IP and some block port 80? I think forcing ISPs to allow home users to serve traffic via some standard method would go a long way to enabling a more dece…

My dynamic IP address with Comcast is pretty much static but I guess it is not a guarantee... I can get it to change by spoofing my router MAC address though.

Same. Mine has been the same for at least 5 years.

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

#192

Post by z3t4 »

CydeWeys wrote: post #147
imrelaxed wrote: post #146

Earlier quoted context omitted.

Huh? Why can’t you assign a port/s to the CPE? You can even implement a port knocking scheme if you’re worried about some service/s on your home network being wide open to the world.

The point is that outside traffic isn't even reaching anything you even have control over, because you don't have a public IP (i.e. the ISP won't set up port forwarding for you). Let's say you wanted to directly send a packet to my phone. There's no way we could make that happen even with both of our cooperation because my phone doesn't get a publicly addressable IP.

Nat:ed ip's are a PITA. But any decent ISP will give you a public IP if you ask. We are running out of ipv4 addresses.

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

#193

Post by sneak »

Note that if you got all excited about n8n when learning about it from this webpage, as a potential open source Zapier:

n8n is not open source, despite being source available. The author goes to pretty great lengths to avoid confronting this fact.

https://github.com/n8n-io/n8n/issues/40

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

#194

Post by numpad0 »

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.

Many Raspberry Pi distro spend all the card’s TBW writing /var/log stuffs for no reason. It’s a known issue often attributed to “cheap microSD cards”.

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

#195

Post by bjoli »

Polylactic_acid wrote: post #101
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 tried running nextcloud on an rpi. It just doesn't cut it. I had the 4gb model and nextcloud runs but its a horrible experience. You go on the web UI and click a photo and it takes 10 seconds to load. Moved my server to a ryzen 5 based setup and now everything is instant. I'm not sure what the limiting factor on the rpi was because the ram and cpu usage was low. Perhaps it was memory or storage speed.

I moved all my home cloud stuff to an old dell small form factor computer that I bought for 40 bucks from a company selling all their old inventory. It is an i5 4500-something that beats the pi4 in everything except 4k output. It also has an SSD and 8gb ram.

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

#196

Post by catdog »

m-p-3 wrote: post #148
mqus wrote: post #123

Earlier quoted context omitted.

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.

It's possible to boot from USB with the Pi4, I wouldn't run anything important from the MicroSD.

Even if direct USB boot does not work out you can just use the SD card to boot the kernel and have the root fs on USB.

With the PI4 you probably can even get better performance from using a USB storage device as it has USB 3.0 Ports.

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

#197

Post by anderspitman »

eat_veggies wrote: post #189
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…

Cloudflare argo tunnels are exactly what you're looking for https://developers.cloudflare.com/argo-tunnel/quickstart

I'm aware of argo tunnels. Unfortunately:

* Argo smart routing is 5 USD/mo + 0.1 USD/GB. The 5/mo is fine, but the data charges could add up quickly for something like Plex.

* CloudFlare doesn't sell domains.

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

#198

Post by anderspitman »

papul1993 wrote: post #177
anderspitman wrote: post #98

Earlier quoted context omitted.

Tailscale runs on WireGuard and therefore requires elevated permissions on each client device. That shouldn't be required for simply proxying a local port. Does Tailscale offer domain registration and TLS certs? Also, is there any way to allow public access to certain ports on certain machines, ie if you wanted to run your personal blog on your RPi?

I think there is a userspace version written in Go that shouldn't need root access.

Unless I'm mistaken, wireguard-go[0] only runs the WireGuard protocol code in userspace rather than the kernel. It still requires configuring network interfaces which requires root.

[0]: https://github.com/WireGuard/wireguard-go

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

#199

Post by anderspitman »

xyzzy_plugh wrote: post #120
anderspitman wrote: post #98

Earlier quoted context omitted.

Tailscale runs on WireGuard and therefore requires elevated permissions on each client device. That shouldn't be required for simply proxying a local port. Does Tailscale offer domain registration and TLS certs? Also, is there any way to allow public access to certain ports on certain machines, ie if you wanted to run your personal blog on your RPi?

I mean I suppose it requires elevated permissions but frankly it doesn't require any more permissions than most software, so this feels like a weird point to pick on. You need elevated permissions to bind 80 and 443, etc., right? You mentioned accessing your own devices from anywhere, and that's what I use Tailscale for. It was a dream to set up, and for my own services, I don't need TLS or custom domains, really. I…

> I mean I suppose it requires elevated permissions but frankly it doesn't require any more permissions than most software, so this feels like a weird point to pick on. You need elevated permissions to bind 80 and 443, etc., right?

I think maybe you're misunderstanding what my goal is. If I have a local webserver running on my laptop on port 8080, I want to expose that via HTTPS on a public domain. The server that terminates the HTTPS connection needs root to run on port 443, but my laptop doesn't need root to start the upstream webserver on 8080, and it shouldn't need root to tunnel it to the public server either.

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

#200

Post by anderspitman »

m-p-3 wrote: post #168
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…

Caddy? https://caddyserver.com/

Caddy is great, and it'll take care of managing the TLS certs. There's a lot left on my wishlist above...
Post reply on HN