Revoke certificate configure in the old server

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: www.thaimedicalfurniture.com

I ran this command: sudo certbot --apache

It produced this output: Address already in use: AH00072: make_sock: could not bind to address

My web server is (include version):
apache2
The operating system my web server runs on is (include version): debian 6.1

My hosting provider, if applicable, is:
GCP
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):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): 2.1.0

I can not access to my old server that has the certificate install, I would like to revoke the old server and configure to the new one.

2

It's usually only necessary to revoke a certificate if it has been compromised.

There's no need to revoke the old one before getting a new one. You can have multiple simultaneously on different servers (or on the same server for that matter).

3 Likes
3

How can I install multiple simultaneously?

4

You can just replace one with another.

An Apache server replies to HTTPS requests but uses a certificate for the domain example.com

I see you have gotten Let's Encrypt certificates before. Your Apache is not using them.

What does this show?

sudo certbot certificates

And these

sudo apache2ctl -t -D DUMP_VHOSTS

sudo ss -pant | grep -Ei 'apache|httpd|:80|:443'
3 Likes
5

sudo certbot certificates
Saving debug log to /var/log/letsencrypt/letsencrypt.log

No certificates found.

sudo ss -pant | grep -Ei 'apache|httpd|:80|:443'
                                                           
LISTEN    0      511  *:443   *:*     users:(("httpd",pid=2348,fd=6),("httpd",pid=2017,fd=6),("httpd",pid=2016,fd=6),("httpd",pid=2015,fd=6))
LISTEN    0      511  *:80    *:*     users:(("httpd",pid=2348,fd=4),("httpd",pid=2017,fd=4),("httpd",pid=2016,fd=4),("httpd",pid=2015,fd=4))
6

sudo apache2ctl -t -D DUMP_VHOSTS
VirtualHost configuration:
*:80 wordpress-1-vm.asia-southeast1-a.c.thaimedicalfurniture.internal (/etc/apache2/sites-enabled/000-default.conf:1)

7

Usually on Debian Apache2 the user is "apache2"

Other systems use httpd but not usually Debian.

This error means Apache2 was not able to connect to (bind to) port 80 as it was already being used. It is being used by httpd which looks like a different install of Apache.

Can you explain more about how your system is configured

3 Likes
8

Already fixed.
The system is using bitnami package. So, It is fixed by use bitnami tool. Thank you very much

3 Likes