Friday, August 24, 2018

5 new servers are added

Hello there,

SetCronJob just added 5 new servers and will be using them for processing your cronjobs. Please add their IP addresses to your whitelist as soon as possible.

Here are the new IPv4 addresses:
206.189.231.210

142.93.14.153
142.93.123.161
142.93.189.98
104.248.15.180

And here are new IPv6 addresses
2604:a880:400:d1::20f:1001

2604:a880:400:d1::86a:5001
2604:a880:400:d1::8e7:b001
2604:a880:800:c1::1c:7001
2604:a880:800:c1::76:e001

You can view our full list of IP addresses at our Help Center.

If you want to receive email notification every time we add new servers, please subscribe here.

If you need any help, please feel free to create a ticket at the Help Center.

Wednesday, August 8, 2018

Set cronjob to run command on your server using SSH

SetCronJob is a web-based cronjob service, and currently, you can only set cronjob with URLs to your scripts.

If your cron scripts only support CLI (command line interface), then you may use our free service at Clustermin to create a cron trigger. It requires that you can access your server using SSH connections.

You can create a free account here. You can add up to 5 servers in the free account, and it'll be more than enough for your case.

First, you'll need to connect your server to Clustermin. For setting up cronjob, you should enter the user that has access to your web folders (public_html, www, etc.) and uncheck the box Create user. No worry, it will install nothing but a public SSH key into your authorized_keys file so that it can connect your server securely using SSH key next time.

Secondly, make sure your command works fine. Click the Execute button, then enter the whole cron command e.g.
php /home/your-user/example.com/proj/app/console do:something
and make sure it works as expected.

Thirdly, when you're sure the command works, visit Script > Add a script to create a script with the command as contents. Remember to check the box This is a private script.
Finally, visit Trigger > Add a trigger, then select your newly created at Run script, and your connected server at On servers.

When the trigger is created, you can copy the trigger URL, and set cronjob with it.

At your desired time, SetCronJob will execute (pull) the trigger, and Clustermin will execute the command on your server.

Let me know if it works for you ;-)

Saturday, July 21, 2018

Multi-Datacenter High Availability for SetCronJob

Hello there,

After recent incidents with the datacenter SetCronJob hosted in, I decided to move all the main servers to another data center as well as work on multi-datacenter clustering.

The servers transfer and multi-datacenter setup were completed without any service downtime. Now SetCronJob fully achieved high availability that can withstand whole datacenter outages.

The clustering was done with great help from Clustermin, my developing service for server cluster management and automation. Setting up once and it'll run setup script, update firewall rules and configurations files in all servers and all clusters, whenever a new server is added or old server removed.

The current setup will greatly improve our service reliability, and hopefully, I don't need to inform you about any downtime again ;-)


Wednesday, July 18, 2018

Power outage in our data center

Hello all,

I'm sorry to inform that we had another power outage at our new datacenter (we migrated to another data center after the last incident). Because of it, our service was unavailable from 22:56 to 23:55:30 July 18, UTC time.

The service has been working fine since then.

I'm still working on our server clusters to prevent this from happening again.

Sorry for the inconvenience that caused.

If you encounter any problem with our service, just let me know.

Wednesday, June 20, 2018

Connectivity issues in our datacenter

Hello there,

Currently, our server provider has a problem with their datacenter in Fremont which SetCronJob hosts on. The whole service is down at the moment.

UPDATED: SetCronJob is online and working again. The total service downtime is about 2 hours 50 minutes.

Although I had no control over major issues like this, I relied too much on my server provider and didn't react in time to migrate the databases to another data centers. This cause unnecessarily longer downtime of the service.

As a token of our apology, I have added a credit of 10% of your account plan price (e.g. $5 for Platinum accounts) to your account balance.

If you have any question or encounter any problem with SetCronJob, please feel free to let me know.