Lost persistent storage can't get it back to work

[Hr46ph]

I had a working config for a long time but this week after migrating to new storage solution I lost all my persistent docker storage.

I use Portainer and I have config backups that was able to import. I have all my docker-compose yaml code.

I recreated all the paths, spun up nginx using the docker-compose from before. The first container I brought back was Duplicati, for secure cloud backups to S3. Unfortunately Nginx-proxy is not picking up the certificate like before and I see a bunch of error messages.

I'm not sure but I don't think it's useful to post the full acme logs and I'm afraid it will contain private info. Here's what I think is important (but ask me anything if I have left it out).

The nginx-proxy logs do not show errors or weird things (or at least I don't think they do). I just it starting worker processes and graceful shutdowns with exits.

Acme picks up the fqdn, I see

[Thu Jun  8 07:56:47 UTC 2023] code='201'
[Thu Jun  8 07:56:47 UTC 2023] original='{
  "status": "pending",
  "expires": "2023-06-15T07:56:47Z",
  "identifiers": [
    {
      "type": "dns",
      "value": "duplicati.internal.mydomain.net"
    }
  ],

Then I see a response, status pending, so far so good I guess.

I then see [Thu Jun 8 07:56:48 UTC 2023] ok, let's start to verify and [Thu Jun 8 07:56:48 UTC 2023] Trigger domain validation.. I see payloads and tokens, then trigger validation code: 200 and sleep 2 secs to verify followed by checking.

It then looks like it repeats some of that a few times. And then:

[Thu Jun  8 07:57:01 UTC 2023] code='200'
[Thu Jun  8 07:57:01 UTC 2023] original='{
  "type": "http-01",
  "status": "invalid",
  "error": {
    "type": "urn:ietf:params:acme:error:connection",
    "detail": "my-ext-ip: Fetching http://duplicati.internal.mydomain.net/.well-known/acme-challenge/blablabla: Timeout during connect (likely firewall problem)",
    "status": 400
  },
  "url": "https://acme-v02.api.letsencrypt.org/acme/chall-v3/blablabla",
  "token": "blablabla",
  "validationRecord": [
    {
      "url": "http://duplicati.internal.mydomain.net/.well-known/acme-challenge/blablabla",
      "hostname": "duplicati.internal.mydomain.net",
      "port": "80",
      "addressesResolved": [
0=7 1=7 2=. 3=1 4=7 5=4 6=. 7=3 8=4 9=. 10=5 11=8 
      ],
      "addressUsed": "my-ext-ip"
    }
  ],
  "validated": "2023-06-08T07:56:49Z"
}'

After that I see this:

[Thu Jun  8 07:57:02 UTC 2023] code='400'
[Thu Jun  8 07:57:02 UTC 2023] original='{
  "type": "urn:ietf:params:acme:error:malformed",
  "detail": "Unable to update challenge :: authorization must be pending",
  "status": 400
}

Now I see the timeout, and the path of that url. I don't quite understand that, Ive not changed the network config, that has all been restored with Portainer's backup. Duplicati is up and running and I have exposed the port (I can connect and use it via its own port as well).

I have no idea how to fix this back to its original working state. Any help will be greatly appreciated!

Thanks!

[Hr46ph]

Cool! I fixed it 😁

Redeploying Nginx-proxy I changed the container name, not realizing that would also change the network name. All docker-compose files had the old network name.