AllTube suddenly shows a 403 page

[micmc]

Hi folks

Anyone else experiencing this?

I use AllTube for quite along time however suddenly all I get is a "403 Forbidden" when I go its URL.
I haven't done anything particular, it seems as it just happened.

I've examined the log file and afaik it seems to be running okay as per the log.

Been trying to restart the app, though it seems to timeout as it does not feel like it wants to restart.

Trying to STOP and then START the app in the "uninstall" section, getting "Cloudron Error - No active task".

Going back into Repair section to try again with the Restart function. App restarts and "running" ...

Going to URL of the app, getting the "403 Forbidden" page again.

Here are the last lines of my log file, just after restarting the app, which is still showing as a 403 page.

Nov 26 13:11:07 + echo '=> Ensure directories'
Nov 26 13:11:07 => Ensure directories
Nov 26 13:11:07 + mkdir -p /run/sessions/ /app/data/templates_c/
Nov 26 13:11:07 + [[ ! -f /app/data/config.yml ]]
Nov 26 13:11:07 + sed -e 's,^youtubedl:.*,youtubedl: /usr/local/bin/youtube-dl,' -i /app/data/config.yml
Nov 26 13:11:07 + [[ ! -f /app/data/php.ini ]]
Nov 26 13:11:07 + echo '=> Ensuring permissions'
Nov 26 13:11:07 => Ensuring permissions
Nov 26 13:11:07 + chown -R www-data.www-data /app/data /run /tmp
Nov 26 13:11:07 + echo '=> Run alltube'
Nov 26 13:11:07 => Run alltube
Nov 26 13:11:07 + APACHE_CONFDIR=
Nov 26 13:11:07 + source /etc/apache2/envvars
Nov 26 13:11:07 ++ unset HOME
Nov 26 13:11:07 ++ '[' '' '!=' '' ']'
Nov 26 13:11:07 ++ SUFFIX=
Nov 26 13:11:07 ++ export APACHE_RUN_USER=www-data
Nov 26 13:11:07 ++ APACHE_RUN_USER=www-data
Nov 26 13:11:07 ++ export APACHE_RUN_GROUP=www-data
Nov 26 13:11:07 ++ APACHE_RUN_GROUP=www-data
Nov 26 13:11:07 ++ export APACHE_PID_FILE=/var/run/apache2/apache2.pid
Nov 26 13:11:07 ++ APACHE_PID_FILE=/var/run/apache2/apache2.pid
Nov 26 13:11:07 ++ export APACHE_RUN_DIR=/var/run/apache2
Nov 26 13:11:07 ++ APACHE_RUN_DIR=/var/run/apache2
Nov 26 13:11:07 ++ export APACHE_LOCK_DIR=/var/lock/apache2
Nov 26 13:11:07 ++ APACHE_LOCK_DIR=/var/lock/apache2
Nov 26 13:11:07 ++ export APACHE_LOG_DIR=/var/log/apache2
Nov 26 13:11:07 ++ APACHE_LOG_DIR=/var/log/apache2
Nov 26 13:11:07 ++ export LANG=C
Nov 26 13:11:07 ++ LANG=C
Nov 26 13:11:07 ++ export LANG
Nov 26 13:11:07 + rm -f /var/run/apache2/apache2.pid
Nov 26 13:11:07 + exec /usr/sbin/apache2 -DFOREGROUND
Nov 26 13:11:07 AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.18.61. Set the 'ServerName' directive globally to suppress this message
Nov 26 13:11:07 AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.18.61. Set the 'ServerName' directive globally to suppress this message
Nov 26 13:11:07 [Fri Nov 26 18:11:07.294542 2021] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.41 (Ubuntu) mod_perl/2.0.11 Perl/v5.30.0 configured -- resuming normal operations
Nov 26 13:11:07 [Fri Nov 26 18:11:07.294568 2021] [core:notice] [pid 1] AH00094: Command line: '/usr/sbin/apache2 -D FOREGROUND'
Nov 26 13:11:10 172.18.0.1 - - [26/Nov/2021:18:11:10 +0000] "GET /healthcheck HTTP/1.1" 200 173 "-" "Mozilla (CloudronHealth)"
Nov 26 13:11:20 172.18.0.1 - - [26/Nov/2021:18:11:20 +0000] "GET /healthcheck HTTP/1.1" 200 173 "-" "Mozilla (CloudronHealth)"
Nov 26 13:11:30 172.18.0.1 - - [26/Nov/2021:18:11:30 +0000] "GET /healthcheck HTTP/1.1" 200 173 "-" "Mozilla (CloudronHealth)"

from the above lines, it seems my apache2.pid gets removed(?), then apache gets to be executed to run again, then :
"Apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.18.61." ???

Anyone has any clue, anyone has experienced something in the like before?
Andy

[jdaviescoates]

@micmc I've vague memories of perhaps experiencing something similar in the past. I think in the end I just uninstalled and reinstalled the app and it was working again.

[micmc]

@jdaviescoates said in AllTube suddenly shows a 403 page:

@micmc I've vague memories of perhaps experiencing something similar in the past. I think in the end I just uninstalled and reinstalled the app and it was working again.

Yeah, that's exactly what I was thinking however it's always interesting to discover what the glitch caused the happens. And now that you are saying, I think I too have the vague impression that it happened before. lol TTYL

[girish]

@micmc are you able to reproduce this after clearing browser cache?

The logs seem quite bad, I am pushing a new package that will fix the logs.

[micmc]

@girish said in AllTube suddenly shows a 403 page:

@micmc are you able to reproduce this after clearing browser cache?

The logs seem quite bad, I am pushing a new package that will fix the logs.

Yeah, great stuff.
Yes, and I tried with other browsers as well.
I'd finally uninstalled and reinstalled to make to work. Just an absolutely weird glitch.