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!
view the rest of the comments
Thanks for helping, @deergon@lemmy.world.
Both traefik containers (on the "server" and "client" VMs) and the wireguard server container were built with
TRAEFIK_NETWORK_MODE=host
. The VMs can ping each other and the Wireguard containers can ping each other.Both traefik containers were built with
TRAEFIK_LOG_LEVEL=warn
but I changed them both toTRAEFIK_LOG_LEVEL=info
just now. There's a tad more info in the logs, but nothing that seems pertinent.How about the Traefik access logs (separate from the main log), do they reveal anything?
From traefik's access.log:
All I can tell from this is that there is a DownstreatStatus of 500. I don't know what that means.
Have you tried accessing your service url from inside the Traefik container? Eg. wget https://10.13.16.1? Also you seem to be accessing the service url with https, which usually requires insecureSkipVerify=true. Otherwise you might get http-500 error downstream.