My site certificate only supports non-www addresses. So, when we try to access an image uploaded to the site we are getting a bad certificate warning because there is a ‘www’ in the address. Is there a solution for this?
My site certificate only supports non-www addresses. So, when we try to access an image uploaded to the site we are getting a bad certificate warning because there is a ‘www’ in the address. Is there a solution for this?
Its possible that certbot messed up something in your nginx config, but i dont see how that would affect the html sent by the server. Did you previously have www.beehaw.org set in docker-compose.yml? Maybe its still using the old setting.
Otherwise i cant think of anything.
I may have. I don’t know how it could retain the old setting. Strange. Thanks for helping.
You need to run
docker-compose upto reload the settings. Withdocker-compose restart, it keeps using the old settings.I think I may have found something. Instead of using ‘restart’ with nginx shouldn’t I be using ‘reload’? See: https://linuxize.com/post/start-stop-restart-nginx/
Either one should work. Anyway, this post shows that images are working correctly in new posts now. But you will have to edit old posts manually to remove the www from the url.
Thanks!
I’ve never used docker-compose restart. I always use docker-compose up.