default cert return 404 after a few minutes of normal operation?

topcoffee4272

Hi there, trying to figure out where I am going wrong with my setup. I am not using a custom configuration file. I let cerwarden generate its own. I followed along with the docs created a dns01cloudflare provider pointing at my cloudflare domain. Using the default ACME Servers for production and staging and setup keys for both my ACME Servers.

I was able to create the default cert without any issues. I setup a DNS entry for certwaqrden.mydoimain.com to point at traefik and setup TCP routing with TLS passthrough in order to access certwarden and my other services controlled by physical certs.

This works fine for about 10 minutes and then for some reason I get a 404 error. Looking at the certs its valid and is verified with Let's Encypt even after I get the 404. What could be causing this? Do I need a new ACME Server for every single cert? I don't understand. It works but then stops working after a few minutes...

tcp:
  routers:
    certwarden:
      rule: "HostSNI(`certwarden.mydomain.com`)"
      service: certwarden
      tls:
        passthrough: true 
  services:
    certwarden:
      loadBalancer:
        servers:
          - address: "10.20.66.111:4055"

gregtwallace

Have you tried accessing it directly without going through the proxy?

I am not familiar with Traefik but definitely isolate if the issue is CW or the Traefik config you’re using to access it.

Let me know if you figure it out or have any other questions. 🙂

topcoffee4272

I removed the default cert and just used traefik to handle TLS. Unfortunately since certwarden is running in a docker container I didn't have a good way to route to certwarden

gregtwallace

What URL is it hitting when you get the 404?

topcoffee4272

gregtwallace mydomain.com through traefik. I had it pointed at 0.0.0.0:4055

gregtwallace

No URL path, just mydomain.com/ ?