Hi @bm1,
Thanks for using Bitnami. Can you tell us how are you running the tools? Can you try using sudo to gain elevated privileges? Apart from that, can you share with us the output of running the next commands?
sudo ls -lart /opt
sudo ls -lart /opt/bitnami
sudo ls -lart /opt/bitnami/bnsupport-tool
sudo /opt/bitnami/bnsupport-tool --help
sudo /opt/bitnami/bnsupport-tool --version
sudo /opt/bitnami/ctlscript.sh status
Thank you, gonggomra. Here are the commands I used (taken from your documentation):
sudo /opt/bitnami/bncert-tool
sudo /opt/bitnami/bndiagnostic-tool
In both cases the tool could not find the WordPress installation. I followed the prompt and tried various folders – / opt / opt/bitnami / opt/bitnami/wordpress – all to no avail
Output from your suggested commands below (IP address changed; I changed ‘bnsupport-tool’ to 'bndagnostic-tool).
Again, this is a brand new instance on AWS – I encountered these problems the first time I logged on with SSH.
Thanks for your help.
bitnami@ip-1-2-3-4:~$ sudo ls -lart /opt
total 12
drwxr-xr-x 3 root root 4096 Jan 3 18:06 .
drwxr-xr-x 19 root root 4096 Jan 4 12:32 …
drwxr-xr-x 19 root root 4096 Jan 4 12:33 bitnami
bitnami@ip-1-2-3-4:~$ sudo ls -lart /opt/bitnami
total 92
drwxr-xr-x 6 root root 4096 Aug 27 2020 brotli
drwxr-xr-x 4 root root 4096 Nov 2 17:26 gonit
lrwxrwxrwx 1 root root 46 Nov 9 18:13 bncert-tool -> /opt/bitnami/bncert/bncert-0.7.1-linux-x64.run
drwxr-xr-x 3 root root 4096 Nov 9 18:22 bncert
drwxr-xr-x 6 root root 4096 Dec 20 13:26 common
drwxr-xr-x 16 root root 4096 Dec 20 13:59 apache
lrwxrwxrwx 1 root root 59 Dec 29 18:26 bndiagnostic-tool -> /opt/bitnami/bndiagnostic/bndiagnostic-0.9.16-linux-x64.run
drwxr-xr-x 3 root root 4096 Dec 29 18:34 bndiagnostic
drwxr-xr-x 12 root root 4096 Dec 31 12:29 php
drwxr-xr-x 5 root root 4096 Jan 3 10:30 nami
drwxr-xr-x 10 root root 4096 Jan 3 12:01 varnish
-rw-r–r-- 1 root root 1332 Jan 3 12:01 .bitnami_components.json
drwxr-xr-x 3 root root 4096 Jan 3 18:06 …
drwxr-xr-x 12 root root 4096 Jan 3 18:06 mariadb
lrwxrwxrwx 1 root root 6 Jan 3 18:06 apache2 -> apache
drwxrwxr-x 14 bitnami daemon 4096 Jan 3 18:06 phpmyadmin
drwxr-xr-x 6 root root 4096 Jan 3 18:06 mysql
drwxr-xr-x 7 daemon daemon 4096 Jan 3 18:07 wp-cli
drwxr-xr-x 12 root root 4096 Jan 3 18:07 scripts
-rwxrwx— 1 bitnami root 109 Jan 3 18:07 properties.ini
-rwxr-xr-x 1 root root 1453 Jan 3 18:07 ctlscript.sh
drwxr-xr-x 6 root root 4096 Jan 4 12:32 var
drwxrwxr-x 6 bitnami daemon 4096 Jan 4 12:33 wordpress
-rw-r–r-- 1 root root 4 Jan 4 12:33 .firstboot.status
drwxr-xr-x 19 root root 4096 Jan 4 12:33 .
drwxr-xr-x 2 bitnami bitnami 4096 Jan 5 10:33 stats
bitnami@ip-1-2-3-4:~$ sudo /opt/bitnami/bnsupport-tool --help
sudo: /opt/bitnami/bnsupport-tool: command not found
bitnami@ip-1-2-3-4:~$ sudo /opt/bitnami/bndiagnostic-tool --help
Bitnami Diagnostic Tool 0.9.16
Usage:
–help Display the list of valid options
–version Display product information
–unattendedmodeui Unattended Mode UI
Default: none
Allowed: none minimal minimalWithDialogs
–optionfile Installation option file
Default:
–debuglevel Debug information level of verbosity
Default: 2
Allowed: 0 1 2 3 4
–mode Installation mode
Default: qt
Allowed: qt gtk xwindow text unattended
–debugtrace Debug filename
Default:
–installer-language Language selection
Default: en
Allowed: sq ar es_AR az eu pt_BR bg ca hr cs da nl en et fi fr de el he hu id it ja kk ko lv lt no fa pl pt ro ru sr zh_CN sk sl es sv th zh_TW tr tk uk va vi cy
–base_installdir <base_installdir> Bitnami directory
Default:
–mail_recipient <mail_recipient> Mail Recipient
Default:
–smtp_host <smtp_host> SMTP server hostname
Default: localhost
–smtp_port <smtp_port> SMTP server port
Default: 25
–smtp_user <smtp_user> SMTP user
Default: user@example.com
–smtp_password <smtp_password> SMTP user’s password
Default:
bitnami@ip-1-2-3-4:~$ sudo /opt/bitnami/bndiagnostic-tool --version
Bitnami Diagnostic Tool 0.9.16 — Built on 2021-12-29 15:17:27 IB: 21.6.0-202106241241
bitnami@ip-1-2-3-4:~$ sudo /opt/bitnami/ctlscript.sh status
apache already running
mariadb already running
php-fpm already running
bitnami@ip-1-2-3-4:~$
I’m having the same issue here. Waiting for an answer.
Yes, I saw, @joshfan. And this post is from seven days ago (end of Dec):
Looks like the sane problem.
Tempted just to buy a certificate but I assume this AMI configuration issue is likely to affect other things.
I got it working manually on an old version of bitnami stack, and it’s been working fine for a few years. I believe it’s just an issue with the latest version. Let’s just wait for an reply before doing it manually.
We checked the bndiagnostic tool on our side and it seems to be an issue with our recent images. Can you please update the /opt/bitnami/properties.ini file and add the next line right below the [General] section line?
installdir=/opt/bitnami
After that, running the bndiagnostic tool should work. If it does, please open a new “Technical issue” thread for your issue providing the generated code.
That fixed the problem. Thanks.
Thanks, gongomra.
I assume this will fix the BNCERT problem too?
Any idea when a patched AMI will be available?
B.
That did fix BNCERT problem as well. But then at the end of the run, it says “failed to renewed automatically”.
The certificates have been created, but my website is still not secure. I can not access .well-known file, docs about which are quite vague. Haven’t been able to make it work.
I also edited the file as suggested. I restarted all Bitnami services.
The BNCERT script ended with:
Performing changes to your installation
The Bitnami HTTPS Configuration Tool will perform any necessary actions to your
Bitnami installation. This may take some time, please be patient.
-Warning: Certificates may not renew automatically, due to a web server
configuration issue. For more information see:
…#certificates-not-renew
ed-automatically
Press [Enter] to continue:
Some errors occurred
The configuration was applied, but some of the changes could not be applied.
Find the details below.
The configuration report is shown below.
Failed steps:
If I now go to website.com I get the non-secure version (and no redirect to www, which I specified along with force HTTPS). If I go to https I can see that the certificate is the dummy testing one for ‘example.com’ and not the one for my domain.
I really need to get four sites running yesterday! Is there any way to access a previous AMI (NB another poster in the forums seven days ago seemed to have a similar problem – see above)?
Help would be appreciated. Thank you.
I’m having this same problem - I edited the properties.ini file to set up the installation directory and was able to continue with the SSL certificate installation, but the certificate generated is self-signed, and set up for example.com, and I also received the same warnings about automatic renewal. I’m considering switching to an older image just to get these sites stood up.
Can you guys try installing certificate manually? There’ s a document for that. I can only try after work hours as my domain has to be directed to the old instance during work hours.
BTW, not sure this thread is still being watched as the original problem has been fixed. You may have to start a new one.
Also guys, a new version has just been released about 3 hours ago. You may want to check that out. Not sure what problems it has fixed.
Same problem after following the steps mentioned above, still the SSL certificate was not generated and uploaded.
Some errors occurred
The configuration was applied, but some of the changes could not be applied.
Find the details below.
The configuration report is shown below.
Failed steps:
I will check if I can upload it manually. Meanwhile, yesterday, I tried to copy from old image of Bitnami package, BNCert tool was able to work perfectly.
Thank you so far for your help.
I have also updated the other forum. 
Ray
Renewal of SSL certificate is still not working, I tried to first check if whether the cert and key are there in the right place but all are fine.
/opt/bitnami/letsencrypt/certificates/shopdev.lalarayph.com.crt
Certificate details are correctly displayed
and also, in the SSL config, all are intact and consistent.
/opt/bitnami/apache2/conf/bitnami/bitnami-ssl.conf
SSLEngine on
SSLCertificateFile “/opt/bitnami/apache2/conf/shopdev.lalarayph.com.crt”
SSLCertificateKeyFile “/opt/bitnami/apache2/conf/shopdev.lalarayph.com.key”
All certs and keys are there, consistent
Restarted all services
sudo /opt/bitnami/ctlscript.sh restart
Source: https://docs.bitnami.com/aws/faq/administration/control-services/
Still not working
Please support further.
Thank you.
Ray
I removed the ‘Solution’ flag from the post above as it did not solve the underlying problem.
It would be great to have more support on this as it is impossible to set up a working instance at the moment.
Thank you.
The new version has not fixed this problem.
Hello all,
Thank you for reporting this issue. We have been able to reproduce this problem and our dev team is currently looking into it. We’ll update this thread with any news as soon as possible.
As a temporary workaround, you can configure the Let’s Encrypt certificate manually using our following guide:
https://docs.bitnami.com/aws/how-to/generate-install-lets-encrypt-ssl/#alternative-approach
Thanks for your understanding,
Fran de Paz
Hi, we have identified the problem reported in the first message of this topic, and released a new version of the bndiagnostic (0.9.17) and bncert (0.7.2) tools with a fix for the errors. If you launch the current version of the tool, it should detect the new version and attempt to download it.
If it doesn’t detect it, you can always download the bndiagnostic tool manually:
https://downloads.bitnami.com/files/bndiagnostic/0.9.17/bndiagnostic-0.9.17-linux-x64.run
md5: e813e84f0fad054e39eba4508157b489
And for bncert:
https://downloads.bitnami.com/files/bncert/0.7.2/bncert-0.7.2-linux-x64.run
md5: 7170b9d68641f5a045a5e6e4b5772a3a
NOTE: These versions of the tool will not fix any errors related to automatic renewal, only those errors related to the “The path does not seem to contain a valid Bitnami installation! Make sure you have proper access rights.” error.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.