@colonelpanic said in Cloudflare Setup Questions: I assume that renewing the Let's Encrypt certificate would not be an issue with the proxy turned on because Cloudron is using a DNS challenge instead of HTTP challenge. Is that a true statement? Yes. Proxying can be left turned on, Cloudron will manage to get certs via DNS challenge. What would be the benefit of creating a Wildcard Origin Cert on Cloudflare and uploading it instead of using Let's Encrypt? AFAIK, there is no benefit. I think the wildcard origin cert is intended for cases where one cannot get a valid cert via DNS or HTTP automation (like some intranets that block outbound access).

@fbartels Thanks for the already asked link. The solution worked from the link: sudo growpart /dev/sda 3 sudo resize2fs /dev/sda3

yeah, I am not sure what changed on Cloudflare side, but we had to do this on our servers as well.

@hollosch

@mehdi Ohh didn't thought about that ! thanks a lot !

I was able to reproduce both issues, thanks for reporting! The proxy auth cookie secret is not persisted. It's stored in platform runtime data. I have migrated this into the database. Redirection logic was incorrect when the token is invalid. This is also fixed.

@robi I guess it could but the app doesn't (maybe for privacy reasons).

@solarsimon said in how extensive are backups?: I am sure you can make my worries disappear... @mehdi said in how extensive are backups?: @solarsimon Dumb question but ... have you tried in another browser, just to make sure it's not a cache problem ? no words. It had to be that simple. solved, or better erase

@msbt thanks so much. My interpretation of the fix suggested didn't work. I have posted a follow-up question there.

For future reference i managed to clear it up by using a slightly modified version of Girish's search command. It seems like the length limit applies to path length not just the filename length find . -type f -print|awk '{print length($0), $0}' | sort -n Went into the web interface and deleted / renamed files longer than 156 bytes and finally cleared trashbin/versioned files (wipes all deleted / old versions of files - careful): sudo -u www-data php -f /app/code/occ versions:cleanup sudo -u www-data php -f /app/code/occ trashbin:cleanup @robi @girish agreed it would be awesome if there was an automated way to handle this in the future

@msbt Thank you, that makes sense!

Amazing, and makes all the difference!

@mehdi this was indeed a bug in the restore code path. the setupToken, as you guessed, should be sent in the top level object and not as part of the backupConfig . Fixed now.

@girish great thanks, It works

Yes also from the graphs, the system is just running out of RAM and thus swaps like crazy causing all this CPU and disk I/O. So using those apps, you'd have to upgrade the droplets.

@nebulon I just added a new dns record on Namecheap manually. After this action, cloudron was able to add my second domain

@wisemetalhead whoops, I somehow missed this question. Not sure why the backup listing disappeared, I think we will have to investigate what happened using the logs. But since the backups itself are still there, you can use the CLI tool's cloudron import to restore (if needed).

@ei8fdb right the graphs don't update immediately, but every 6 hours or so. Otherwise, the disk spins a lot I will mark this thread as solved, but this problem will go away soonish. I think only ~20 apps are left to use the new base image. The 7.1 release also updates all the internal containers to use the latest image. Should all be done end of this month.

@girish no, I mean, like nothing ever happened in that it worked perfectly (via the interface, not CLI). Should have been more articulate in my response but was just so excited how easy it was!