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
I use the Traefik file provider for this.
https://doc.traefik.io/traefik/providers/file/
It picks up all my .yml configs in the watched folder which define the routers and services external to Docker.
Would the file provider configs live on the Traefik server, or would they need to be on the external service. Reading through this, and looking at the example configuration files doesn't really seem to point that out. Sorry for the noob questions.
Trying to understand this, but the way the documentation is written is different than I am used to.
Thank you!
No worries for the question. It's not terribly intuitive.
The configs live on the Traefik server. In my static traefik.yml config I have the following providers section, which adds the
file
provider in addition to thedocker
provider which you likely already have:And in the /config folder mapped into the Traefik container I have several files for services external to docker. You can combine them or keep them separate since the
watch: true
setting tells it to read in all files (and it's near instant when you create them, no need to restart Traefik).Here is my homeassistant.yml in that folder (I have a separate VM running HASS outside of Docker/Traefik):
Hope this helps!
so in my traefik.yml file I have cloudflare set as my certresolver as follows:
And I had to get the secret mounted via the docker-compose file.
So where you have:
tls:
Do I have to redefine all of the same information I did in my Traefik yml but in this separate config.yml?
(I did set it up in my traefik.yml and docker-compose.yml to mount and use this config, which I had commented out for later use.
Thank you so much for the help!
Edit:
Essentially I am trying to get my PiHole which is hosted on another pi setup with an SSL cert for local use only:
So in looking at your config I tried using:
However when doing this error logs returned:
I am doing something very wrong... And feel a little lost.
I think you're close.
You need to change
service: pihole-rtr
toservice: pihole-svc
.No, you just need to reference it like you have. Define once, reference many.
I will give this a shot! Thank you for the help. I will report back, in hopes that between your knowledge and my fumbles that someone else too can learn from this!
I hate to report back, but something isn't quite working for pihole behind Traefik.
running "docker logs traefik" returns no error, and yet no certificate was presented to my pihole.
Not sure what else I might be missing or that I might have wrong.
Can you see the router and service in the Traefik dashboard and do they show any errors there?
Shows in traefik, no errors there.
If you're sure you've got a DNS entry for the Pihole FQDN pointing at Traefik, open the dev panel in your browser (F12), switch it to the Network tab, and visit the pihole URL.
See if you get anything back and especially take note of the HTTP status codes.
I will likely have to do some tinkering, and more reading up on this from the documentation I am thinking. I am getting HTTP 200 statuses basically across the board. When going to the FQDN it doesn't redirect to the PiHole admin page like I was expecting. Again, likely some configuration that I have wrong.