This is related to Snap caddy https.
I’ve encountered a similar issue where I’ve assigned a Digital Ocean floating IP to a Droplet, and I’ve pointed my domain name to the floating IP. So, the value of curl ipinfo.io/ip doesn’t match dig <domain-name> |grep -A1 ";; ANSWER SECTION:" |tail -1 | awk '{print $5}'.
As a result, the following keeps failing:
$ sudo snap set rocketchat-server https=enable
error: cannot perform the following tasks:
- Run configure hook of "rocketchat-server" snap (run hook "configure": Error: Your public IP doesn't match the one resolved for caddy-url, disabling https ...)
To fix it, I have to use the IP of the Droplet in my DNS settings for my domain instead of the floating IP, which makes the floating IP useless.