Cloudron Forum

@micmc aha - i'm iterating fast and pretty-much daily What you're getting, is what I'm using every day now, so it's all being refined from real-life use, and self-improving using the @agent-review subagent. I've added a ton for development workflow best-practice with git, to help anyone vibe-coding stay better organised and safer with their workflow. Issues and PRs welcome. It is all opinionated for the tools i work with most, but hopefully all self-explanatory enough to see how to extend for your own needs. I'm having a ton of fun with it. Hope you all enjoy the journey as much as I am. It really is becoming the dream team

Hello @luckow The error states access denied error. Can you please check if the database is accessible from the web terminal?

@LoudLemur Yeah AnythingLLM is amazing, I believe much cleaner and intuitive than Open WebUI. One can install it online as well via Coolify or EasyPanel and it's quite impressive out of the box too. Thanks for sharing this summary.

Big Love @d19dotca

@luisegundo can you not just "print to PDF" ?

Hello @luisegundo To get the PostgreSQL credentials of the nocodb app open the web terminal of the nocodb app: [image: 1765647416723-f1418f0e-ffb5-409b-9680-b28964c09c8a-image.png] In this terminal copy and paste the following command and press enter: printenv | grep -i POSTGRESQL You will get an output like this: CLOUDRON_POSTGRESQL_URL=postgres://user876d5ae64c9d44a4979aafbfffb68286:25025a6a57810a29ae4a052a416291bda191d339b63f129e42a512e07ba0b8f36fe6fccddbf3f1c15fd607d6d81d84ab9a1fee67547ff498890405a594d1bdd6@postgresql/db876d5ae64c9d44a4979aafbfffb68286 CLOUDRON_POSTGRESQL_DATABASE=db876d5ae64c9d44a4979aafbfffb68286 CLOUDRON_POSTGRESQL_PASSWORD=25025a6a57810a29ae4a052a416291bda191d339b63f129e42a512e07ba0b8f36fe6fccddbf3f1c15fd607d6d81d84ab9a1fee67547ff498890405a594d1bdd6 CLOUDRON_POSTGRESQL_USERNAME=user876d5ae64c9d44a4979aafbfffb68286 CLOUDRON_POSTGRESQL_HOST=postgresql CLOUDRON_POSTGRESQL_PORT=5432 Copy and save this output somewhere, you will need it later. Now in the metabase web UI I can add a database with the previous credentials. Tip, use the CLOUDRON_POSTGRESQL_URL and put in the Connection string (optional) field in Metabase and give it a descriptive display name instead of the long generated string db876d5ae64c9d44a4979aafbfffb68286: [image: 1765647679218-e02db919-16e8-4c93-9bd2-417281768c96-image-resized.png] Now I can access the NocoDB PostgreSQL database in Metabase: [image: 1765647746938-0c1362ae-2245-4a37-a241-26318225a2d0-image-resized.png] Is this what you needed?

Hello @vk182 @vk182 said in Hiding apps behind the proxy app to enable cloudron authentication: Can you please point me to the documentation on how this can be done? I understand now that and app updates itself, isn't it? I have done so already here said in Hiding apps behind the proxy app to enable cloudron authentication: I did a recent post about this, see: https://forum.cloudron.io/post/115963

Hello @imc67 You can use the PID from the process to figure out what mysql service it is. e.g. your iotop shows for mysqld the pid 1994756. You can run systemctl status mysql.service and there is the pid displayed: ● mysql.service - MySQL Community Server Loaded: loaded (/usr/lib/systemd/system/mysql.service; enabled; preset: enabled) Active: active (running) since Mon 2025-12-01 09:17:59 UTC; 1 week 5 days ago Main PID: 1994756 (mysqld) Status: "Server is operational" Tasks: 48 (limit: 4603) Memory: 178.7M (peak: 298.0M swap: 95.4M swap peak: 108.7M) CPU: 1h 41min 31.520s CGroup: /system.slice/mysql.service └─1994756 /usr/sbin/mysqld Notice: journal has been rotated since unit was started, output may be incomplete. So from iotop I can confirm that the system mysqld service is pid 1994756 so I'd know to inspect the system mysqld service and not the docker mysql service. You can also get the pid from the mysqld inside the docker container with docker top mysql: docker top mysql UID PID PPID C STIME TTY TIME CMD root 1889 1512 0 Nov07 ? 00:06:17 /usr/bin/python3 /usr/bin/supervisord --configuration /etc/supervisor/supervisord.conf --nodaemon -i Mysql usbmux 3079 1889 0 Nov07 ? 03:49:38 /usr/sbin/mysqld usbmux 3099 1889 0 Nov07 ? 00:00:11 node /app/code/service.js Then I know the mysqld pid of the docker service is 3079 which I can check again with the system: ps uax | grep -i 3079 usbmux 3079 0.4 1.0 1587720 43692 ? Sl Nov07 229:38 /usr/sbin/mysqld Now we can differentiate between the two. Okay. Now that we can differentiate between the two, you can observe iotop and see which one has a high I/O. After you narrow it down to either one, then we can do some analysis what database / table get accesses the most even further narrow it down.

Haven't been able to find a solution and just dealing with the notification of not using a CDN while using the S3 storage.

@Teiluj said in Stirling-PDF requires reinstallation: However, it does not gives me clarity on where things stands with regards to OIDC/SSO enabled instances, and which are now subject to the change. As far as I understand, the situation is that if you already have an oidc enable instance installed on your Cloudron, then you can keep it, but you won't get any more updates on it, that's all. Any new install will have the newer version with all the new restrictions.

@joseph said in Migrating a site from one cloudron instance to another.: For email, you can move mailbox by mailbox using imapsync. It's a hassle if you have a ton of mailboxes, right? It seems easier to move the apps over to the mailserver VPS and then transfer the entire Cloudron back.

@dylightful ok. it could be useful to follow @joseph advice, to try to reproduce issue... I had the same problem with Hetzner Storage Box via CIFS mount...

Hi @joseph, thanks for the assistance. Running the command above with --server mail.domain.com, I get "Network Unreachable". Running it with --server my.domain.com, I get "Connection Timeout". Under Email > Domain > Status, the outbound SMTP is green. The more I look into this, the more it seems that I would have to use mailjet directly instead of going through the outbound SMTP, but I am not sure if it's a good approach.