4 ms·
glad to see this posted. nginx has driven me crazy the past 4 days. After reading and reading and reading, and experimenting.. I have a feeling that when I ran
by stevenicr 5y ago
glad to see this posted. nginx has driven me crazy the past 4 days. After reading and reading and reading, and experimenting.. I have a feeling that when I ran lets encrypt certbot, it added some things in files that were needed, but became a problem when I actually made the config files that were needed to point to the new folders.. I'm still not sure actually.
I ended up just adding another domain name and configuring it from scratch to point to a matrix client folder, and then running the certbot expand.. and now it's working on a different domain.
Guides like this one posted are much more help trying understand the whole chain of things as opposed to a bunch of random pseduo answers via stackover and the like.
- nicolaslem 5y agoWe are what, 6 or 7 years after Let's Encrypt changed how we deal with certificates? The fact that nginx still requires the perfect incantation of certbot, cronjobs and whatnot is mind-boggling. I love nginx but it's hard to recommend it when other solutions exist that require zero fiddling and zero maintenance to get HTTPS working.
- clarents 5y agoWhat would you recommend?
- marginalia_nu 5y agoI really wish there was some better process than certbot for getting certificates. Feels sketchy as hell to have that thing running on my servers.