To access cron jobs, go to "Advanced Tools" section, then click the "CronJobs" menu.
Cron jobs are system commands that can be scheduled. For example, if you wanted a CGI script to run every Monday morning, you could do this through the cron jobs menu. Values that can be set are minute, hour, day, month, and day of week (Monday-Sunday; the numbers 0 or 7 represent Sunday). Any value can be ignored by placing an asterisk (*) in the text field.
In the above example, we are setting updater.cgi to run every day at midnight.
You can also specify exact times using commas to separate them (e.g. 1,2,3 is minutes 1, 2 and 3).
You can specify spans using a dash (e.g. 5-7 is minutes 5 to 7).
You can specify intervals using a star and a forward slash. (e.g.: */2 is every 2nd minute.)
You can combine them to create a more precise schedule. (e.g.: 1,5,11-15,30-59/2 (minutes 1, 5, 11 to 15 and every 2nd minute between 30 and 59).
Remember to click "Add" when you are finished entering your data.
If you're trying to run a php script, remember to run the php binary, and pass it the php script. For example:
/usr/local/bin/php /home/user/domains/domain.com/public_html/file.php
What to check after following this guide
After changing settings, make sure the result works not only in the control panel but also for real website visitors or mailbox users. Test without browser cache and avoid changing many settings at once unless you know exactly what each change does.
For domains, check which DNS records are visible from outside. If records were changed recently, some networks may still use the old values until DNS propagation is complete.
- check the name servers at the registrar;
- verify A, MX, TXT, CNAME or other required records;
- wait for DNS propagation if the change was recent.
When to contact GoodNet support
If the guide is not enough, contact GoodNet support. Include the domain, service name, when the issue started, what you already checked and the exact error text. This helps support move directly to diagnostics.