@girish Thanks for the assistance.

Apparently this was caused by a misconfigured IPv6 / Ubuntu installation script which my host helped me diagnose and correct. Thank you for your help, I'm glad I stumbled upon Cloudron.

My previous Cloudron installation became corrupted so I've attempted to reinstall and restore from backup, however, during the restore it said "Run cloudron-setup with --version 5.2.4 to restore from this backup".

I tried "wget https://cloudron.io/cloudron-setup --version 5.2.4" and a few other variations with no luck and couldn't find any documentation on this topic. Any idea how to install 5.2.4 directly?

@girish said in Install Link 404 Error:

@woke You caught us in the middle of a transition of our server. Can you try again?

It is working now, thank you!

I am attempting to reinstall Cloudron on my VPS that became corrupted and I'm receiving a 404 error when attempting to install via: wget https://cloudron.io/cloudron-setup

41a5:~# wget https://cloudron.io/cloudron-setup
--2020-08-14 05:00:36-- https://cloudron.io/cloudron-setup
Resolving cloudron.io (cloudron.io)... 52.7.53.124
Connecting to cloudron.io (cloudron.io)|52.7.53.124|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2020-08-14 05:00:37 ERROR 404: Not Found.

@girish Unfortunately I have not... I tried the steps and continue to receive the same error. Thinking about just wiping the server at this point, not sure what else to try.

"Job for mysql.service failed because the control process exited with error code.
See "systemctl status mysql.service" and "journalctl -xe" for details."

2020-07-03T18:43:09.363989Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation$
2020-07-03T18:43:09.364473Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.30-0ubuntu0.18.04.1) starting as process 23208 ...
2020-07-03T18:43:09.369544Z 0 [Note] InnoDB: PUNCH HOLE support available
2020-07-03T18:43:09.369592Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-07-03T18:43:09.369601Z 0 [Note] InnoDB: Uses event mutexes
2020-07-03T18:43:09.369608Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2020-07-03T18:43:09.369614Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-07-03T18:43:09.369626Z 0 [Note] InnoDB: Using Linux native AIO
2020-07-03T18:43:09.369931Z 0 [Note] InnoDB: Number of pools: 1
2020-07-03T18:43:09.370205Z 0 [Note] InnoDB: Using CPU crc32 instructions
2020-07-03T18:43:09.372281Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2020-07-03T18:43:09.385584Z 0 [Note] InnoDB: Completed initialization of buffer pool
2020-07-03T18:43:09.392729Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-07-03T18:43:09.423982Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2020-07-03T18:43:09.425909Z 0 [ERROR] InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 517725298 and the end 517725184.
2020-07-03T18:43:09.425934Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2020-07-03T18:43:10.026710Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2020-07-03T18:43:10.026809Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2020-07-03T18:43:10.026828Z 0 [ERROR] Failed to initialize builtin plugins.
2020-07-03T18:43:10.026840Z 0 [ERROR] Aborting

I hadn't logged into the backend of my Cloudron in a month or so and there has been several automatic updates since then. I just tried and received the "Cloudron is offline. Reconnecting..." message constantly. I've reboot the VPS a couple times, and followed some instructions in https://cloudron.io/documentation/troubleshooting/#unreachable-dashboard with no luck yet.

Here's what I get from console after entering "systemctl status mysql.service":
● mysql.service - MySQL Community Server
Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2020-07-03 19:24:16 UTC; 2s ago
Process: 15803 ExecStart=/usr/sbin/mysqld --daemonize --pid-file=/run/mysqld/mysqld.pid (code=exited, status=1/FAILURE)
Process: 15780 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=0/SUCCESS)

Any suggestions?

@girish Thanks for the assistance.

Apparently this was caused by a misconfigured IPv6 / Ubuntu installation script which my host helped me diagnose and correct. Thank you for your help, I'm glad I stumbled upon Cloudron.

Here is what I received:
":~# curl -sL https://nodejs.org/dist/v10.18.1/node-v10.18.1-linux-x64.tar.gz | tar zvxf -

gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now"

So I just waited about 10 hours and then completely reinstalled Ubuntu 18.04LTS, went through the install setup again, and got stuck at the exact same spot.

"=> Installing base dependencies and downloading docker images (this takes some time) ...Init script failed. See /var/log/cloudron-setup.log for details"

I have a VPS with my hosting provider and just installed a fresh Ubuntu 18.04LTS OS, updated everything, and then followed the instructions to install Cloudron. For some reason, I keep getting an error during the same part of the install.

This is what the error says:
=> Installing base dependencies and downloading docker images (this takes some time) ...Init script failed. See /var/log/cloudron-setup.log for details"

Inside the log, at the bottom, I see this failure:
"# debconf-set-selection of unattended-upgrades/enable_auto_updates + dpkg-reconfigure does not work
cp /usr/share/unattended-upgrades/20auto-upgrades /etc/apt/apt.conf.d/20auto-upgrades

echo "==> Installing node.js"
==> Installing node.js
mkdir -p /usr/local/node-10.18.1
curl -sL https://nodejs.org/dist/v10.18.1/node-v10.18.1-linux-x64.tar.gz | tar zxvf - --strip-components=1 -C /us$

gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now"

Any idea what the cause is?