thank you for taking the time to share, I actually moved over to nginx… all over the place >_> a few people have made it pretty clear I’m going to overwhelm caddy quickly with the number of different domains and sites we host so I’m starting over with nginx now.
yes nginx loads the page no problem, it’s nextcloud that’s throwing the error which is frustrating because there seems to be no way to tell nextcloud the location of config.php has changed (along with the rest of the root dir)
Hey everyone, [it's me again.](https://lemmy.world/post/24523007) I'm now on NGINX, surprisingly simple, not here with a webserver issue today though, rather a nextcloud specific issue. I removed my last post about migrating from Apache to Caddy after multiple users pointed out security issues with what I was sharing, as well as suggesting caddy would be unable to meet my complex hosting needs. Thank you, if that was you.
During the NGINX setup which has gone shockingly smoothly I moved all of my site root directories from /usr/local/apache2/secure to /var/www/
Everything so far has moved over nicely... that is until nextcloud. It's showing an "Internal Server Error" when loading up. When I check the logs in nextcloud/data/nextcloud.log it informs me nextcloud can't find the config.php file and is still looking in the old apache webroot. I have googled relentlessly for about four hours now and everything I find is about people moving data directories which is completely irrelevant. Does anyone know how to get F*%KING nextcloud to realize that config.php is in /var/www/nextcloud/config where it belongs? I'm assuming nextcloud has an internal variable to know where it's own document root is but I can't seem to find it.
Thanks for any tips.
Cheers
[nextcloud.log](https://privatebin.io/?b18c2032de4f5f59#HB9Aq6frnYQJSEuW6Nu2xB2XGc6qeVM5XN6g8GknBAr6) <- you can click me
Okay good feedback thank you I’ll look at nginx too. As far as the professional goes - unfortunately times are tough - budget is tight, but I will look into it long term to shore things up when we’re a little more settled. Going to have to do my best on my own for now.
Only thing I’m having trouble with so far is handling a line like this >
<FilesMatch \.php$> # Apache 2.4.10+ can proxy to unix socket SetHandler "proxy:unix:///run/php74-fpm.sock|fcgi://localhost/" </FilesMatch>
Not really sure how caddy handles this.
I appreciate the offer. If I get stuck I’ll dump it. If it’s as straight forward as everyone says I should be able to pull it off it looks so easy. Don’t want to make others do my work for me unduly.
We are a community oriented business and I really hate the big tech companies controlling the fate of my company. Lemmy seemed like one of a few easy alternative platforms where we were free from being stuck under the thumb of a tech giant or a ban away from loosing our members.
The only thing I can think of that might be interfering is HSTS? I’m not sure how acme is accessed when a browser can only access a site with ssl. Perhaps HSTS is interfering with the cert process somehow?
This is out of my skillset but I’m sure there’s documentation online I can check out to give it a shot. We use this server for our (very) small business so I’m trying not to jack anything up worse than it is but it seems like something I could potentially tackle. Thank you.
Thanks I’m gonna check this out first thing. I thought that was weird but I’m not sure what in httpd.conf could be interfering with the process. I will give the file a better read through and see what I can come up with - it’s a good starting point.
Just popping in this morning to thank everyone for their suggestions overnight. I have some stuff to look at now when I get to the office this morning. Can’t respond to every comment at the moment but I will. Just wanted to say thanks.
My friend chose it, he was old school. I don’t personally have a preference between the two but we use this server for our small business so I haven’t really wanted to risk messing everything up to switch when it’s (mostly) currently functional.
EDIT: Thanks everyone for your time and responses. To break as little as possible attempting to fix this I've opted to go with ZeroSSL's DNS process to acquire a new cert. I wish I could use this process for all of my certs as it was very quick and easy. Now I just have to figure out the error message lemmy is throwing about not being able to run scripts.
Thank you all for your time sincerely. I understand a lot more than I did last night.
--------
Original Post
--------
As the title says I'm unable to renew a cert on a self-hosted lemmy instance. A friend of mine just passed away and he had his hands all up in this and had it working like magic. I'm not an idiot and have done a ton of the legwork to get our server running and working - but lemmy specifically required a bit of fadanglin' to get working correctly. Unfortunately he's not here to ask for help, so I'm turning to you guys. I haven't had a problem with any of my other software such as nextcloud or pixelfed but for some reason lemmy just refuses to cooperate.
I'm using acme.sh to renew the cert because that's what my buddy was using when he had set this all up. I'm running apache2 on a bare metal ubuntu server.
Here's my httpd-ssl.conf:
https://pastebin.com/YehfTPNV
Here's some recent output from my acme.sh/acme.log:
https://pastebin.com/PESVVNg4
Here's the terminal read out and what I'm attempting to execute:
https://pastebin.com/jfHfiaE0
If you can make any suggestions at all on what I might be missing or what may be configured incorrectly I'd greatly appreciate a nudge in the right direction as I'm ripping my hair out.
Thank you kindly for your time.
thank you for taking the time to share, I actually moved over to nginx… all over the place >_> a few people have made it pretty clear I’m going to overwhelm caddy quickly with the number of different domains and sites we host so I’m starting over with nginx now.