Unable to load QB homepage


#1

Hey, this has been such a terrible past few days! Please forgive the long post. :slight_smile:

When visiting my quickbox.io URL I receive “This site can’t be reached”.

I think I have accidentally updated my php or apache2 when I stupidly ran this command I found while trying to fix a Sonarr install issue I had (and have).

apt-get -y update && apt-get -y upgrade

I am on the latest v2.5.1 QB - When comparing the installs of my two QB servers - the broken one and my working one I can see they have different versions of php installed.

Broken:

 [[email protected]]:(27.5Mb)~$ php --version
 PHP 7.0.19-1+deb.sury.org~xenial+1 (cli) (built: May 11 2017 14:06:14) ( NTS )
Copyright (c) 1997-2017 The PHP Group
 Zend Engine v3.0.0, Copyright (c) 1998-2017 Zend Technologies
 with Zend OPcache v7.0.19-1+deb.sury.org~xenial+1, Copyright (c) 1999-2017, by Zend Technologies

Working:

 [[email protected]]:(421b)~$ php --version
 PHP 7.0.18-1+deb.sury.org~xenial+1 (cli) (built: Apr 11 2017 14:36:44) ( NTS )
 Copyright (c) 1997-2017 The PHP Group
 Zend Engine v3.0.0, Copyright (c) 1998-2017 Zend Technologies
 with Zend OPcache v7.0.18-1+deb.sury.org~xenial+1, Copyright (c) 1999-2017, by Zend Technologies

When running sudo service apache2 status, broken:

Warning: apache2.service changed on disk. Run ‘systemctl daemon-reload’ to reload units.
● apache2.service
Loaded: not-found (Reason: Not a directory)
Active: inactive (dead)

Working:

Warning: apache2.service changed on disk. Run ‘systemctl daemon-reload’ to reload units.
● apache2.service
Loaded: not-found (Reason: No such file or directory)
Active: active (running) since Wed 2017-05-10 02:59:42 UTC; 1 weeks 1 days ago
CGroup: /system.slice/apache2.service
├─ 9833 /usr/sbin/fcgi-pm -k start
├─ 9834 /usr/sbin/apache2 -k start
├─ 9835 /usr/sbin/apache2 -k start
├─ 9836 /usr/sbin/apache2 -k start
├─ 9837 /usr/sbin/apache2 -k start
├─ 9838 /usr/sbin/apache2 -k start
├─ 9840 /usr/sbin/apache2 -k start
└─11515 /usr/sbin/apache2 -k start

“sudo systemctl daemon-reload” results in no output/result.

So when I try and install or --reinstall apache2 I get this error:

[[email protected]]:(27.5Mb)~$ sudo apt-get install --reinstall apache2
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 167 not upgraded.
Need to get 0 B/86.7 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 233069 files and directories currently installed.)
Preparing to unpack .../apache2_2.4.18-2ubuntu3.2_amd64.deb ...
Failed to stop apache2.service: Unit apache2.service not loaded.
invoke-rc.d: initscript apache2, action "stop" failed.
Unpacking apache2 (2.4.18-2ubuntu3.2) over (2.4.18-2ubuntu3.2) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for systemd (229-4ubuntu17) ...
Processing triggers for ureadahead (0.100.0-19) ...
Setting up apache2 (2.4.18-2ubuntu3.2) ...
Failed to start apache2.service: Unit apache2.service not found.
invoke-rc.d: initscript apache2, action "start" failed.
● apache2.service
   Loaded: not-found (Reason: Not a directory)
   Active: inactive (dead)
Warning: apache2.service changed on disk. Run 'systemctl daemon-reload' to reload units.

Does anyone have any idea if I am on the right tracks?

Thank you for reading. :slight_smile:


#2

Stupid question but I have to check: Did you try rebooting after the update?


#3

I am also running updates & upgrades regularly, as far as I can tell, this has never been an issue and this makes me think there is more going on than a simple update. QuickBox shouldn’t break on these things, and especially in regards to a minor bump in PHP versions.

Another concern I have is your --reinstall of the apache service. This could easily interfere with your config files that are installed by QuickBox as I wouldn’t recommend performing a reinstall without first analyzing the real issue first.

What does la -l /etc/apache2/sites-enabled output. Also, had you simply tried to do box upgrade from your console to see if it replaces any borked files?


#4

Yeah, it’s been rebooted more than a few times since. :slight_smile:

I don’t recall doing anything other than upgrading Sonarr and then running that upgrade command afterwards.

I’ve also tried doing a box upgrade and it said it was already up-to-date.

The results of that command are:

[[email protected]]:(17.2Gb)~$ la -l /etc/apache2/sites-enabled
total 68
-rw-r--r-- 1 root     root     1598 Mar  7 04:50 000-default-le-ssl.conf
-rw-r--r-- 1 root     root     1069 May 18 19:31 aliases-seedbox.conf
-rw-r--r-- 1 root     root     1069 May 17 22:44 aliases-seedbox.conf.orig
-rw-r--r-- 1 www-data www-data  214 Apr 17 17:15 couchpotato.conf
-rw-r--r-- 1 root     root     1665 May 18 00:32 default-ssl.conf
-rw-r--r-- 1 root     root     1024 May 18 00:32 .default-ssl.conf.swp
-rw-r--r-- 1 www-data root      363 Mar  8 06:57 emby.conf
-rw-r--r-- 1 root     root      116 Mar  7 04:38 fileshare.conf
-rw-r--r-- 1 www-data www-data  218 Apr 22 11:36 jackett.conf
-rw-r--r-- 1 root     root      246 Apr 10 00:08 nextcloud.conf
-rw-r--r-- 1 www-data www-data  130 Apr 26 02:26 ombi.conf
-rw-r--r-- 1 www-data www-data  545 Mar 12 17:16 plex.conf
-rw-r--r-- 1 www-data www-data  199 Mar 12 17:32 plexpy.conf
-rw-r--r-- 1 www-data www-data  154 Mar 12 18:05 plexrequests.conf
-rw-r--r-- 1 www-data www-data  199 May 17 23:19 sonarr.conf
-rw-r--r-- 1 root     root      421 Mar 12 17:10 wut.console.conf
-rw-r--r-- 1 root     root      285 Mar  7 10:13 wut.rapidleech.conf

One thing I found odd was when I manually stopped all services running under my username, and then restarted rutorrent - When I tried to access the URL it would briefly load the empty rutorrent template, and then when refreshed it would return the “This site cannot be reached” message.


#5

Turns out I updated apache which wiped out the SSL certs etc. Never mind! :slight_smile:


#6

Yup, which is what I was trying to say when you said you had done the --reinstall. Glad/hopefully this got sorted out. If you notice something is still a bit off and can’t quite figure out the default configs, just let me know and I will gladly help you out where/when I can. :slight_smile: