Selfhosted

40180 readers

1487 users here now

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!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Setting up Baikal (lemm.ee)

submitted 1 year ago by Corr@lemm.ee to c/selfhosted@lemmy.world

12 comments fedilink hide all child comments

I've managed to set up a baikal server to sync my calendars and tasks instead of using a free cloud service provided by nextcloud. I'm able to reach it from beyond my local network, but this is all very new to me and I'm a little worried about what permanently leaving a port open for this.

I'm hoping to find some resources for securing this, before leaving it up all the time. I suppose as an alternative I can always only run it at home and only sync when I'm home but this seems less ideal.

Thanks a bunch for the help in advance. I really appreciate it.

you are viewing a single comment's thread
view the rest of the comments

[–] Corr@lemm.ee 1 points 1 year ago (1 children)

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 :)

[–] BitSound@lemmy.world 2 points 1 year ago (1 children)

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.

[–] Corr@lemm.ee 1 points 1 year ago (1 children)

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!

[–] Patrick@discuss.tchncs.de 2 points 1 year ago

If you want an (even) simpler wireguard setup, you could also look into https://pivpn.io/ for the server side.