Hi,
I have an old PC out in the shed running (L)Ubuntu that I use as a Nextcloud server (also Cherry Music and wife's backup, but it's Nextcloud that is vexing me). A few days ago my phone flashed a 'can't connect' warning from the calendar sync, so obviously I ignored it for a while. Then I tried connecting from my desktop Nextcloud client, and that failed too. I did some basic diagnostics and found:
1. Nextcloud is running, I can log in fine from the desktop using the LAN IP address of the server.
2. I use DDNS to route WAN connections and that's working fine because when I try to use Firefox to access the server I get a 401 error from Nginx. (What I should get is a Nextcloud login screen).
3. That's odd because as far as I was aware the server ran Apache.
4. Issuing status commands to Apache or Nginx doesn't get me anywhere.
5. sudo apt install apache2 reveals that I already have the latest.
6. sudo apt install nginx gives me a list of packages to install (I didn't) so I assume that means I was right about having Apache not Nginx. But that doesn't explain the Nginx 401.
7. sudo ps ux doesn't show Apache running.
8. Trying to start Apache doesn't work:
phil@webserver:/$ sudo service apache2 start Job for apache2.service failed because the control process exited with error code. See "systemctl status apache2.service" and "journalctl -xe" for details.
That would be fine if I had any clue where to look for those log files. And was likely to understand what they say.
So what I need (I think) is an idiot's guide to getting Apache running again that's easier than re-installing everything from scratch. Can anyone help?
On Sun, Oct 27, 2019 at 07:45:17PM +0000, Phil Thane wrote:
Hi,
I have an old PC out in the shed running (L)Ubuntu that I use as a Nextcloud server (also Cherry Music and wife's backup, but it's Nextcloud that is vexing me). A few days ago my phone flashed a 'can't connect' warning from the calendar sync, so obviously I ignored it for a while. Then I tried connecting from my desktop Nextcloud client, and that failed too. I did some basic diagnostics and found:
- Nextcloud is running, I can log in fine from the desktop using the LAN IP
address of the server.
- I use DDNS to route WAN connections and that's working fine because when
I try to use Firefox to access the server I get a 401 error from Nginx. (What I should get is a Nextcloud login screen).
That's odd because as far as I was aware the server ran Apache.
Issuing status commands to Apache or Nginx doesn't get me anywhere.
sudo apt install apache2 reveals that I already have the latest.
sudo apt install nginx gives me a list of packages to install (I didn't)
so I assume that means I was right about having Apache not Nginx. But that doesn't explain the Nginx 401.
sudo ps ux doesn't show Apache running.
Trying to start Apache doesn't work:
See below, there's an error in the apache configuration, or something.
phil@webserver:/$ sudo service apache2 start Job for apache2.service failed because the control process exited with error code. See "systemctl status apache2.service" and "journalctl -xe" for details.
That would be fine if I had any clue where to look for those log files. And was likely to understand what they say.
Do *exactly* what it says:-
systemctl status apache2.service
and/or:-
journalctl -xe
(at a command prompt) You *might* need to be root, but I think not as they work on my system without being root.
So what I need (I think) is an idiot's guide to getting Apache running again that's easier than re-installing everything from scratch. Can anyone help?
Run the above as the system told you and it may be obvious what's wrong, if not then show us what is says and I'm sure some guru here will know what the problem is.
-
Chris Green -
Phil Thane