How to setup CRON on Hostinger

Self-Hosted | v5
1

CRON jobs on Hostinger are setup on this panel. screenshot-hpanel.hostinger.com-2023.10.24-12_24_53 - Nimbus Capture

What do I need to fill in for this?

Thanks!

2

Hi,

There cron command can be found here: Free Source Available Invoicing, Expenses & Time-Tracking | Invoice Ninja

It needs to be run every minute.

3

I’d already found that but I can’t parse out what the command I need to use is. Thanks.

4

This is the main command but it will need to be adjusted to work on your sever.

cd /path-to-your-project && php artisan schedule:run

5

Ok. I adjusted it and installed it to run every minute/hour/day/month - how do I test it now? Thanks.

6

You could try configuring a test recurring invoice.

7

I created one and told it to send now and it’s now in my invoices. Does this mean it’s working?

8

No, the cron is used for scheduled sends

9

Health Check seems to suggest CRON isn’t correct.

10

The cron isn’t referenced in the health check.

If the cron isn’t running you’ll see an error in the bottom left corner in the Flutter app.

11

I do see an error. A triangle with a ! in it.

12

What do you see when clicking the triangle?

If it says the cron isn’t running it means the command being used isn’t correct.

13

I finally got the CRON job to run but it output this error:

/home/u737112827/domains/woodalldesign.net/public_html/invoicing/kwoodall.sh: line 4: cd: too many arguments Could not open input file: artisan

14

Can you share your cron, you may be missing the &&

15

I had to turn it into a shell script as the CRON web interface didn’t allow special characters.


#!/bin/bash

# This script will do Kermit's bidding
cd /usr/bin/php/home/u737112827/domains/woodalldesign.net/public_html/invoice/
php artisan schedule:run
16

From the error it looks like the commands are being run together

17

I think it was the wrong path. At least it worked for the fresh install of IN. Any advice before I export the old and import into the fresh?

18

If you have SSH access you can run the command from the CLI to test it.

19

Yes, that’s how I resolved it. The path was the issue.

Thanks for your help!

20

Glad to hear it, thanks for the update!