However, trying to enable HTTPS on the installation is not working and I cannot see anything in the logs to give me a clue as to what could be going wrong.
fullchain.pem and privkey.pem are in the certs directory, and I have chmod 770 them.
When I run docker-compose up, the Rasa X installation is available at the subdomain but not on HTTPS. I don’t see any SSL or HTTPS or .pem related errors in the logs when I run docker-compose logs.
How can I figure out why HTTPS isn’t working? Is there a log somewhere of some component that is looking for the certificate files or something?
From the instructions it seems as though HTTPS should just immediately work after copying the certificates, so I have no idea how to check on what should be happening and why it isn’t in this case.
Uncomment the line include /etc/nginx/conf.d/ssl.conf; in nginx-config-files/rasax.nginx.template
Uncomment the lines in nginx-config-files/ssl.conf.template AND adjust them to change the paths /etc/nginx/certs/{fullchain,privkey}.pem to /etc/certs/{fullchain,privkey}.pem.
After this, my Rasa X installation works through HTTPS.
@M_R_LY perhaps you could shell into the docker instance and double check that the file is where you think it is? The error says it can’t find the file at /etc/rasa/bot_support/certs/fullchain.pem so that location would be the first thing I would check.
indeed that was it.
i was specifying the wrong location, forgot that when you run docker-compose up -d command docker mounts certs folder in container according to what we wrote in docker-compose.yml as configuration in the nginx part. so instead of specifying the /etc/certs/fullchain.pem (the one in the container) i was referencing my /etc/rasa/bot_support/certs/fullchain.pem
Last question !! the certificate work only with mozilla ??? @justyn