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:
- 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
Mine was having some weird problem with docker, I think it must be a docker bug. Basically it put the Wanderer stuff at the very bottom of the routes (running "sudo route" on Debian lists the routes). The last entry in the routes table needs to be eth0 or the equivalent so that stuff can loop back to the beginning of the list. At least that's my understanding.
So anyway, to get around that bug/limitation I had to create a static docker network which I called "wanderer-static" using
docker network create --attachable -d bridge --subnet 172.28.0.0/16 --gateway 172.28.0.1 wanderer-static
. Choose a subnet that's not being used already.Then in the docker compose file, point everything at that network by:
Removing
Adding
And finally, pointing each service to that network. Under each service you should have:
I also had to update the ORIGIN and whatever else to
http://wanderer-static:7000
, etc.