My domain is:
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
My project is containerized along side caddy (version 2.2.1-alpine) and is orchestrated with docker swarm. It is running on a remote server from linode, using the docker app from the marketplace which runs debain 9. When I issue the docker deploy command, everything is working. However, inspecting the logs of caddy shows that it is not able to complete any of the challenges ([https://pastebin.com/eBHkn8DE](https://Link to full error log form docker service logs).
From inside of my remote server, I have tried to curl different letsencrypt urls and all of them are functional. From outside the server, I am able to see that both port 80 and 443 are open (When I am running my server) when I run nmap 22.214.171.124 or nmap mediacomune.com
Starting Nmap 7.80 ( https://nmap.org ) at 2020-11-13 12:03 AEDT Nmap scan report for mediacomune.com (126.96.36.199) Host is up (0.027s latency). Not shown: 997 closed ports PORT STATE SERVICE 22/tcp open ssh 80/tcp open http 443/tcp open https
So to me it seems that both ports are reachable from outside of the server and lets encrypt should be able to reach it. Lets debug results of my my domain name however, shows that AAAA and A are not working through either port.
When I checked my DNA and AAAA records on mxtoolbook it also showed the corrects ip address, so it seems that my A/AAAA records are functional. So I am lost as to why caddy cant issue the certificates. And why letsencrypt cant reach my sever.