Cloudron Forum

I see now this is related to the recent change to the WordPress app.

This adds a button to my login page, I don't want that.

Can I disable somehow?

Is it possible to change an existing app from having Cloudron OpenID as the login method to using its own user management?

Particularly with WordPress?

"OpenID Connect Generic" showed up on my site as a recently as a plug-in.

Thanks @dsp76. I figured it was something like that.

It would be great to have a one-click Mautic Dev install, like we have for WordPress!

How can I setup a webhook from my Cloudron?

Is it possible to use Mautic's Webhook Bounce Management with Cloudron's built-in email server?

https://docs.mautic.org/en/5.x/channels/emails.html#webhook-bounce-management

I've been trying to install Mautic via the LAMP app and it seems like it won't work. Has anyone been able to do this successfully?

Looks like a cool project!

https://cap.so/

https://github.com/CapSoftware/Cap

Everything is working great right now! Thanks.

The error I posted is in the browser console.

I've been using the react version for months at this point. The recent update broke the Cloudron version.

I was able to switch back to the Flutter app by running the mysql command:

UPDATE accounts SET set_react_as_default_ap = 0;

However, it would be great to be able to access the react app again!

Updating to 1.12.15 my instance to stop loading (just a white screen when you go the URL).

I have updated to 1.12.16 but it did not fix the issue.

Upon loading the app I see this in the error log:

<!--

If you are reading this, there is a fair change that the react application has not loaded for you. There are a couple of solutions:

1. Download the release file from https://github.com/invoiceninja/invoiceninja and overwrite your current installation.
2. Switch back to the Flutter application by editing the database, you can do this with the following SQL

UPDATE accounts SET
set_react_as_default_ap = 0;

-->

Thank you, I updated and payment went through right away.

I wonder if recurring invoices I made before the first change you made were still billed twice but the new ones will only be billed once?

Do you think that is possible? I tried doing some daily test recurring invoices and they were not billed in duplicate.

@nebulon My recurring invoices are now not running at all.

Any ETA on this release?

(I use App Links with clients and is confusing to have the links not working.)

Thanks @nebulon. I have installed the update and will let you know when I have enough data. Fingers crossed.

@girish here is the most recent one

Mar 18 00:49:48 box:tasks update 713: {"percent":21,"message":"Uploading backup 25376M@1MBps (example.com)"}
Mar 18 00:49:58 box:tasks update 713: {"percent":21,"message":"Uploading backup 25386M@1MBps (example.com)"}
Mar 18 00:50:05 box:shell backup-snapshot/app_a64992c5-6f6d-401e-9edc-fa8d1f52adfa: /usr/bin/sudo -S -E --close-from=4 /home/yellowtent/box/src/scripts/backupupload.js snapshot/app_a64992c5-6f6d-401e-9edc-fa8d1f52adfa tgz {"localRoot":"/home/yellowtent/appsdata/a64992c5-6f6d-401e-9edc-fa8d1f52adfa","layout":[]} errored BoxError: backup-snapshot/app_a64992c5-6f6d-401e-9edc-fa8d1f52adfa exited with code 1 signal null
Mar 18 00:50:05 box:tasks setCompleted - 713: {"result":null,"error":{"stack":"BoxError: Backuptask crashed\n at runBackupUpload (/home/yellowtent/box/src/backuptask.js:163:15)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async uploadAppSnapshot (/home/yellowtent/box/src/backuptask.js:360:5)\n at async backupAppWithTag (/home/yellowtent/box/src/backuptask.js:382:5)\n at async fullBackup (/home/yellowtent/box/src/backuptask.js:503:29)","name":"BoxError","reason":"Internal Error","details":{},"message":"Backuptask crashed"}}
Mar 18 00:50:05 box:tasks update 713: {"percent":100,"result":null,"error":{"stack":"BoxError: Backuptask crashed\n at runBackupUpload (/home/yellowtent/box/src/backuptask.js:163:15)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async uploadAppSnapshot (/home/yellowtent/box/src/backuptask.js:360:5)\n at async backupAppWithTag (/home/yellowtent/box/src/backuptask.js:382:5)\n at async fullBackup (/home/yellowtent/box/src/backuptask.js:503:29)","name":"BoxError","reason":"Internal Error","details":{},"message":"Backuptask crashed"}}
Mar 18 00:50:05 box:taskworker Task took 6604.595 seconds
[no timestamp] Backuptask crashed

Thanks for this.

How do I apply the patch?

Here is a video explanation of the bug.

https://share.clientamp.com/MbSr7C7R

To investigate further, I performed an analysis of all the running processes on my system using the ps aux command.
Here are the relevant processes I found:

1. Queue Worker Process:

www-data 2129 0.0 0.3 194696 104424 pts/0 S 23:12 0:01 php /app/code/artisan queue:work database

This process is running the Laravel Artisan queue:work command with the database queue connection.

2. Schedule Worker Process:

www-data 37 0.0 0.3 192452 103156 pts/0 S 22:18 0:05 php /app/code/artisan schedule:work

This process is running the Laravel Artisan schedule:work command, responsible for executing scheduled tasks.

Apart from these processes, I found multiple Apache web server processes and a Supervisord process, which I don't think are related to the queue or InvoiceNinja application.

Is the presence of a single queue worker process and a separate schedule worker process expected in the standard InvoiceNinja setup on Cloudron?

Could the schedule worker process be contributing to the duplicate recurring invoices issue, or is it unrelated?

Are there any other processes or configurations I should investigate further to identify the root cause of the duplicate recurring invoices problem?

Thank you for your assistance and guidance in resolving this issue.