Could not update from 7.3.6 to 7.4.3

[fmbabacan]

Hello,

Cloudron running on AWS Lightsail and I got an error while I was adding redirection to Wordpress Developer Version App. I clicked the save button the app could not start again. I opened the log, firstly app's log:

Aug 06 23:42:26 box:shell reload (stdout): sudo: unable to resolve host ip-<my-private-ip>: Name or service not known

After than I went to Cloudron docs and I tried to update Cloudron, that will maybe repair system files. And I got the other error:

Aug 06 23:31:47 box:tasks startTask: 3365 done. error: {
stack: 'BoxError: Version info mismatch\n' +
' at verifyUpdateInfo (/home/yellowtent/box/src/updater.js:101:87)\n' +
' at downloadAndVerifyRelease (/home/yellowtent/box/src/updater.js:112:11)\n' +
' at processTicksAndRejections (node:internal/process/task_queues:96:5)\n' +
' at async update (/home/yellowtent/box/src/updater.js:144:25)',
name: 'BoxError',
reason: 'External Error',
details: {},
message: 'Version info mismatch'

So I can not start my Wordpress app and update Cloudron. Anyone have any ideas on this subject?

Best,

[robi]

Check your services, make sure unbound is running or restart it.

[nebulon]

You first error is just a warning, that the hostname is not resolving to the ip correctly. This can be ignored or you change the hostname to your dashboard domain. So there is likely some other error then with the app if it won't start after changing redirection.

Second the platform update, can you run systemctl restart box and manually check for updates again then perform it.

[fmbabacan]

@nebulon I just tried your solution for second error. But nothing changed. Can you connect and control this?

[nebulon]

We can take a direct look at it, if you enable remote SSH support as mentioned in https://docs.cloudron.io/support/#ssh-keys and send us a mail to support@cloudron.io with our public server IP and dashboard domain.

[fmbabacan]

@robi All services look working

[fmbabacan]

@nebulon I just sent an email. Thanks

[nebulon]

For others reading this: After looking at the WordPress instance, it appeared to have been hacked and someone placed suspicious includes in wp-config.php those made the app simply hang. Removing that brought it back, however in such situations, it is strongly advised to start fresh as we don't know what else may have been modified.