Solved LetsEncrypt not working when IPv6 is added

[Barend]

I found out that in DirectAdmin (evolution skin) when you add IPv6 adresses, no device (like eth0) gets associated with it.
In my case that was the reason let's encrypt could not generate a cert.

I solved this by adding the IPv6 adresses in the old 'enhanced' skin, where the device tick is on by default.

Steps to take:
- Can you ping the IPv6 address? (> PING -6 xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx)
- Is the AAAA record (IPv6) present in the DNS?
- Is the IPv6 adde to DirectAdmin at the Admin/Reseller level?
- Is the IP assigned to a reseller?
- Is the IP connected to a Device (see column 'Device')
- As a Admin/Reseller, have you added the IP to a website (User)? (will ping without this step)

 

[Barend]

Correction: In evolution skin the device tick is also on by default, but the 'ADD IP' button is grayed out, untill you uncheck it.
But if you check it again, you can still submit the form.

 

[Active8]

Enhanced skin is prem joke beside, still switching to this in my daily work. after using it for year still the best skin for admin

 

[Barend]

Agree, but Custombuild no longer supports Enhanced.