@girish Yeah, unfortunately won't work yet.
https://forum.cloudron.io/topic/8940/apps-with-openid-connect-provider-beta/13

Could it be that ip address of the instance changed the service is not able to resolve to the new ip address?

The AWS LightSail IP-Address had changed, I had to manually go to my Google Cloud DNS, and update the ip-address to new ip-address and do a DNS Sync for other apps to update the ip-address.

I am bit surprised that DNS sync wasn't automatic when the host ip-address had changed. Am I missing anything?

@jpodner I had the same issue. Solved it by following the instruction on this page to extend my LVM space.

https://packetpushers.net/ubuntu-extend-your-default-lvm-space/

@Jan-Macenka The sync dns also syncs the mail related dns settings. There should also be an event in the eventlog indicating the dynamic dns updated your dns (or not). When things are going out of sync, can you check what it says in the event log?

I don't see how this can be actually used for malicous action regarding the translations, since those are coming in a well-known format and from your server itself, so unless someone intercepts or changes that on the server, nothing much can happen (and if someone can do that, well there are other things one should be worried about)

If there are serious concerns around a real security issue, would be great to have that explained if someone is aware.

I guess the webterminal probably needs similar fix most likely.

This is intentional and hardcoded https://git.cloudron.io/cloudron/box/-/blob/master/src/cron.js#L6

If there is nothing to clean, this is a very cheap internal database lookup only.

Nice. Thanks!

@robi instead of clickable, the logs are unified now into a single stream (similar to app logs).

@jordanurbs With no proxying, does redirection to www work ?

SERVER! Not a plain old computer. Go back and reread https://docs.cloudron.io/installation/

carefully
fully
completely

when you come to something that you don't understand, come here and ask.
when you come upon terms that are new, google them, read up on them, learn about them.

after 1 month of doing this, THEN try to actually install and use Cloudron.

I have not used VMWare tools extensively, but I think you can do the below

Take a full Cloudron backups before you do anything. I think the best approach is to simply use VMware snapshots. Snapshot the VM. Move/copy the snapshot to the end destination and create a new VM again from snapshot. Depending on your setup, maybe the move/copy is redundant. As I said, I don't really know much about the VMware tools. Change the IP address of the dashboard my.cloudron.example to the new IP manually. i.e via your DNS provider. Start the the new VM. You should be able to visit my.cloudron.example already and login Once you visit, go to Domains -> Sync DNS. This will resync all the DNS entries with the new IP automatically.

That should be it, I guess.

If something goes bad, please let us know here and you can always start up the old instance immediately and continue.

@CRBear Yes, changes to those should work but they get overwritten on updates. Maybe you can just keep a copy of your changes for now and replace them after an update.

@ccfu oooh ok. The list won't become active until it hits a real box. Ok, that makes a lot more sense now. I appreciate it.

@linuxpowerhouse Did you check the upgrading instructions at https://docs.cloudron.io/guides/upgrade-ubuntu-20/ ?

@timconsidine for-free-adam-sandler.gif

Not meaning to dogpile on you @NoMan-0 , I just like the movies, the scene, the gif, and @timconsidine's post gave me reason to post it!!

@girish Perfect, that's where I went wrong, thanks.

Welp... I followed a few other posts about email not working, and found a file in the mail queue, removed it, restarted the mail... and now it works. I might delete all this... but I might leave it up as a suggestion to anyone else to do the same. At the very least, try restarting mail in the Dashboard.