Acme client can't listen on port 80 (interface is in the way?)

Software SW help
1

I want to connect to my router with an HTTPS connection. So I registered a domain name mydomain.com, pointed it to my router’s public IP, which works. Next, I downloaded the package luci-app-acme. I entered the below settings:

image
image1022×882 33.8 KB

I used my private Outlook address, and set the domain to mydomain.com. Considering how basic my DDNS provider is, I doubt I can use their API and so have left that field empty.

After starting the tool, I see this message in the logs:

Oct  2 06:39:40 turris acme: Running pre checks for mydomain.com.
Oct  2 06:39:40 turris run-acme[25943]: acme: Running pre checks for mydomain.com.
Oct  2 06:39:40 turris acme: mydomain.com: Cannot run in standalone mode; another daemon is listening on port 80.
Oct  2 06:39:40 turris run-acme[25943]: acme: mydomain.com: Cannot run in standalone mode; another daemon is listening on port 80.
Oct  2 06:39:40 turris acme: Disable other daemon or set webroot to continue.
Oct  2 06:39:40 turris run-acme[25943]: acme: Disable other daemon or set webroot to continue.

The message is pretty straightforward, and I assume it’s because the web interface (Foris and Luci) is running on that port already. Is this the case? And if so, how can I temporarily disable the web interface so that the Acme client can start listening on port 80, or change the webroot?

2

Solved it myself. In /etc/lighttpd/lighttpd.conf , uncomment server.port and set it to a different port (I used 8080). Then look a bit lower, and change the listen on IPv6 port to something else as well (I used 8080 again). After this, I called /etc/init.d/lighttpd restart. The web interface is now running on port 8080, so for me the address was 192.168.1.1:8080.

After this I opened a browser, went to the web interface with the new port, restarted the Acme client, and I got my first Let’s Encrypt certificate.