gosh, i only changed the language in the settings. needed to go to the user profile and made the switch. no wonder why thanks guys!

@girish So after the upgrade to 7.2.2 the problem vanished. Closing the Ticket. Thank you for the help!

@Lizzit right most likely this is the case, especially since it is hard for a system like Cloudron to correctly detect and fixup already made changes or package installations to fit its need for a stable update-able system. To maybe say this in advance, also after having installed Cloudron, it is not supported to install other things on the side, as it will eventually break on updates in our experience. Note that Cloudron is aiming for reducing the technical complexity for selfhosting and reduce time to maintain it, which requires some more stricter control of the system as such and we have decided on that route, since with the affordability of virtual servers it is likely much easier to just get a fresh Ubuntu rather than trying to debug configurations on updates.

@necrevistonnezr said in Nextcloud App "not responding" after upgrading to Ubuntu 22.04: EDIT: I guess that replacement should go into /home/yellowtent/box/src/infra_version.js - but after a restart of box, still not running... Yes, that's the correct place to fix it! I will add a warning to our docs that updating to ubuntu 22 when using FTS feature does not work out of the box / without patching until 7.3.

@humptydumpty I think not - https://askubuntu.com/questions/844689/instance-with-canonical-livepatch-service-requires-restart

@girish The MX record resolves to an ISPs server (Strato): smtpin.rzone.de But I don't know if this is particular timeout is domain specific or applies to all of strato. I'm worried it might be the former, at least protocol wise at the point of the delay the recipient domain is known and the server could apply domain specific settings for the backoff/delay.

@tuejon What you could do is setup proxmox an run 2 virtual machines on your server. One with cloudron one with whatever you want to do.

@girish Ah I didn't see this until too late, sorry. I had tried to start over to a degree by destroying the current backup disk and mounting a new disk instead then clearing out the backups history and seeing if that starts working better for me. So far so good, but if the issue comes back I'll certainly send the email out and enable remote support, as I agree there seems like some odd issue for sure.

@Dreamcatch22 I am fixing the docs to add the resolution of the other thread. About the "unable to resolve host" issue, that is just a warning. But to fix it, you have to make sure that your server's hostname (/etc/hostname) has an entry in the /etc/hosts . See https://askubuntu.com/questions/59458/error-message-sudo-unable-to-resolve-host-none for example on how to fix that.

@girish thank you! And thank you again for your prompt help!

@samaneha Which app do you want to migrate? The backups have the database dump and the data files. What else do you need to migrate?

@msbt We won't break it intentionally atleast.

That was the piece of information I was missing. Now it works perfect. How much time am I going to save updating WordPress Developer applications... Thank you @girish

@kubernetux Email needs to be configured for sending out email by apps. Do you not care if your apps are able to send emails (like password reset, reminders etc). If you don't, go to Email -> Select domain -> Outbound -> Select disabled. The notification will then go away.

Maybe there was some bug in our migration path. Will keep an eye out for related bug reports.

@robi said in Best way to update from Ubuntu 18.04 to 20.04?: one can use the -y option for apt to 'assume yes' to all prompts. this doesn't work with do-release-upgrade for whatever reason.

I've hit this problem after updating to 7.2.2 broke one of my volume mounts. No idea how to get the app out of the error state.

@Grafnus no you don't need to adjust anything on the image or manifest. When you install it from the appstore, you can set the ports in the installation settings.

@ei8fdb said in Cannot load certificate key .../_.sub.domain.org.key failed - No such file or directory: _.sub.domain.org.key One of the nginx config files is referencing this key. You can delete the config file and the key/cert file. You can find out which file is referencing it by grep'ing inside /etc/nginx/applications . Once deleted, you can systemctl restart nginx

@therealwebmaster If you mount it manually, use the Filesystem provider. Then, the backup path is simply /mounted-old-cloudron/var/backups/<timestamp>/box_<timestamp>_v<box_version>. See https://docs.cloudron.io/guides/download-backups/#backup-file-names for some hints.