Wireguard might work well here. You'll have to set it up on each device you want to have access your server, but I'm guessing that syncing only involves a handful of devices, which wouldn't be bad.
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
So if I understand this correctly, I configure wireguard on the server end and port forward to the IP for the wireguard interface? and then configure devices to send packets through their wireguard interface for specific applications to get synced up? Thanks for your reply :)
Yeah, when you configure it, you essentially say "all traffic to 1.2.3.0/24 should go through this wireguard connection". Then, your OS automagically knows "oh, this connection to 1.2.3.4 should go through Wireguard, and I'll handle it like so". You don't have to configure any applications specifically, their network connections just get routed appropriately by your OS.
So I'm just taking a look at wireguard on android. I just need to point a specific address to wireguard and it takes care of it then? This seems relatively straightforward to configure.
Last question (hopefully). I'm running this server off a pi with bullseye. The guide on their site for setting up a server uses buster but the client uses bullseye. The buster version needs to setup unstable release packages but the bullseye client doesn't. This should mean that I'm good to just grab the default Debian package on bullseye?
Thank you very much for your help with this!
If you want an (even) simpler wireguard setup, you could also look into https://pivpn.io/ for the server side.
Use a reverse proxy in front and be sure to have auth setup in Baikal.
I’ve been using it with traefik for 5ish years now without issues.
Just in case you never heard of it, there is also the option to use Tailscale. It lets you connect to your services without opening any ports and uses Wireguard under the hood but makes configuration simpler
I have wireguard set up now and its working completely fine now. Thanks for the recommendation!
There are a number of options...
Setup a reverse proxy with nginx, using SSL, with http auth or better yet client certificates.
Setup a VPN to access your home network.
Use SSH forwarding to access the local service.
Are these all roughly equivalent in security? Or is it a case of some of these being a bit less complex to set up but you sacrifice security? I'll look into these options though. Thank you
If setup correctly they are mostly equivalent.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
Fewer Letters | More Letters |
---|---|
HTTP | Hypertext Transfer Protocol, the Web |
IP | Internet Protocol |
SSH | Secure Shell for remote terminal access |
SSL | Secure Sockets Layer, for transparent encryption |
VPN | Virtual Private Network |
nginx | Popular HTTP server |
5 acronyms in this thread; the most compressed thread commented on today has 11 acronyms.
[Thread #80 for this sub, first seen 25th Aug 2023, 11:15] [FAQ] [Full list] [Contact] [Source code]