SSL Certificate Error Bitnami

Help
1

Hello. I have a Bitnami LAMP 7.2.32-5 server, but I opened a new server with this version, Bitnami package for LAMP 8.5.0.

On the previous server in 2020, I was able to successfully complete my initial configuration using this tutorial: Generate and Install a Let's Encrypt SSL Certificate for a Bitnami Application

However, I'm now having trouble configuring the new server.

The commands I've entered are:

sudo /opt/bitnami/ctlscript.sh stop
sudo /opt/bitnami/letsencrypt/lego --tls --email="rmor23@gmail.com" --domains="www.mapjumpers.com" --path="/opt/bitnami/letsencrypt" run
2025/12/01 18:38:21 [INFO] [www.mapjumpers.com] acme: Obtaining bundled SAN certificate
2025/12/01 18:38:22 [INFO] [www.mapjumpers.com] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz/2833984606/619508292556
2025/12/01 18:38:22 [INFO] [www.mapjumpers.com] acme: authorization already valid; skipping challenge
2025/12/01 18:38:22 [INFO] [www.mapjumpers.com] acme: Validations succeeded; requesting certificates
2025/12/01 18:38:23 [INFO] [www.mapjumpers.com] Server responded with a certificate

Then I enter these commands:

sudo mv /opt/bitnami/apache/conf/bitnami/certs/tls.crt /opt/bitnami/apache/conf/bitnami/certs/tls.crt.old
sudo mv /opt/bitnami/apache/conf/bitnami/certs/tls.key /opt/bitnami/apache/conf/bitnami/certs/tls.key.old
sudo ln -sf /opt/bitnami/letsencrypt/certificates/mapjumpers.com.key /opt/bitnami/apache/conf/bitnami/certs/tls.key
sudo ln -sf /opt/bitnami/letsencrypt/certificates/mapjumpers.com.crt /opt/bitnami/apache/conf/bitnami/certs/tls.crt

Then I type:

sudo chown root:root /opt/bitnami/apache/conf/bitnami/certs/server*

And I get this error:

chown: cannot access '/opt/bitnami/apache/conf/bitnami/certs/server*': No such file or directory

Then I type:

sudo chmod 600 /opt/bitnami/apache/conf/bitnami/certs/server*

And I get this error:

chmod: cannot access '/opt/bitnami/apache/conf/bitnami/certs/server*': No such file or directory

I found these two links from people who have similar problems in the Forum:

In one of the threads, the moderator asks a user to type the command

ls -l /opt/bitnami/apache/conf/bitnami/certs/server*.

When I do this, I get the following:

`ls: cannot access '/opt/bitnami/apache/conf/bitnami/certs/server*': No such file or directory

Also, when I run the Bitnami Diagnostic tool, the Apache section shows me the following errors:

The Apache configuration has errors:

AH00526: Syntax error on line 18 of
/opt/bitnami/apache/conf/bitnami/bitnami-ssl.conf:
Press [Enter] to continue:
SSLCertificateFile: file '/opt/bitnami/apache/conf/bitnami/certs/tls.crt' does not exist or is empty.

Please check the configuration.

Can you help me solve this? Thanks in advance.

2

This isn't a problem with Let's Encrypt as it's returning a certificate (crt.sh | 22847729314) and the mv and ln commands are working. We can help a little bit though.

The ls command might be failing because permissions on the /opt/bitnami/apache/conf/certs directory -- or one of the parents of that directory -- are such that your normal user can't list the files. Remember that wildcard expansion is done by your shell (which is running as you), and not ls. However it will also fail if there are no files in that directory whose names begin with server -- and the ones covered in your description all start with tls -- tls.key, tls.crt and so on.

chown -R root:root /opt/bitnami/apache/conf/bitnami/certs will set the ownership on the directory and everything inside it, and that will work even if your user doesn't have permissions all the way down to certs.

The next issue is that the bitnami-ssl.conf file is trying to look for a certificate file in the /opt/bitnami/apache/conf/bitnami/certs directory, which is completely different to where your certs are.

Best to look at that configuration file and either modify it to point to where your certificates and keys are (/opt/bitnami/apache/conf/certs) or move them to where the configuration expects them to be.

It's good practice for the private key files to be mode 600 (owner read/write, no access to anybody else) but the certificates can be mode 644 (owner write, everybody read) as there is nothing sensitive in those.

4 Likes
3

You got good advice from @met24 and I don't want to get in the middle of that.

But, in the instruction link you posted it describes using bncert to get a cert. Yet, you skipped over that to the part for Alternative Approach

Why did you do that? I thought bncert was the generally recommended tool on Bitnami.

3 Likes
4

@MikeMcQ The thing is, the first time I used Bintami in 2020, for some reason I couldn't get the bncert-tool to work, so I switched to the alternative method, which worked fine and was easy at the time.

But now, when I used the alternative method in 2025, this second time it gave me this strange error.

1 Like
5

Thanks. I think @met24 described some problems with your procedure. Did those resolve your problem?

2 Likes
6

Hi everyone. I sent the question to someone from Bitnami's technical support and they replied with this: [<application>] <SSL Certificate Error Bitnami> · Issue #1872 · bitnami/vms · GitHub

I was able to resolve it, thanks for your help.

3 Likes