Let's Encrypt Problem

osloasn

I have configured it and confirmed that it is functioning. I can access the site using ports 80 and 443.

I just noticed that the file created earlier inside the acme challenge directory is gone.

root@mail:/opt/mailcow-dockerized# ls -lat data/web/.well-known/acme-challenge/
total 8
drwxr-xr-x 2 root root 4096 Apr 14 13:33 .
drwxr-xr-x 3 root root 4096 Apr 14 11:42 ..

I just noticed that the file created earlier inside the acme challenge directory is gone.

root@mail:/opt/mailcow-dockerized# ls -lat data/web/.well-known/acme-challenge/
total 8
drwxr-xr-x 2 root root 4096 Apr 14 13:33 .
drwxr-xr-x 3 root root 4096 Apr 14 11:42 ..

I just noticed that the file created earlier inside the acme challenge directory is gone.

root@mail:/opt/mailcow-dockerized# ls -lat data/web/.well-known/acme-challenge/
total 8
drwxr-xr-x 2 root root 4096 Apr 14 13:33 .
drwxr-xr-x 3 root root 4096 Apr 14 11:42 ..

I apologize for the triple post. I’m new to the community.

DocFraggle

osloasn I have configured it and confirmed that it is functioning. I can access the site using ports 80 and 443

To clarify: did you configure http after I asked if it’s enabled? Or was it already enabled?

DocFraggle

Is it a standard setup or are you using a reverse proxy?

osloasn

It is a standard setup.

osloasn

It was already enabled. I’ve been dealing with these issues for days.

DocFraggle

Ok, really strange… it’s all checking out ok in my eyes… DNS ok, http ok, Nginx responding for test URL

http://mail.lldmusatech.net/.well-known/acme-challenge/x

Any host or external firewall which may block Letsencrypt?

osloasn

None.

DocFraggle

Then I’m out of ideas… I guess you already tried restarting the stack it rebooting the server?

osloasn

Yes, I did.

It could be IPv6 that is causing it. I’m following the steps using this URL, but I’m stuck at the last step. I’m not able to find DISABLE_IPv6

https://docs.mailcow.email/post_installation/firststeps-disable_ipv6/

Disable IPv6 listeners for NGINX

Set DISABLE_IPv6=y in mailcow.conf

DocFraggle

osloasn Set DISABLE_IPv6=y in mailcow.conf

I guess this line is meant to be added to your mailcow.conf file.

But I doubt that your problem is based on IPv6, as it’s trying to validate the IPv4 address

osloasn

The internal Docker service is trying to communicate using IPv6. I know this because, when looking at the queue manager, the recipients column shows IPv6 being used (uploaded image).

FYI - I bypassed the HTTP verification.

DocFraggle

osloasn The internal Docker service is trying to communicate using IPv6.

So? This has absolutely nothing to do with the verification of an A record (=IPv4)

osloasn

Understood.

What I’m trying to say is that the service inside the Docker network environment is trying to use IPv6 instead of IPv4.

osloasn

The option I used to fix my issue was to disable the HTTP verification check.