If you are installing your iriusRisk on-premises, you see that your nginx docker is not starting or getting automatically restarted, and you have the following error in the nginx logs:
nginx: [emerg] cannot load certificate key "/etc/nginx/ssl/star_iriusrisk_com.key": BIO_new_file() failed (SSL: error:8000000D:system library::Permission denied:calling fopen(/etc/nginx/ssl/star_iriusrisk_com.key, r) error:10080002:BIO routines::system lib)
Or:
nginx: [emerg] cannot load certificate "/etc/nginx/ssl/star_iriusrisk_com.crt": BIO_new_file() failed (SSL: error:8000000D:system library::Permission denied:calling fopen(/etc/nginx/ssl/star_iriusrisk_com.crt, r) error:10080002:BIO routines::system lib)
It could be due to the permissions that your key.pem or cert.pem have.
To solve it, you can execute the following command on your docker path:
sudo chmod 644 *.pem
You can also target to the specific file, like:
sudo chmod 644 key.pem
Or:
sudo chmod 644 cert.pem
Then, you can force the restart with:
docker restart iriusrisk-nginx
This way, your nginx docker will be able to access to the certificates and start function as a reverse proxy.
Comments
0 comments
Please sign in to leave a comment.