@jdaviescoates so the folder is owned by root even after an app restart?

Just to note, it seems it was a timing issue, where the DNS in this case took longer than expected for full propagation.

Just to let anyone else know, I ran into the same issue with 7.2.0 when migrating servers and made the change that @girish mentioned and it still didn't work until I restarted docker (systemctl restart docker) and then it worked!

This was sorted out in support. The Stripe account associated with the customer got disconnected from our appstore account. This was caused by a bug which we have now fixed.

@girish That issue appears to have happened again two days ago... So originally on May 19th, but most recently I see occurrences of Temporary translation failure on May 20, 2022 around 11:50 PM Pacific Time. So it's definitely an infrequent issue, but appears to be recurring periodically.

This should be fixed with the next release. There were a couple of state issues which needed fixing.

This should now be fixed with next release. It will show 100+ in such a case.

@girish Thank you!! It worked with the version parameter!

@girish Then just expose a button for the Mail admins to be able to clear the queue

@alexdimarco said in Does cloudron block bogon networks?:

One of the wifi networks (I do not have control over) uses bogon IP space for addressing. When connected to this network I cannot access any Cloudron servers. Do they block bogon? If so, how can I white list a network - in specific 100.64.0.0/10?

Cloudron blocks nothing by default.

Thank you! Wait and see then ..

@wisameldin On the ubuntu 20 install, can you run the setup script again with ./cloudron-setup --redo ?

I think this is the same issue as:
https://forum.cloudron.io/topic/6660/help-please-failing-setup-of-cloudron

https://forum.cloudron.io/topic/6632/help-me-please-got-error-while-installing-the-cloudron-on-a-fresh-ubuntu-20-04-x64-server

https://forum.cloudron.io/topic/6561/that-install-script-fails-74-times-out-of-75

I tried to fix this with https://git.cloudron.io/cloudron/box/-/commit/bfb233eca19df07a82e3b524812d8270371ed738 but clearly it's not enough.

@robi Good point ... I think it's this way because one way to expand boxdata/appdata/platformdata is using symlinks. Then there's volumes , backups. So, it was easier to filter out by known filesystems.

As a hack, change the update schedule for every hour 😄

Related note: would be nice if we could display "the app is xx updates behind". We don't have an appstore API for this though.

Here we go : https://docs.cloudron.io/apps/#low-resource-warning

@girish the example command did the trick! I was not using the correct syntax but also I didn't specify the database name. Once I did that I was able to reach the Ghost mysql database from the Discourse app 🙂

@S0ulf3re I think the issues you are facing to related to DNS, so the box logs probably won't help.

As a first step to get the dashboard reachable again, ismy.domain.com pointing to Cloudron server IP? You can check host my.domain.com on your PC to verify what the DNS is configured as.

@girish That did the trick, I appreciate it.

@atridad yes it does. If you run cloudron --help you can see the "global" options on the top, which apply also to subcommands.