Cloudron Forum

@girish this was a different Cloudron than the DNS MX issue which is still persisting ;-/

@ruihildt Updates to packages are rolled out slowly. So if a user tries to check for an update manually (i.e they click for 'check for updates') and they are not part of the rollout, they get shown that message. Generally, it is safe to update anyway but we are just being careful here.

@jdaviescoates said in "subdomain 'selfhost.cloud' is in use": use the File Manager Which is exactly what I did Actually the first time I used to nice new File Manager

@nebulon just for information - livepatch doesn't mean you don't have to reboot - it just lets you postpone that moment as convenient. For sync - a good practice on old good *nix is to issue sync twice before reboot - to make sure the buffers dumped for sure. On the reboot automation using third-party apps - it's doable; everything is, but why, if you can just add it inside of the system?

Yes, I think repair would work just fine. I'll give that a shot next time I run into this. The upgrade process makes sense, as you say, working on custom applications is a bit of a special usecase

@girish This solved it for me. Thanks!

@girish Thank you kindly!

@girish The manual check method is good enough for me. If you do the release channel thing thats cool. But for those of us that a hungry, an extra few clicks isn't a bother.