Traefik: remote error: tls: bad certificate
I switched now successful to the production letsencryt server and get all the time these errors:
Traefik routing to another URL when a PathPrefix is part of another
I have this config file for Traefik (instanced by Coolify)
How to get traefik to generate ssl cert after adding new service?
I’m running traefik as a reverse proxy and SSL endpoint. Running as a docker-compose service. Yesterday I added a new router and service to my traefik-config/traefik-dynamic.yaml
. The new router is working; traffic is routed to my server correctly, so I know traefik found the new config without any other action from me. But it hasn’t yet generated the associated SSL cert and I don’t know how to make it do so. I’d prefer to avoid restarting it. I’m using acme and letsencrypt like this:
Traefik path with /#/
I’ve set up Traefik in Docker. I’ve encountered the following issue: I have a URL like https://example.net/#/foo, https://example.net/#/bar/foo etc. that I want to redirect to another domain on a different server, while keeping only the domain name changed, for example, to https://example2.net/#/foo. Essentially, I’m having trouble handling the “#” in the URL.