Some challenges have failed

Help
1

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command:
sudo certbot certonly -d homemiva.sytes.net --standalone --dry-run

It produced this output:
Could not bind TCP port 80 because it is already in use by another process on
this system (such as a web server). Please stop the program in question and then
try again.

My web server is (include version):
LAMP - Debian12 - Apche2 - Mariabd - PHP8.2

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

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):
no
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

Hello.
The problem I am facing is the following.

I have a LAMP web server on a debian machine with IP 192.168.1.100 and it is in production on port 80 without problem.

Now on another different machine I have installed another LAMP web server for another different application and the IP of that machine is 192.168.1.110, but in this case I am using port 8080 so that it does not conflict with the other server.

Everything is behind a router, and for name resolution, on both servers I use NO-IP.

I'm trying to generate the SSL certificates for this second server and I'm getting errors.

Domain: xxxxxxx.xxx.net
Type: unauthorized
Detail: 79.152.183.68: Invalid response from http://xxxxxxx.xxx.net/.well-known/acme-challenge/GbtnW3kjR9PvPq1ORg_L8Mm4_DzMxGh4VZoPJv0RiBY: 404

From my LAn I enter both servers, but the second one through the IP, and not the domain

It is as if entering from the WLAN trying to enter server 19.168.1.100 and or 192.168.1.110

Greetings

2

Hi @fgm,

Did you do what I’ve quoted above?

1 Like
3

Yeah
I stopped server 1 and tried, but it says the same thing.

4

Then there is still some process owning Port 80; whatever that process is it needs to release Port 80.
Typically stopping the process does that.

1 Like
5

Generally, if you have Apache running you use the --apache or --webroot method to get the cert. Not --standalone.

Was there a particular reason you chose that?

Also, how do you plan to access these two domain names? That is, should they both be available on the public internet or are these just for your private network use?

Because it may be easier to choose one of them to respond to all requests from the internet and proxy specific requests to the other server.

3 Likes
6

Hello.
I must be able to access both from WLAN

I have tried both things.
On the one hand, make server 2 the CNAME of server 1 and use a reverse proxy, and it has not worked.

I have also tested my domain on server 2 with domain A and it also gives me an error.

7

For the proxy, you would have A records (and/or AAAA records) for both domains which point to the same IP. If you have a router you send all arriving requests to your chosen server (say, server1).

Then, in server1 you have two VirtualHosts. One for each domain name. Server1 handles requests for itself and proxies requests for the other domain to server2.

You should work to get this working using HTTP first and then add certs for HTTPS after. We are not a support forum for Apache. You may want to review their docs or Apache support forums on how to setup reverse proxy. Your server setup is not unusual you should be able to find good advice.

Once it is working you will be able to get certs for both domain names by running Certbot on server1

3 Likes
8

You may be right and I have the problem with my Apache configuration.

I apologize.
I will investigate.

Thank you so much.

2 Likes
9

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.