The renewal should have spun up a temporary web server to satisfy this request.
[as it did when you originally obtained the cert]
Something must NOT have been written down/remembered correctly about all those initial issuance parameters.
You can try to manually edit the corresponding renewal.conf file [not recommended at this point]
OR
rerun the renewal request and feed it all those "missing" parameters.
I appologize in advance for not having the exact syntax and options for you; as even to me
renew
--standalone
--dry-run
Seem to overlap/contratict/negate each other.
So I’m not exactly sure how to state your desired request so that certbot can understand what to do.
[I mean I do understand you but cerbot is real picky about options/orders/etc.]
Currently, the renew verb is capable of either renewing all installed certificates that are due to be renewed or renewing a single certificate specified by its name. If you would like to renew specific certificates by their domains, use the certonly command instead. The renew verb may provide other options for selecting certificates to renew in the future.
Also I forgot to add some more details - originally I didn't specify an external interface to use and cert bot showed me some other error. Verbose mode showed that certbot skipped IPv4 cause of the same error and used IPv6 insteed.
Asked me what to do (to keep the existing one or to renew). I selected option number 2 and it worked fine. Just added --dry-run at the end and got the same error with port 50080.
So I’m not the only one…
It seems counterintuitive that you take a “perfectly good running command” and just add “–dry-run” to it (just for testing), and it then returns some “you can’t do that because…” err msg.
Again I do apologize for not knowing this, I mean, not knowing how to get around this.
But there is a way - of that I am sure.
Let me search through some recent topics for similar “problems”…
Actually host machine indeed has this IP address. Several days ago I updated wsl up to the second version. Looks like microsoft changed networking part for it (https://github.com/microsoft/WSL/issues/4150) and wsl doesn't see this interface.