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

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
[-] vividspecter@lemm.ee 2 points 4 days ago

Beyond the other comments is your public IP on ipinfo.io etc something like 100.64.X.X or 10.X.X.X?

If so, you're behind a CG-NAT and raw wireguard will not work. I say this so you don't waste time configuring something that will never work. Ignore the below if you have a real public IP.

Some ISPs will allow you to get a real dynamic ipv4 address for free, or you can configure ipv6 but any clients that you connect will also need public ipv6 support.

Otherwise, consider tailscale/headscale/netbird (SaaS or on a VPS) which have NAT traversal support.

this post was submitted on 17 Dec 2024
37 points (100.0% liked)

Selfhosted

40678 readers
314 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS