My domain is: sys10.crabdance.com
I ran this command: Running a docker compose which creates 4 containers: nextcloud, jrcs/letsencrypt-nginx-proxy-companion, jwilder/nginx-proxy:alpine, mariadb
It produced this output: Everything was fine until june 6th and it looks like it wont do a cert renewal. When I go to the url the browser blocks it with NET::ERR_CERT_AUTHORITY_INVALID.
The letsencrypt portion of the docker-compose.yml has this:
I then ran "docker exec -ti jrcs/letsencrypt-nginx-proxy-companion bash" to enter into the container and run the start.sh (cant tell you what's in it as "nano" is not found in that container nor is "Apt" to install nano).
start.sh started running until it reached "Verifying: sys10.crabdance.com. it reported "Pending" 4 times then "sys10.crabdance.com:Verify error:65.110.xxx.xxx; Fetching http://sys10.crabdance.com/.well-known/acme-challenge/; Timeout during connect (likely firewall problem)
Please check log file for more details; /dev/null"
I would check that but not sure if that is referring to the letsencrypt container or the main nextcloud folder where docker compose is run from. If it's in the container I cant get nano to work and any other files found in /dev/null
If this helps - in my config.php I have a "trusted_domains" with an array listing both a local computer (192.168.x.x) and the sys10.crabdance.com.
My firewall has both http and https pointing to the correct ip where the service is running. It was also running properly before June 4th or 6th
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): Using Debian - terminal
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you're using Certbot): command not found
Not sure what other info you will need or where/what container to find it in and or how to read it if nano is not running within the container.