Cloudron Forum

https://github.com/minio/minio?tab=readme-ov-file

Whats the implication of that on its cloudron app ?

@nebulon Got a date in mind for the platform upgrade? the mobile is app, is janky / broken in its current state.

After some app update, I got a circle of doom please wait while indexing / hashing (a term I don't remember) ... ANyway it didn't ever finished and I restarted the phone for a different update. Opened immich again, & I had to reselect the "backup" folders with photos on my phone before they displayed again, and even then it only showed them as on local device, despite them being also on the server (confirmed via a web browser). mobile app seems a bit janky right now

No I didn't change any settings, just have automatic updates enabled, so thought that the updates had triggered the problem.
Yes thats correct, I'm not sure what the default setting is for email, and the only issue I can find is the health report error to do with queued jobs.

Did I do any other changes to get it working, or to break it ?
It was just failing to send invoices 1 september,
When I found the 404 error, and looked at the invoice ninja github, Ifound a similar issue logged by another user at the same time.
I found the other users attempt to run a php command to trigger the queue, which appeared to work in console, but made no difference to the health report screen. Also I added SCOUT_DRIVER=null to the env file.
It wasn't until I changed the email settings to use SMTP, and corrected the default email address of the admin account, to my actual address, that sending invoices again worked for me.

Because the default( which looked blank) stopped working, so I tried some other settings, because I needed to send invoices. otherwise I don't eat (lol).
Yes it works fine.

If you want I can turn on the ssh for support on my install to check the logs, etc ?
Basically I'm not sure why it stopped, or exactly when, it didn't become apparent until I tried sending an invoice, and it "bounced".
The upstream issue was similar but not identical.
Eventually I went to settings to specify the mail server, fixed an issue with the account I was using still having admin@cludron.local as an email address, and mail was successfully going out again. i thought this setting was blank previously, but honestly cannot recall exactly.
I also tried the command in the github issue

php artisan queue:work database --queue=scout

Seemed to run ok, but the queue is still the same

FYI still a problem for me, and the upstream issue isn't the same they make no mention of having an error in the queue, only that the queue doesn't clear.
Also they updated upstream to say it was fixed in .27

I've got my invoices and quotes working again, just have the queue error with a failed job.

Sorry, I saw cloudron had a patch for invoice ninja app, and I applied it and mistakenly assumed it was for that issue. I thought it would be fairly high priority, but apparently not.

Haven't been able to send invoices this month. Queued tasks grows every time I try.
Mail settings were blank, but when I select to use SMTP nothing sends either

I see theres been a patch for the app, but the problem still exists and resending the invoice just adds items to the stuck queue

Ok I found the queue has 30 failed jobs, last error...

Error: Call to a member function filter() on null in /app/code/app/Models/Client.php:430
Stack trace:
#0 /app/code/app/Services/Client/ClientService.php(213): App\Models\Client->currency()
#1 /app/code/app/Jobs/Ninja/CompanySizeCheck.php(65): App\Services\Client\ClientService->getCreditBalance()
#2 /app/code/vendor/laravel/framework/src/Illuminate/Collections/Traits/EnumeratesValues.php(240): App\Jobs\Ninja\CompanySizeCheck->App\Jobs\Ninja\{closure}()
#3 /app/code/app/Jobs/Ninja/CompanySizeCheck.php(72): Illuminate\Support\LazyCollection->each()
#4 /app/code/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(36): App\Jobs\Ninja\CompanySizeCheck->handle()
#5 /app/code/vendor/laravel/framework/src/Illuminate/Container/Util.php(41): Illuminate\Container\BoundMethod::Illuminate\Container\{closure}()
#6 /app/code/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(93): Illuminate\Container\Util::unwrapIfClosure()
#7 /app/code/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(37): Illuminate\Container\BoundMethod::callBoundMethod()
#8 /app/code/vendor/laravel/framework/src/Illuminate/Container/Container.php(662): Illuminate\Container\BoundMethod::call()
#9 /app/code/vendor/laravel/framework/src/Illuminate/Bus/Dispatcher.php(128): Illuminate\Container\Container->call()
#10 /app/code/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(144): Illuminate\Bus\Dispatcher->Illuminate\Bus\{closure}()
#11 /app/code/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(119): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}()
#12 /app/code/vendor/laravel/framework/src/Illuminate/Bus/Dispatcher.php(132): Illuminate\Pipeline\Pipeline->then()
#13 /app/code/vendor/laravel/framework/src/Illuminate/Queue/CallQueuedHandler.php(124): Illuminate\Bus\Dispatcher->dispatchNow()
#14 /app/code/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(144): Illuminate\Queue\CallQueuedHandler->Illuminate\Queue\{closure}()
#15 /app/code/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(119): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}()
#16 /app/code/vendor/laravel/framework/src/Illuminate/Queue/CallQueuedHandler.php(126): Illuminate\Pipeline\Pipeline->then()
#17 /app/code/vendor/laravel/framework/src/Illuminate/Queue/CallQueuedHandler.php(70): Illuminate\Queue\CallQueuedHandler->dispatchThroughMiddleware()
#18 /app/code/vendor/laravel/framework/src/Illuminate/Queue/Jobs/Job.php(102): Illuminate\Queue\CallQueuedHandler->call()
#19 /app/code/vendor/laravel/framework/src/Illuminate/Queue/Worker.php(439): Illuminate\Queue\Jobs\Job->fire()
#20 /app/code/vendor/laravel/framework/src/Illuminate/Queue/Worker.php(389): Illuminate\Queue\Worker->process()
#21 /app/code/vendor/laravel/framework/src/Illuminate/Queue/Worker.php(176): Illuminate\Queue\Worker->runJob()
#22 /app/code/vendor/laravel/framework/src/Illuminate/Queue/Console/WorkCommand.php(138): Illuminate\Queue\Worker->daemon()
#23 /app/code/vendor/laravel/framework/src/Illuminate/Queue/Console/WorkCommand.php(121): Illuminate\Queue\Console\WorkCommand->runWorker()
#24 /app/code/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(36): Illuminate\Queue\Console\WorkCommand->handle()
#25 /app/code/vendor/laravel/framework/src/Illuminate/Container/Util.php(41): Illuminate\Container\BoundMethod::Illuminate\Container\{closure}()
#26 /app/code/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(93): Illuminate\Container\Util::unwrapIfClosure()
#27 /app/code/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(37): Illuminate\Container\BoundMethod::callBoundMethod()
#28 /app/code/vendor/laravel/framework/src/Illuminate/Container/Container.php(662): Illuminate\Container\BoundMethod::call()
#29 /app/code/vendor/laravel/framework/src/Illuminate/Console/Command.php(211): Illuminate\Container\Container->call()
#30 /app/code/vendor/symfony/console/Command/Command.php(326): Illuminate\Console\Command->execute()
#31 /app/code/vendor/laravel/framework/src/Illuminate/Console/Command.php(181): Symfony\Component\Console\Command\Command->run()
#32 /app/code/vendor/symfony/console/Application.php(1096): Illuminate\Console\Command->run()
#33 /app/code/vendor/symfony/console/Application.php(324): Symfony\Component\Console\Application->doRunCommand()
#34 /app/code/vendor/symfony/console/Application.php(175): Symfony\Component\Console\Application->doRun()
#35 /app/code/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(201): Symfony\Component\Console\Application->run()
#36 /app/code/artisan(37): Illuminate\Foundation\Console\Kernel->handle()
#37 {main}

And also (I think the same error)
https://github.com/invoiceninja/invoiceninja/issues/11247

Since the last update / server reboot my sent invoices report they are bouncing.
When I open the invoice it says
Unable to send an email: 404 page not found (code 404)

Maybe the syncthing app doesn't re-test permission immediately? I went back to the folder, and the error was gone, syncthing says its "up to date" seems to have created its files ok.
Nothing got touched in the inbetween time. But its working now, so I'm happy with that result.
Thanks!

@joseph Seems strange to me, because theres another subfolder (music) that has cloudron permission, that the navidrome app uses. I don't remember having to change any folder permissions manually.
Also why doesn't the "volumes" page allow me to create folders and then change permission? I can create ok, but they always have root, and the menu for selecting another user permission displays I can select another user ie cloudron, hit the blue button, and nothing happens, no error, and the folder remains a root folder.

And I tried to "sudo chmod 777 sync" the folder, via ssh and it completes without error..but it remains a root only folder, and syncthing fails to create a file in it.

Theres also a 3rd folder backup, that has root permission but subfolders have cloudron permission and its used by the minio app. This has worked for a few weeks now.

Oh, I just rebooted it again, and it seems to be all services / apps are running.
Thanks

All my apps say configuring (queued)

aart@cloudron:/home/yellowtent/platformdata/logs$ systemctl status mysql
● mysql.service - MySQL Community Server
     Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2025-08-18 09:51:50 UTC; 45min ago
    Process: 876 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=0/SUCCESS)
   Main PID: 1010 (mysqld)
     Status: "Server is operational"
      Tasks: 43 (limit: 38208)
     Memory: 303.1M
        CPU: 14.762s
     CGroup: /system.slice/mysql.service
             └─1010 /usr/sbin/mysqld

Notice: journal has been rotated since unit was started, output may be incomplete.

How do I know what version it is?

I got it going again, with the cloudron-support --troubleshoot command
Thanks