I just set up Let's Encrypt for the first time, using the instructions provided: ./letsencrypt-auto --agree-dev-preview --server https://acme-v01.api.letsencrypt.org/directory auth During the install process, I got this error: The program apache2 (process ID 31582) is already listening on TCP …

Using ./letsencrypt-auto -d paulschreiber.com auto gives the same port-in-use warning as before.

You could use the docker version and change your apache configuration to proxy the verification requests to the webserver running in the docker container. I described something similar with nginx in another topic Also take a look at the webroot and manual modes in the documentation webroot: (–web…

[image] paulschreiber: I had to stop Apache, run LE, and start Apache again. i see same error/problem with nginx, on old git (28-october) webroot is the way.

Small typo, you use at the end of your line: ‘auto’. That must be ‘auth’.

@let’s encrypt dev-team: why not using a less essential port (e.g. 81 or 82) to provide the challenge code? Sure this will need some firewall and routing config, but in that case we could use the well-working standalone client for cert renewal while keeping our e.g. apache running for ports 80 and…

Or let us specify a port to issue the challenge code, so we could use these on NATed servers by setting up port forwarding appropriately.

Just generated my first cert and this is really intrusive, it doesn’t bind to a single IP either so if you have multiple webservers bound to different IPs then it forces you to close those too. Having the ability to bind to another port would be a great idea.

I propose to solve this issue as follows: Note: you may want to change 9999 to a different value make sure apache modules mod_proxy and mod_proxy_http are enabled a2enmod proxy proxy_http add the following to the mod_proxy config file (usually /etc/apache2/mods-enabled/proxy.conf) <If…

Thank you for your help. But in my case, I have to use 2 servers because LE is not supported by my nas so. My nas (syno) has a reverse proxy and redirects http requests on the port 9999 of my second server (ubuntu) On this server, I execute LE with your paramaters. But it doesn’t work and failed…

@mafiaman42 : please don’t hijack this thread in your specific case you probably need to make sure that your nas does the proxy redirection mentioned in step 2 above => but of cause not with http://127.0.0.1:9999/.well-known/acme-challenge/ as the target but with http://put-the-name-of-your-second-…

LE client needs to bind to port 80, which I'm already using

Help

Nemis November 3, 2015, 8:02am 5

i see same error/problem with nginx, on old git (28-october)
webroot is the way.

Topic		Replies	Views
Problems using letsencrypt-client in Beta Help	8	7857	October 30, 2015
Support for ports other than 80 and 443 Feature Requests	114	145508	December 19, 2017
Letsencrypt initial setup on ubuntu 16.04 (can't switch to port 80) Help	9	3496	December 22, 2016
I don't have a live directory in my letencrypt installation folder Aide (en français)	25	2213	July 22, 2022
TLS-SNI-01 Renew - Could not bind to port 80 Help	9	2320	February 22, 2019

LE client needs to bind to port 80, which I'm already using

Related topics