I’ve spent countless hours trying to get certbot to work for my application. I’m running a nodejs (Ubuntu Desktop 14.04) server in a virtual box at home. Eventually, it will need to serve https on port 4443. I’ve also registered for a duckdns sub-domain.
I can access my site through a browser locally and via my cell phone’s browser while connected to the cell network. I was able to do this in each of the scenarios below.
Initially, I ran in to the issue where I had to use iptables to take port 443 traffic to port 4443 (the port where my https app resides). The next issue I ran in to was… I was already using self-signed certs there and learned that was an issue. Then I figured out that certbot can also use port 80 and that it doesn’t try to validate existing certs when doing so and that it only needs access to a working port 80. Sooooo…I created a separate nodejs server on port 1337 to serve up a static page, setup iptables to send port 80 traffic to 1337 (random), and ran certbot using --standalone-supported-challenges http-01. I used standalone in all of the steps above.
The last error I’m getting via certbot is:
The following errors were reported by the server:
Detail: Invalid response from
Does this mean I need to serve up a static page at the route it is specifying in the error message? I’ve poured through docs most of the day resolving all of the issues mentioned above, and now I am here and don’t know what else to do.
Thanks in advance for any help that you can provide.