Selfhosted

40696 readers

412 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 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Ripping my hair out over this, how do I make Wireguard in Docker work? (sh.itjust.works)

submitted 5 days ago* (last edited 5 days ago) by amogussussywussy@sh.itjust.works to c/selfhosted@lemmy.world

11 comments fedilink hide all child comments

I'm a noob to self-hosting, I have set up some containers but only through watching tutorials on youtube, in reality I barely understand what I'm doing.

I have a wireguard docker container set up, but when I connect to it with my phone, there's no internet.

Can somebody tell me what I'm doing wrong? I just want to access my server outside my home network.

Here is the docker-compose.

version: "2.1" services: wireguard: image: linuxserver/wireguard container_name: wireguard cap_add: - NET_ADMIN - SYS_MODULE environment: - PUID=1000 - PGID=1000 - TZ=Asia/Singapore - SERVERURL=auto #optional - SERVERPORT=51820 #optional - PEERS=1 #optional - PEERDNS=auto #optional - INTERNAL_SUBNET=10.13.13.0 #optional volumes: - ./config:/config - /lib/modules:/lib/modules ports: - 51820:51820/udp sysctls: - net.ipv4.ip_forward=1 - net.ipv4.conf.all.src_valid_mark=1 restart: unless-stopped

Please tell me if there is anymore information I need to provide.

EDIT: fellas i figured it out, i just had to port foward 51820 on my router :sob: thank you for your help in the comments

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

[–] RxBrad@infosec.pub 2 points 5 days ago* (last edited 5 days ago)

EDIT: My suggestion probably doesn't work for your use-case, but I'll leave it for anyone else....

I use this to only tunnel the ports I actually need: https://github.com/DigitallyRefined/docker-wireguard-tunnel

My CGNAT'ed home PC is the client, and my public-facing Oracle Cloud instance is the server.

I've tried and failed miserably to use the "official" Wireguard container. Once I start reading suggestions to modify iptables outside of Docker, I know I'm in trouble.