Raspberry Pi as a local server for self hosting applications

Post by fareesh » Tue, Sep 15, 2020, 9:10 AM UTC

phaer wrote: post #216

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…

> 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. You'll need don't need any of that with Onion Services. Tor does not only anonymize, but offers easily configurable services with NAT punching, an .oni…

Post by encom » Tue, Sep 15, 2020, 9:26 AM UTC

tga wrote: post #239

encom wrote: post #124

Earlier quoted context omitted.

I wanted to do that, but I had a look at Pi Hole and ran away screaming. Instead of proper packaging, they have a 3000 line install script they want you to pipe into Bash. I went a saner route, and used dnsmasq and a blocklist[1] updated nightly via cron. Dnsmasq in turn queries Stubby that talks to uncensoreddns.org via DNS-over-TLS. Boom, DoT on my entire LAN. [1] https://github.com/notracking/hosts-blocklists

Would you feel better with a 3000 line install script inside a package? Or maybe you would prefer the same 3000 lines of code nicely compiled in a single binary?

Post by SturgeonsLaw » Tue, Sep 15, 2020, 9:29 AM UTC

z3t4 wrote: post #192

CydeWeys wrote: post #147

Earlier quoted context omitted.

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.

Post by simfoo » Tue, Sep 15, 2020, 9:38 AM UTC

xyzzy_plugh wrote: post #93

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…

Or just setup Tailscale, which takes about two minutes.

Post by ptrwis » Tue, Sep 15, 2020, 9:53 AM UTC

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.