Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

Cloudron Forum

Apps | Demo | Docs | Install

Cloudron Dashboard and Apps inaccessible after updating Cloudron to new version

Scheduled Pinned Locked Moved Solved Support
3 Posts 2 Posters 243 Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    Manas
    wrote on last edited by
    #1

    I update my Cloudron when I received an email from Cloudron team saying new version has been released.

    I hit reboot in the dashboard and after that I cannot access my dashboard or the apps anymore. When I tried using command line to check for errors as per the documentation, I understood that the disk has somehow filled up.

    I used this command "apt-get remove dpkg --list 'linux-image*' |grep ^ii | awk '{print $2}'\ | grep -v \uname -r``" and then rebooted the server.

    Running the command "/home/yellowtent/box/setup/start.sh" gave me this output.

    2021-11-17T03:26:02 ==> start: Cloudron Start
    media:x:500:
    2021-11-17T03:26:02 ==> start: Configuring docker
    Synchronizing state of apparmor.service with SysV service script with /lib/systemd/systemd-sysv-install.
    Executing: /lib/systemd/systemd-sysv-install enable apparmor
    Error response from daemon: network with name cloudron already exists
    2021-11-17T03:26:04 ==> start: Ensuring directories
    2021-11-17T03:26:04 ==> start: Configuring journald
    2021-11-17T03:26:04 ==> start: Setting up unbound
    2021-11-17T03:26:05 ==> start: Adding systemd services
    Synchronizing state of unbound.service with SysV service script with /lib/systemd/systemd-sysv-install.
    Executing: /lib/systemd/systemd-sysv-install enable unbound
    Synchronizing state of cron.service with SysV service script with /lib/systemd/systemd-sysv-install.
    Executing: /lib/systemd/systemd-sysv-install enable cron
    2021-11-17T03:26:10 ==> start: Configuring sudoers
    2021-11-17T03:26:10 ==> start: Configuring collectd
    2021-11-17T03:26:10 ==> start: Configuring logrotate
    2021-11-17T03:26:10 ==> start: Adding motd message for admins
    2021-11-17T03:26:10 ==> start: Configuring nginx
    Job for nginx.service failed because the control process exited with error code.
    See "systemctl status nginx.service" and "journalctl -xe" for details.
    

    The command journalctl -u nginx says there is an error with Nginx.

    Starting nginx - high performance web server...
    Nov 17 01:31:55 apokolips nginx[2125]: nginx: [emerg] cannot load certificate key "/home/yellowtent/platformdata/nginx/cert/_.manas.one.key": PEM_read_bio_Pri>
    Nov 17 01:31:55 apokolips systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
    Nov 17 01:31:55 apokolips systemd[1]: nginx.service: Failed with result 'exit-code'.
    Nov 17 01:31:55 apokolips systemd[1]: Failed to start nginx - high performance web server.
    Nov 17 01:31:55 apokolips systemd[1]: nginx.service: Scheduled restart job, restart counter is at 1.
    Nov 17 01:31:55 apokolips systemd[1]: Stopped nginx - high performance web server.
    

    This output keeps repeating itself.

    I hosted Nextcloud and Matrix. Thanks in advance.

    girishG 1 Reply Last reply
    0
  • girishG Do not disturb
    girishG Do not disturb
    girish Staff
    replied to Manas on last edited by
    #2

    @manas What is inside the certificate file that nginx is erroring? Is it an empty file or missing entirely?

    M 1 Reply Last reply
    0
  • M Offline
    M Offline
    Manas
    replied to girish on last edited by
    #3

    @girish I have removed that file. done sudo apt auto clean and rebooted the server.
    After reboot and runnning the /home/yellowtent/box/setup/start.sh
    command, everything worked again. That key was the issue.

    1 Reply Last reply
    0

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Login

  • Don't have an account? Register

  • Login or register to search.