How update the expire SSL certificate from Bitnami Google Cloud Platform?

Help
1

Hi sir

Thank you for your help
My domain:www.makerb2c.com
Google Cloud Platform
Bitnami
WordPress
the expire SSL certificate at 2019-4-1

Firstly, we have registered SSL by the link（https://docs.bitnami.com/google/apps/wordpress-pro/administration/generate-configure-certificate-letsencrypt/）. That tool uses lego to run the Let’s Encrypt certificate generation commands.
But not auto update after 90 days.So now the ssl overdue.

In few days, i find help from the link( https://www.onepagezen.com/free-ssl-certificate-wordpress-google-cloud-click-to-deploy/).
Done 3. Generate Certificates ,the follow error:

chintagentweb@wordpresspro-1-vm:~$ ./certbot-auto certonly --webroot -w /var/www/html/ -d makerb2c.com -d www.maker
b2c.com
Requesting to rerun ./certbot-auto with root privileges…
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for makerb2c.com
http-01 challenge for www.makerb2c.com
Using the webroot path /var/www/html for all unmatched domains.
Waiting for verification…
Challenge failed for domain www.makerb2c.com
Challenge failed for domain makerb2c.com
http-01 challenge for www.makerb2c.com
http-01 challenge for makerb2c.com
Cleaning up challenges
Some challenges have failed.
IMPORTANT NOTES:

the link is not succeed for update the SSL certificate.

Do you have some ways for the update the expire SSL certificate?

maybe, please help me

thanks

2

Hi @makerele

checking that tutorial there is something about Apache.

But checking your website ( https://check-your-website.server-daten.de/?q=makerb2c.com )

Domainname Http-Status redirect Sec. G
• http://makerb2c.com/
35.193.159.119 301 https://www.makerb2c.com/ 0.240 E
• http://www.makerb2c.com/
35.193.159.119 301 https://www.makerb2c.com/ 0.237 A
• https://makerb2c.com/
35.193.159.119 200 3.677 N
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
• https://www.makerb2c.com/
35.193.159.119 200 6.766 N
Certificate error: RemoteCertificateChainErrors
• http://makerb2c.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
35.193.159.119 301 https://www.makerb2c.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 0.240 E
Visible Content: 301 Moved Permanently nginx/1.14.1
• http://www.makerb2c.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
35.193.159.119 301 https://www.makerb2c.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 0.236 A
Visible Content: 301 Moved Permanently nginx/1.14.1
• https://www.makerb2c.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 404 5.203 N
Not Found

a nginx answers.

If you use certbot with webroot, you must find your correct webroot.

With Bitnami, this may be another path.

So find your correct webroot.

3

This may not be the correct webroot location.
To test, you can create the following:
mkdir /var/www/html/.well-known
mkdir /var/www/html/.well-known/acme-challenge
echo 'testing' > /var/www/html/.well-known/acme-challenge/1234

which should create a "test" file that should be accessible at:
https://www.makerb2c.com/.well-known/acme-challenge/1234

4

so sorry. Maybe, please help me. How find the correct webroot?

5

so sorry. Maybe, please help me. How find the correct webroot?

6

Check your config and the Bitnami documentation.

If you use Bitnami (I don't use it), there are different webroots possible.

7

I checked the webroot

chintagentweb@wordpresspro-1-vm:/ cd /opt/bitnami/apps/wordpress/htdocs chintagentweb@wordpresspro-1-vm:/opt/bitnami/apps/wordpress/htdocs dir
google1e3262ba2ef40190.html wp-activate.php wp-config-sample.php wp-load.php wp-trackback.php
index.php wp-admin wp-content wp-login.php xmlrpc.php
license.txt wp-blog-header.php wp-cron.php wp-mail.php
nginx.conf wp-comments-post.php wp-includes wp-settings.php
readme.html wp-config.php wp-links-opml.php wp-signup.php

right?

But again done
chintagentweb@wordpresspro-1-vm:~ cd /tmp/certbot chintagentweb@wordpresspro-1-vm:/tmp/certbot ./certbot-auto certonly --webroot -w /opt/bitnami/apps/wordpress/htdo
cs -d makerb2c.com -d www.makerb2c.com
Requesting to rerun ./certbot-auto with root privileges…
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for makerb2c.com
http-01 challenge for www.makerb2c.com
Using the webroot path /opt/bitnami/apps/wordpress/htdocs for all unmatched domains.
Waiting for verification…
Challenge failed for domain makerb2c.com
Challenge failed for domain www.makerb2c.com
http-01 challenge for makerb2c.com
http-01 challenge for www.makerb2c.com
Cleaning up challenges
Some challenges have failed.

IMPORTANT NOTES: - The following errors were reported by the server: Domain: makerb2c.com Type: unauthorized Detail: Invalid response from https://www.makerb2c.com/.well-known/acme-challenge/FRZhu-aVG5NvhLWtGs3Tnbuyv05CGhXpxCfOrZAwRIo [35.193.159.119]: “<html>\r\n<head><title>403 Forbidden</title></head>\r\n<body bgcolor=“white”>\r\n<center><h1>403 Forbidden</h1></center>\r\n<hr><center>” Domain: www.makerb2c.com Type: unauthorized Detail: Invalid response from https://www.makerb2c.com/.well-known/acme-challenge/vCLMHyPYXovTobHLq67ByimxuiKQc81zm-fdMJQZzDs [35.193.159.119]: “<html>\r\n<head><title>403 Forbidden</title></head>\r\n<body bgcolor=“white”>\r\n<center><h1>403 Forbidden</h1></center>\r\n<hr><center>” To fix these errors, please make sure that your domain name was entered correctly and the DNS A/AAAA record(s) for that domain contain(s) the right IP address.

8

chintagentweb@wordpresspro-1-vm:~$ mkdir /var/www/html/.well-known
mkdir: cannot create directory ‘/var/www/html/.well-known’: Permission denied

This command is denied.

so sorry. I’m a rookie. maybe, please help all steps.

thank again for help.

9

Hi @makerele,

To perform administrative tasks on a Unix system, you usually need to prefix them with sudo; this causes them to run as root (the system administrator account).

So for example, you can run sudo mkdir /var/www/html/.well-known instead of mkdir /var/www/html/.well-known to perform this task as root.

That’s the basis of the joke in this comic:

10

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