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.
I ran this command:
sudo nginx -t
nginx: [emerg] cannot load certificate “/opt/bitnami/nginx/conf/www.hellosfo.com.crt”: BIO_new_file() failed (SSL:
error:02001002:system library:fopen:No such file or directory:fopen(’/opt/bitnami/nginx/conf/www.hellosfo.com.crt’,
‘r’) error:2006D080:BIO routines:BIO_new_file:no such file)
nginx: configuration file /opt/bitnami/nginx/conf/nginx.conf test failed
My web server is (include version):VM instance in GCP.
The operating system my web server runs on is :
Debian Bitnami Nginx Wordpress on GCP VM instance
My hosting provider, is:Google Cloud Platform.
I can login to a root shell on my machine :yes
and I ls and have the following in my folder install
apps certbot-auto certbot-auto.1 stack
I’m not using a control panel to manage my site I SSH to VM in GCP or Gcloud CLI.
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): Cerbot-Auto ?
I would say, something happened to your cert file (moved, copied, permissions changed, …).
Does the file exist?
Please show out of: sudo ls -l /opt/bitnami/nginx/conf/www.hellosfo.com.crt
If it does exist, check the file permissions.
If it doesn't exist, do you have the private key?
If yes (private key), getting the current public cert for it is easy.
if no (private key), then start over - get a new key and cert.
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Error while running nginx -c /etc/nginx/nginx.conf -t.
nginx: [emerg] dlopen() “/opt/bitnami/nginx/modules/ngx_http_auth_pam_module.so” failed (/opt/bitnami/nginx/modules/ngx_http
_auth_pam_module.so: cannot open shared object file: No such file or directory) in /etc/nginx/modules-enabled/50-mod-http-au
th-pam.conf:1
nginx: configuration file /etc/nginx/nginx.conf test failed
The nginx plugin is not working; there may be problems with your existing configuration.
The error was: MisconfigurationError(‘Error while running nginx -c /etc/nginx/nginx.conf -t.\n\nnginx: [emerg] dlopen() “/op
t/bitnami/nginx/modules/ngx_http_auth_pam_module.so” failed (/opt/bitnami/nginx/modules/ngx_http_auth_pam_module.so: cannot
open shared object file: No such file or directory) in /etc/nginx/modules-enabled/50-mod-http-auth-pam.conf:1\nnginx: config
uration file /etc/nginx/nginx.conf test failed\n’,)
So as you can see it a conflicting configuration from many ongles:
I’m just can quite on this tray out project …this is not a production envirnment.
as you can see that Nginx very fragile into Debian image and you add to this Bitnami…without your SSH port configuration…and all this before Evan talking about AN SSL or CERT !!
since this just a tray out ENV I’m just can a leave it here…
look for an Easy setup Into GCP; what do think ?
Do you have a short cut-code to troubleshoot all that?
Yes you totally right;
the ssh machine was broken yeserday I deleted accidentally the rules and permissions in the edit file of my instance config GCP.
i have also miss-configured Apache and Nginx in my CONF file.
also i just let go chrome go and started FIREFOX…!!!
Remember all this happening in small virtual memory machine running Debian and those images they got bombard from left and right in a heavy traffic by the MN.
it make sense that crash will happen and accident will occur.
it will be worst if i was hosting those tools and apps locally …thanks God we are in the cloud ERA , and free!!
so what you think should i clean this NGINX mess and start over from scratch…or should i start with a new instance…?
i really don’t have any thing of value in this WordPress site, not even a custom *Theme!!
I would just blow it away and start it all brand new.
But hopefully you can make some changes that will help stop this from happening again.
[or you will be doing this all over again next week - lol]