Cloudron Forum

Yes, the backups are on a remote storage.
The system now says:
Free space: 2.99 Go and /var/backups (Old Backups): 3.93 GB
I'd like to remove these old backups, how do I do it?

Good call on the backups saving location, I've set it up somewhere else yesterday.
Cloudron managed to create new backups last night and delete the old ones.
However, it's still failing to update to the next Baserow version. It seems that it creates a backup every time it tries, filling out the disk space and then it fails because there is not enough disk space.
Any idea of what I could do to fix this?

Yes exactly. Now, the app can also not create new backups. It seems to be keeping backups from Nov 15th onwards (when the backup policy is set to keep them 2 days only). I don't see how to delete specific backups to make more room nor why Cloudron doesn't manage to clear them.
Any chance we could hop on a call to figure this out?

I've retried the update, df says:

Filesystem 1K-blocks Used Available Use% Mounted on
overlay 30297152 27992580 2288188 93% /
tmpfs 65536 0 65536 0% /dev
shm 65536 16 65520 1% /dev/shm
/dev/root 30297152 27992580 2288188 93% /tmp
tmpfs 1974552 0 1974552 0% /proc/acpi
tmpfs 1974552 0 1974552 0% /proc/scsi
tmpfs 1974552 0 1974552 0% /sys/firmware

I am running into a similar issue, there is 2/3 of the content of a table I can not access (record lines are displayed in white with no content and I can't click on them). I can not figure out what the issue is and it makes some view of the table crash (but not others).
In Cloudron, Baserow has an error saying: FileSystem Error: failed to register layer: write /app/code/web-frontend/node_modules/node-sass/build/Release/obj.target/binding.node: no space left on device
It's failing to update to 1.29.2 (currently at 1.29.0).
Weirdly, I have 4Go of space left on my server and the update is about 1Go.

Is there another device I should look at?

I tried restoring it a number of times after giving more space to Postgresql and now it restarted again. For a while, Cloudron told me there was no DNS record pointing on the app (there was no modification there in the last months) and then it started working again.
What are the steps I can take so it doesn't happen again in the future?

Hello,

I've added a 70k records to a base in Baserow today. It was working alright (a bit slow, sure) but tonight it wouldn't let me access some tables and gave me error messages when trying to change rows in the tables I could access.

I tried increasing the memory with not much success. The graphs were showing I was quite under the limit but could not access a large part of my app.

When I tried restoring the back up, it gave me error 500, saying other users where accessing the app. Now it won't start, saying:

Nov 13 03:12:49 - ERROR (node:25) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
Nov 13 03:12:49 - (Use node --trace-deprecation ... to show where the warning was created)
Nov 13 03:12:50 => Healtheck error got response status 502

Can someone please help? I am out of my depth here

Thank you!

Super interested in the Budibase integration as well!

@girish thx.
So I entered systemctl status box. It said box.service - Cloudron Admin is active. Below it give me the error: Yellowtent : unable to resolve host ip-XXX-XX-XX-XXX: Name or service not known (the IP being my IPv4 address for ens5).

I entered systemctl restart box but nothing happened.

I ran /home/yellowtent/box/setup/start.sh and it seemed to have done what it was supposed to.

I asked again systemctl status box. It said box.service - Cloudron Admin is active. Below it gives me the same error: Yellowtent : unable to resolve host ip-XXX-XX-XX-XXX: Name or service not known (the IP being my IPv4 address for ens5).

The my.domain.com still remains unreachable.

Will be emailing you at support@cloudron.io shortly

Thank you for your reply

So the instance managed to restart and Docker as well. It looks like it's either Cloudron or Baserow that didn't reboot.
I can SSH into the server.
I doubled checked if my.domain.com resolves correctly and it doesn't.
I checked the status of nginx and it says it's active and running since we restarted the instance.
I don't understand what you mean with "box code"?
I entered: systemctl restart docker but nothing happened...

Any clue of what I could be missing?

Hey there,

With a DevOps colleague, we turned off the AWS EC2 instance on which Cloudron (and Baserow) is deployed to see if it would boot back up. It didn't. Both the my.domain.com (Cloudron dashboard) and the data.domain.com (Baserow) remain inaccessible several hours after our test.

Could someone please:

• Explain why this happened (happy to provide more details if need be)?
• Comment on whether Cloudron should reboot automatically or not?
• If not, detail what steps I should take to guarantee the system remains stable even in case of a crash?

Thank you for your help

@girish Ha ok, makes sense, will try setting up the relay and update the thread. Thx!

Hi everyone,

I've recently deployed Baserow on an AWS EC2 instance. Cloudron is telling me the PTR record needs to be adjusted. To do so, I've looked at the Cloudron documentation and the AWS documentation for Use reverse DNS for email applications.

I then did the following steps:

1. Created an elastic IP address for my instance
2. Made an A record in my Godaddy DNS for pointing "my" to the newly created elastic IP address
3. Made a reverse DNS record in the EC2 console for the elastic IP address

But I am still getting the PTR error on the Cloudron side.

Any clue what I might be missing?

Thank you for your help