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


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
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
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
svigneauS

svigneau

@svigneau
About
Posts
10
Topics
4
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Cloudron fails to start due to nginx failure linked to absent app certificate
    svigneauS svigneau

    This did the trick. Thank you so much!

    Support nginx certificates

  • Cloudron fails to start due to nginx failure linked to absent app certificate
    svigneauS svigneau

    Hi,

    After an automatic Cloudron update, my Cloudron dashboard became unresponsive, although individual apps kept working. I restarted the server to try and solve this issue, but Cloudron wouldn't start.

    This seems linked to nginx, as checking nginx status gives:

    > systemctl status nginx.service
    ● nginx.service - nginx - high performance web server
         Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
        Drop-In: /etc/systemd/system/nginx.service.d
                 └─cloudron.conf
         Active: failed (Result: exit-code) since Sat 2023-08-26 21:54:09 UTC; 3s ago
           Docs: http://nginx.org/en/docs/
        Process: 277464 ExecStart=/usr/sbin/nginx -c /etc/nginx/nginx.conf (code=exited, status=1/FAILURE)
    

    Testing nginx configuration gives:

    nginx -t
    nginx: [emerg] cannot load certificate "/home/yellowtent/platformdata/nginx/cert/jitsi.sebastienvigneau.xyz.cert": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/home/yellowtent/platformdata/nginx/cert/jitsi.sebastienvigneau.xyz.cert','r') error:2006D080:BIO routines:BIO_new_file:no such file)
    nginx: configuration file /etc/nginx/nginx.conf test failed
    

    How should I go from there?

    Support nginx certificates

  • After Cloudron upgrade to v8.3.1, postgresql fails to start with message 'root@postgres FATAL: role "root" does not exist'
    svigneauS svigneau

    Hi,
    After upgrading Cloudron to v8.3.1, the postgresql service (as well as multiple apps presumably depending on it) fails to restart and shows the following error message: 'root@postgres FATAL: role "root" does not exist.'
    How would you suggest to handle this?
    Best,
    Sébastien

    Support postgresql services

  • After Cloudron upgrade to v8.3.1, postgresql fails to start with message 'root@postgres FATAL: role "root" does not exist'
    svigneauS svigneau

    Thanks for asking! Here are the logs:

    Service postgresql
    Apr 01 09:19:55 ==> Detected existing installation
    Apr 01 09:19:55 ==> Copying updated config
    Apr 01 09:19:55 ==> Updating existing postgresql
    Apr 01 09:19:55 waiting for server to start....2025-04-01 13:19:55.095 GMT [15] LOG: skipping missing configuration file "/var/lib/postgresql/16/main/custom.conf"
    Apr 01 09:19:55 2025-04-01 13:19:55.095 GMT [15] LOG: skipping missing configuration file "/var/lib/postgresql/16/main/custom.conf"
    Apr 01 09:19:55 2025-04-01 13:19:55.268 UTC [15] LOG: starting PostgreSQL 16.6 (Ubuntu 16.6-0ubuntu0.24.04.1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0, 64-bit
    Apr 01 09:19:55 2025-04-01 13:19:55.268 UTC [15] LOG: listening on IPv4 address "0.0.0.0", port 5432
    Apr 01 09:19:55 2025-04-01 13:19:55.268 UTC [15] LOG: listening on IPv6 address "::", port 5432
    Apr 01 09:19:55 2025-04-01 13:19:55.370 UTC [15] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
    Apr 01 09:19:55 2025-04-01 13:19:55.557 UTC [18] LOG: database system was interrupted; last known up at 2025-04-01 13:18:53 UTC
    Apr 01 09:19:55 2025-04-01 13:19:55.857 UTC [18] LOG: database system was not properly shut down; automatic recovery in progress
    Apr 01 09:19:55 2025-04-01 13:19:55.928 UTC [18] LOG: invalid record length at 0/1550C80: expected at least 24, got 0
    Apr 01 09:19:55 2025-04-01 13:19:55.928 UTC [18] LOG: redo is not required
    Apr 01 09:19:56 2025-04-01 13:19:56.005 UTC [16] LOG: checkpoint starting: end-of-recovery immediate wait
    Apr 01 09:19:56 .2025-04-01 13:19:56.264 UTC [16] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.035 s, sync=0.055 s, total=0.316 s; sync files=2, longest=0.033 s, average=0.028 s; distance=0 kB, estimate=0 kB; lsn=0/1550C80, redo lsn=0/1550C80
    Apr 01 09:19:56 2025-04-01 13:19:56.321 UTC [15] LOG: database system is ready to accept connections
    Apr 01 09:19:56 done
    Apr 01 09:19:56 server started
    Apr 01 09:19:56 ==> Waiting for Postgres
    Apr 01 09:19:56 pg_ctl: server is running (PID: 15)
    Apr 01 09:19:56 /usr/lib/postgresql/16/bin/postgres "-D" "/var/lib/postgresql/16/main"
    Apr 01 09:19:56 ==> Postgres is running
    Apr 01 09:19:56 ==> Resetting root password
    Apr 01 09:19:56 2025-04-01 13:19:56.439 UTC [28] root@postgres FATAL: role "root" does not exist
    Apr 01 09:19:56 psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: FATAL: role "root" does not exist
    Apr 01 09:20:57 ==> Detected existing installation
    Apr 01 09:20:57 ==> Copying updated config
    Apr 01 09:20:57 ==> Updating existing postgresql
    Apr 01 09:20:57 waiting for server to start....2025-04-01 13:20:57.400 GMT [15] LOG: skipping missing configuration file "/var/lib/postgresql/16/main/custom.conf"
    Apr 01 09:20:57 2025-04-01 13:20:57.400 GMT [15] LOG: skipping missing configuration file "/var/lib/postgresql/16/main/custom.conf"
    Apr 01 09:20:57 2025-04-01 13:20:57.610 UTC [15] LOG: starting PostgreSQL 16.6 (Ubuntu 16.6-0ubuntu0.24.04.1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0, 64-bit
    Apr 01 09:20:57 2025-04-01 13:20:57.610 UTC [15] LOG: listening on IPv4 address "0.0.0.0", port 5432
    Apr 01 09:20:57 2025-04-01 13:20:57.610 UTC [15] LOG: listening on IPv6 address "::", port 5432
    Apr 01 09:20:57 2025-04-01 13:20:57.711 UTC [15] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
    Apr 01 09:20:57 2025-04-01 13:20:57.830 UTC [18] LOG: database system was interrupted; last known up at 2025-04-01 13:19:56 UTC
    Apr 01 09:20:58 2025-04-01 13:20:58.114 UTC [18] LOG: database system was not properly shut down; automatic recovery in progress
    Apr 01 09:20:58 2025-04-01 13:20:58.185 UTC [18] LOG: invalid record length at 0/1550CF8: expected at least 24, got 0
    Apr 01 09:20:58 2025-04-01 13:20:58.185 UTC [18] LOG: redo is not required
    Apr 01 09:20:58 2025-04-01 13:20:58.262 UTC [16] LOG: checkpoint starting: end-of-recovery immediate wait
    Apr 01 09:20:58 .2025-04-01 13:20:58.539 UTC [16] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.052 s, sync=0.052 s, total=0.333 s; sync files=2, longest=0.033 s, average=0.026 s; distance=0 kB, estimate=0 kB; lsn=0/1550CF8, redo lsn=0/1550CF8
    Apr 01 09:20:58 2025-04-01 13:20:58.595 UTC [15] LOG: database system is ready to accept connections
    Apr 01 09:20:58 done
    Apr 01 09:20:58 server started
    Apr 01 09:20:58 ==> Waiting for Postgres
    Apr 01 09:20:58 pg_ctl: server is running (PID: 15)
    Apr 01 09:20:58 /usr/lib/postgresql/16/bin/postgres "-D" "/var/lib/postgresql/16/main"
    Apr 01 09:20:58 ==> Postgres is running
    Apr 01 09:20:58 ==> Resetting root password
    Apr 01 09:20:58 2025-04-01 13:20:58.747 UTC [28] root@postgres FATAL: role "root" does not exist
    Apr 01 09:20:58 psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: FATAL: role "root" does not exist
    Apr 01 09:21:59 ==> Detected existing installation
    Apr 01 09:21:59 ==> Copying updated config
    Apr 01 09:21:59 ==> Updating existing postgresql
    Apr 01 09:21:59 waiting for server to start....2025-04-01 13:21:59.973 GMT [15] LOG: skipping missing configuration file "/var/lib/postgresql/16/main/custom.conf"
    Apr 01 09:21:59 2025-04-01 13:21:59.973 GMT [15] LOG: skipping missing configuration file "/var/lib/postgresql/16/main/custom.conf"
    Apr 01 09:22:00 2025-04-01 13:22:00.141 UTC [15] LOG: starting PostgreSQL 16.6 (Ubuntu 16.6-0ubuntu0.24.04.1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0, 64-bit
    Apr 01 09:22:00 2025-04-01 13:22:00.142 UTC [15] LOG: listening on IPv4 address "0.0.0.0", port 5432
    Apr 01 09:22:00 2025-04-01 13:22:00.142 UTC [15] LOG: listening on IPv6 address "::", port 5432
    Apr 01 09:22:00 2025-04-01 13:22:00.239 UTC [15] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
    Apr 01 09:22:00 2025-04-01 13:22:00.350 UTC [18] LOG: database system was interrupted; last known up at 2025-04-01 13:20:58 UTC
    Apr 01 09:22:00 2025-04-01 13:22:00.648 UTC [18] LOG: database system was not properly shut down; automatic recovery in progress
    Apr 01 09:22:00 2025-04-01 13:22:00.715 UTC [18] LOG: invalid record length at 0/1550D70: expected at least 24, got 0
    Apr 01 09:22:00 2025-04-01 13:22:00.715 UTC [18] LOG: redo is not required
    Apr 01 09:22:00 2025-04-01 13:22:00.798 UTC [16] LOG: checkpoint starting: end-of-recovery immediate wait
    Apr 01 09:22:01 .2025-04-01 13:22:01.033 UTC [16] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.035 s, sync=0.052 s, total=0.283 s; sync files=2, longest=0.031 s, average=0.026 s; distance=0 kB, estimate=0 kB; lsn=0/1550D70, redo lsn=0/1550D70
    Apr 01 09:22:01 2025-04-01 13:22:01.088 UTC [15] LOG: database system is ready to accept connections
    Apr 01 09:22:01 done
    Apr 01 09:22:01 server started
    Apr 01 09:22:01 ==> Waiting for Postgres
    Apr 01 09:22:01 pg_ctl: server is running (PID: 15)
    Apr 01 09:22:01 /usr/lib/postgresql/16/bin/postgres "-D" "/var/lib/postgresql/16/main"
    Apr 01 09:22:01 ==> Postgres is running
    Apr 01 09:22:01 ==> Resetting root password
    Apr 01 09:22:01 2025-04-01 13:22:01.217 UTC [28] root@postgres FATAL: role "root" does not exist
    Apr 01 09:22:01 psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: FATAL: role "root" does not exist
    Apr 01 09:23:02 ==> Detected existing installation
    Apr 01 09:23:02 ==> Copying updated config
    Apr 01 09:23:02 ==> Updating existing postgresql
    Apr 01 09:23:02 waiting for server to start....2025-04-01 13:23:02.267 GMT [15] LOG: skipping missing configuration file "/var/lib/postgresql/16/main/custom.conf"
    Apr 01 09:23:02 2025-04-01 13:23:02.267 GMT [15] LOG: skipping missing configuration file "/var/lib/postgresql/16/main/custom.conf"
    Apr 01 09:23:02 2025-04-01 13:23:02.468 UTC [15] LOG: starting PostgreSQL 16.6 (Ubuntu 16.6-0ubuntu0.24.04.1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0, 64-bit
    Apr 01 09:23:02 2025-04-01 13:23:02.469 UTC [15] LOG: listening on IPv4 address "0.0.0.0", port 5432
    Apr 01 09:23:02 2025-04-01 13:23:02.469 UTC [15] LOG: listening on IPv6 address "::", port 5432
    Apr 01 09:23:02 2025-04-01 13:23:02.562 UTC [15] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
    Apr 01 09:23:02 2025-04-01 13:23:02.669 UTC [18] LOG: database system was interrupted; last known up at 2025-04-01 13:22:01 UTC
    Apr 01 09:23:02 2025-04-01 13:23:02.931 UTC [18] LOG: database system was not properly shut down; automatic recovery in progress
    Apr 01 09:23:02 2025-04-01 13:23:02.998 UTC [18] LOG: invalid record length at 0/1550DE8: expected at least 24, got 0
    Apr 01 09:23:02 2025-04-01 13:23:02.998 UTC [18] LOG: redo is not required
    Apr 01 09:23:03 2025-04-01 13:23:03.080 UTC [16] LOG: checkpoint starting: end-of-recovery immediate wait
    Apr 01 09:23:03 .2025-04-01 13:23:03.339 UTC [16] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.035 s, sync=0.054 s, total=0.308 s; sync files=2, longest=0.033 s, average=0.027 s; distance=0 kB, estimate=0 kB; lsn=0/1550DE8, redo lsn=0/1550DE8
    Apr 01 09:23:03 2025-04-01 13:23:03.396 UTC [15] LOG: database system is ready to accept connections
    Apr 01 09:23:03 done
    Apr 01 09:23:03 server started
    Apr 01 09:23:03 ==> Waiting for Postgres
    Apr 01 09:23:03 pg_ctl: server is running (PID: 15)
    Apr 01 09:23:03 /usr/lib/postgresql/16/bin/postgres "-D" "/var/lib/postgresql/16/main"
    Apr 01 09:23:03 ==> Postgres is running
    Apr 01 09:23:03 ==> Resetting root password
    Apr 01 09:23:03 2025-04-01 13:23:03.508 UTC [28] root@postgres FATAL: role "root" does not exist
    Apr 01 09:23:03 psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: FATAL: role "root" does not exist
    Apr 01 09:24:04 ==> Detected existing installation
    Apr 01 09:24:04 ==> Copying updated config
    Apr 01 09:24:04 ==> Updating existing postgresql
    Apr 01 09:24:04 waiting for server to start....2025-04-01 13:24:04.545 GMT [15] LOG: skipping missing configuration file "/var/lib/postgresql/16/main/custom.conf"
    Apr 01 09:24:04 2025-04-01 13:24:04.545 GMT [15] LOG: skipping missing configuration file "/var/lib/postgresql/16/main/custom.conf"
    Apr 01 09:24:04 2025-04-01 13:24:04.916 UTC [15] LOG: starting PostgreSQL 16.6 (Ubuntu 16.6-0ubuntu0.24.04.1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0, 64-bit
    Apr 01 09:24:04 2025-04-01 13:24:04.917 UTC [15] LOG: listening on IPv4 address "0.0.0.0", port 5432
    Apr 01 09:24:04 2025-04-01 13:24:04.917 UTC [15] LOG: listening on IPv6 address "::", port 5432
    Apr 01 09:24:05 2025-04-01 13:24:05.016 UTC [15] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
    Apr 01 09:24:05 2025-04-01 13:24:05.143 UTC [18] LOG: database system was interrupted; last known up at 2025-04-01 13:23:03 UTC
    Apr 01 09:24:05 2025-04-01 13:24:05.485 UTC [18] LOG: database system was not properly shut down; automatic recovery in progress
    Apr 01 09:24:05 .2025-04-01 13:24:05.551 UTC [18] LOG: invalid record length at 0/1550E60: expected at least 24, got 0
    Apr 01 09:24:05 2025-04-01 13:24:05.552 UTC [18] LOG: redo is not required
    Apr 01 09:24:05 2025-04-01 13:24:05.700 UTC [16] LOG: checkpoint starting: end-of-recovery immediate wait
    
    Support postgresql services
  • Login

  • Don't have an account? Register

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