Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:cloud.ecosprog.net and cloud.ecosprog.com
I ran this command: certbot --nginx
It produced this output: ailed authorization procedure. cloud.ecosprog.net (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://cloud.ecosprog.net/.well-known/acme-challenge/hloCeUiiDhJb4Q7Zy3nNZgiwe-Q04ZuLfiQjnLCYttc: Timeout during connect (likely firewall problem)
My web server is (include version): Nginx (nginx/1.14.0 (Ubuntu)) reverse proxy with Ubuntu 18.04 snap apps running Apache 2
The operating system my web server runs on is (include version): Bioth nginx reverse proxy and app servers are running Ubuntu 18.04
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don’t know): yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): no
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you’re using Certbot): certbot 0.31.0
I have tried to install certs on both app servers before without the reverse proxy and have had the same problem with the ACME challenge. All servers are hosted locally through a static IP and the whole setup works fine with self-signed certs. The port 80 and 443 traffic is forwarded through a fibre router and then through a router/firewall and as stated above this routing works currently with the self-signed certs installed.
Any help with this would be much appreciated.