Monday, November 26, 2018

Team Plan - Multiple User per Account

If you are working in a team or company and want to share your account with your colleagues, you can now upgrade to Team Plan.

To convert your account to Team plan, log in to SetCronJob, visit the Account tab, check the box Team support at the current plan (starred), then click Select, and click Update plan directly.
Add Team support to your plan
The current price for Team support is $4, $10 and $20 for Gold, Platinum and Diamond account respectively. So standard Gold accounts are at $20 / year, and Gold Team accounts are at $24 / year.

When your account plan is updated, you can add team member at Account > Members.
Add team member to your account
Your team member needs to sign up first at SetCronJob. They will have their own account, but they needn't pay, upgrade, or renew them to use your account.

Currently, all team members can access your account and cronjobs, including:
- Manage your cronjobs (including view, add, edit, delete, view logs, etc).
- View your account information (name, email, plan, payments, address, API token, etc).
- Make payment and change your account plan.
- Manage your account's contacts (email, slack, webhook URL).

However, they can NOT change your account name, email, password. Team member won't be able to see and update your account's members list either.

Only the account owner will be able to add (invite) or delete team members.

After your team members are added to your account, they can access your account by clicking their profile name (top right corner), then click Switch account.
Switch to shared accounts
They can click Access to enter your account and manage your cronjobs. Once they're done, they can switch back to their own account or just log out. The current working account is persistently stored, so one can only work on one account at a time, and they'll continue where they left off whenever they log in to SetCronJob again.

If you have any question, just discuss at our forum, or create a ticket.

Friday, September 21, 2018

Auto delete one-time cronjobs

Hello there,

Now you can save one API requests with our new feature: automatically delete one-time cronjobs after they executed.

First, create or edit a group and update the select box Automatically delete stopped (one-time) cronjobs after to the desired value. You may want to keep the executed cronjobs long enough so you can check its execution results later.
Auto delete one-time cronjobs
After that, just create all one-time cronjobs under that group, and that's it.

Once your one-time cronjobs executed, they'll be deleted automatically after the set time.

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 ;-)