This issue is impacting us on a migration. We can't get the migration to work because the cron is not running on the target server.

Should we just create a user or two and hope the cron starts runing?

Confirmation of resolution. Issue is fixed.

@nebulon - Sorry for the late reply, its been chaos here. It's possible it could have been an update, we don't actually bill very often, so it may have been down for days with no one noticing.

We have gone to backup, and the site is responding, but now none of our logins work. Says 401: bad credentials.

If we try to password reset we get 500: Server Error.

We tried restores both from Digital Ocean and from inside Cloudron. Now that it is back up, can someone walk me through hacking a set of creds via MySQL or something to back in?

App went to not responding and I have tried everything to get it back via the GUI. Nothing works.

Any help DEEPLY appreciated here. Our whole business is ridin on this one. If we don't get this back we will effectively be toast, as unravelling it will cost too much.

This is the full error from the logs. This sequence just keeps repeating:

In Connection.php line 485:
Sep 28 15:08:38
Sep 28 15:08:38 [PDOException (42S01)]
Sep 28 15:08:38 SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'recurring_e
Sep 28 15:08:38 xpenses' already exists
Sep 28 15:08:38
Sep 28 15:08:38
Sep 28 15:08:38 Exception trace:
Sep 28 15:08:38 at /app/code/vendor/laravel/framework/src/Illuminate/Database/Connection.php:485
Sep 28 15:08:38 PDOStatement->execute() at /app/code/vendor/laravel/framework/src/Illuminate/Database/Connection.php:485
Sep 28 15:08:38 Illuminate\Database\Connection->Illuminate\Database{closure}() at /app/code/vendor/laravel/framework/src/Illuminate/Database/Connection.php:685
Sep 28 15:08:38 Illuminate\Database\Connection->runQueryCallback() at /app/code/vendor/laravel/framework/src/Illuminate/Database/Connection.php:652
Sep 28 15:08:38 Illuminate\Database\Connection->run() at /app/code/vendor/laravel/framework/src/Illuminate/Database/Connection.php:486
Sep 28 15:08:38 Illuminate\Database\Connection->statement() at /app/code/vendor/laravel/framework/src/Illuminate/Database/Schema/Blueprint.php:109
Sep 28 15:08:38 Illuminate\Database\Schema\Blueprint->build() at /app/code/vendor/laravel/framework/src/Illuminate/Database/Schema/Builder.php:365
Sep 28 15:08:38 Illuminate\Database\Schema\Builder->build() at /app/code/vendor/laravel/framework/src/Illuminate/Database/Schema/Builder.php:228
Sep 28 15:08:38 Illuminate\Database\Schema\Builder->create() at /app/code/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php:261
Sep 28 15:08:38 Illuminate\Support\Facades\Facade::__callStatic() at /app/code/database/migrations/2021_08_23_101529_recurring_expenses_schema.php:79
Sep 28 15:08:38 RecurringExpensesSchema->up() at /app/code/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php:394
Sep 28 15:08:38 Illuminate\Database\Migrations\Migrator->Illuminate\Database\Migrations{closure}() at /app/code/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php:403
Sep 28 15:08:38 Illuminate\Database\Migrations\Migrator->runMigration() at /app/code/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php:202
Sep 28 15:08:38 Illuminate\Database\Migrations\Migrator->runUp() at /app/code/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php:167
Sep 28 15:08:38 Illuminate\Database\Migrations\Migrator->runPending() at /app/code/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php:112
Sep 28 15:08:38 Illuminate\Database\Migrations\Migrator->run() at /app/code/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php:85
Sep 28 15:08:38 Illuminate\Database\Console\Migrations\MigrateCommand->Illuminate\Database\Console\Migrations{closure}() at /app/code/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php:585
Sep 28 15:08:38 Illuminate\Database\Migrations\Migrator->usingConnection() at /app/code/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php:94
Sep 28 15:08:38 Illuminate\Database\Console\Migrations\MigrateCommand->handle() at /app/code/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:36
Sep 28 15:08:38 Illuminate\Container\BoundMethod::Illuminate\Container{closure}() at /app/code/vendor/laravel/framework/src/Illuminate/Container/Util.php:40
Sep 28 15:08:38 Illuminate\Container\Util::unwrapIfClosure() at /app/code/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:93
Sep 28 15:08:38 Illuminate\Container\BoundMethod::callBoundMethod() at /app/code/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:37
Sep 28 15:08:38 Illuminate\Container\BoundMethod::call() at /app/code/vendor/laravel/framework/src/Illuminate/Container/Container.php:651
Sep 28 15:08:38 Illuminate\Container\Container->call() at /app/code/vendor/laravel/framework/src/Illuminate/Console/Command.php:136
Sep 28 15:08:38 Illuminate\Console\Command->execute() at /app/code/vendor/symfony/console/Command/Command.php:299
Sep 28 15:08:38 Symfony\Component\Console\Command\Command->run() at /app/code/vendor/laravel/framework/src/Illuminate/Console/Command.php:121
Sep 28 15:08:38 Illuminate\Console\Command->run() at /app/code/vendor/symfony/console/Application.php:978
Sep 28 15:08:38 Symfony\Component\Console\Application->doRunCommand() at /app/code/vendor/symfony/console/Application.php:295
Sep 28 15:08:38 Symfony\Component\Console\Application->doRun() at /app/code/vendor/symfony/console/Application.php:167
Sep 28 15:08:38 Symfony\Component\Console\Application->run() at /app/code/vendor/laravel/framework/src/Illuminate/Console/Application.php:92
Sep 28 15:08:38 Illuminate\Console\Application->run() at /app/code/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php:129
Sep 28 15:08:38 Illuminate\Foundation\Console\Kernel->handle() at /app/code/artisan:37

In Invoice Ninja v5 Dashboard the area is now for a new version. Of course when we click UPDATE it says app.php is locked.

But in the Cloudron dashboard the tile does not offer a new version.

Is the built in upgrade usually disabled in a Cloudron instance?

Confirmation of resolution. Issue is fixed.

If we wanted to change the branding on a self hosted instance, are there any guides to doing that?

Our bin is customer facing, we would like to clean it up and use our logo.

@nebulon said in InvoiceNinja cron not enabled:

php /app/code/artisan queue:work --sleep=3 --tries=3 --max-time=3600

I ran that code via the terminal and it didn't give a response. I had to exit out of the command.

I didn't see any change in the dashboard status (red triangle) or have any success with another migration attempt.

I am still unclear wether I am supposed to add a line to cron, or if I am just supposed to wait until the error goes away and try migrating again.

EDIT*. - For clarity, this is the error we are getting when we try to migrate from our v4 install: "Cross account migration is not allowed. Please read more about it here:"

@nebulon - Its in the instructions in the Cloudron thread and in the Invoice Ninja docs.

We are trying to migrate form one self hosted instance to the new v5 instance and we are getting an error when we try and the red alert triangle at the bottom of the v5 dashboard saying "The CRONS need to be enabled."

I am now seeing this one that mentions laravel, the docs are a bit confusing and circular between Cloudron and Invoice Ninja.

https://invoiceninja.github.io/docs/self-host-troubleshooting/#cron-not-running-queue-not-running

I am surprised this is an issue, I figured stuff like CRON would be handled in the install from Cloudron like v4

@fbartels said in Path To Project on Cloudron:

https://docs.cloudron.io/custom-apps/addons/#scheduler

Unfortunately I am not a developer so your answer is way over my head.

Ill try /app/code and see what happens

We are trying to get the laravel cron set up and the instruction on the IN site are to add. this line to crontab:

"* * * * * cd /path-to-your-project && php artisan schedule:run >> /dev/null 2>&1"

On a Cloudron install, what is the correct value for "/path-to-your-project"?

This issue is impacting us on a migration. We can't get the migration to work because the cron is not running on the target server.

Should we just create a user or two and hope the cron starts runing?