Hi everyone, installed Freedombox on a $5 digitalocean droplet last night, connected it with my domain, installed the TinyTinyRSS app and enabled Let’s Encrypt with the domain. I imported my RSS feeds and everything was working fine when I went to bed. Today I woke up and got this message.
“Please wait for FreedomBox to finish installation. You can start using your FreedomBox once it is done.”
I get this message when accessing the server through its domain name, and it’s IP. Really not sure what’s happened here, as everything was definitely working fine when I went to bad. I can still ssh into the server, what do I need to type to make htat message go away and get access again?
@markonius My guess is, 1 day after setup, it checked for package updates and found some to be upgraded. This caused FreedomBox service (plinth) to run a setup script for an app. But it did not complete successfully, so it is stuck in a loop running the setup.
Please run sudo journalctl -u plinth and check if there is an error in the log.
Can’t login to via SSH now, I just get “Permission denied, please try again.”
I’ve deleted the server, and started a new one. If I get the same problem, what should I do? Using my SSH key to login to this one instead of the default account DigitalOcean creates for you
Hi are you still here? I get the same problem again when trying to update freedombox on a new server. I ran the command you said and this is the result
– Logs begin at Thu 2019-12-26 20:24:37 UTC, end at Sat 2019-12-28 16:45:56 UTC. –
Dec 26 20:32:23 HQ systemd[1]: Started FreedomBox Service (Plinth).
Dec 26 20:32:26 HQ /usr/bin/plinth[14411]: Configuration loaded from file - /etc/plinth/plinth.config
Dec 26 20:32:26 HQ /usr/bin/plinth[14411]: Script prefix - /plinth
Dec 26 20:32:26 HQ /usr/bin/plinth[14411]: AXES: BEGIN LOG
Dec 26 20:32:26 HQ /usr/bin/plinth[14411]: AXES: Using django-axes 4.4.0
Dec 26 20:32:26 HQ /usr/bin/plinth[14411]: AXES: blocking by IP only.
Dec 26 20:32:26 HQ /usr/bin/plinth[14411]: Module load order - [‘bind’, ‘coquelicot’, ‘quassel’, ‘firewall’, ‘names’, ‘config’, ‘syncthing’, ’
Dec 26 20:32:26 HQ /usr/bin/plinth[14411]: Executing command - [‘sudo’, ‘-n’, ‘/usr/share/plinth/actions/pagekite’, ‘is-disabled’]
Dec 26 20:32:26 HQ sudo[15227]: plinth : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/share/plinth/actions/pagekite is-disabled
Dec 26 20:32:26 HQ sudo[15227]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 26 20:32:27 HQ sudo[15227]: pam_unix(sudo:session): session closed for user root
Dec 26 20:32:27 HQ /usr/bin/plinth[14411]: Executing command - [‘sudo’, ‘-n’, ‘/usr/share/plinth/actions/pagekite’, ‘get-kite’]
Dec 26 20:32:27 HQ sudo[15414]: plinth : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/share/plinth/actions/pagekite get-kite
Dec 26 20:32:27 HQ sudo[15414]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 26 20:32:27 HQ sudo[15414]: pam_unix(sudo:session): session closed for user root
Dec 26 20:32:27 HQ /usr/bin/plinth[14411]: Executing command - [‘sudo’, ‘-n’, ‘/usr/share/plinth/actions/dynamicdns’, ‘status’]
Dec 26 20:32:27 HQ sudo[15587]: plinth : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/share/plinth/actions/dynamicdns status
Dec 26 20:32:27 HQ sudo[15587]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 26 20:32:28 HQ sudo[15587]: pam_unix(sudo:session): session closed for user root
Dec 26 20:32:28 HQ /usr/bin/plinth[14411]: Running first setup.
Dec 26 20:32:28 HQ /usr/bin/plinth[14411]: Setting up CherryPy server
Dec 26 20:32:28 HQ /usr/bin/plinth[14411]: Running setup for modules, essential - True, selected modules - None
Dec 26 20:32:28 HQ /usr/bin/plinth[14411]: Running module setup - firewall
Dec 26 20:32:28 HQ /usr/bin/plinth[14411]: [26/Dec/2019:20:32:28] ENGINE Listening for SIGTERM.
Dec 26 20:32:28 HQ /usr/bin/plinth[14411]: [26/Dec/2019:20:32:28] ENGINE Listening for SIGHUP.
Dec 26 20:32:28 HQ /usr/bin/plinth[14411]: [26/Dec/2019:20:32:28] ENGINE Listening for SIGUSR1.
Dec 26 20:32:28 HQ /usr/bin/plinth[14411]: [26/Dec/2019:20:32:28] ENGINE Bus STARTING
Dec 26 20:32:28 HQ /usr/bin/plinth[14411]: [26/Dec/2019:20:32:28] ENGINE Started monitor thread ‘_TimeoutMonitor’.
Dec 26 20:32:28 HQ /usr/bin/plinth[14411]: Executing command - [‘sudo’, ‘-n’, ‘/usr/share/plinth/actions/firewall’, ‘setup’]
Dec 26 20:32:28 HQ sudo[15814]: plinth : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/share/plinth/actions/firewall setup
Dec 26 20:32:28 HQ sudo[15814]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 26 20:32:28 HQ /usr/bin/plinth[14411]: [26/Dec/2019:20:32:28] ENGINE Serving on http://127.0.0.1:8000
Dec 26 20:32:28 HQ /usr/bin/plinth[14411]: [26/Dec/2019:20:32:28] ENGINE Bus STARTED
lines 1-34
Hi Markonius, still here? I have same problem after first update with stable version in Raspberry Pi 3 B, the upgrade setup goes in a loop. I have rebooted with brute force removing the power cord, and the problem has been fixed. Now I don’t know if this is going to cause other problems… but for now it works. I will try to find out what could have caused it by analyzing the log.