Kinsta Cron Commands
FeedSync Service on Kinsta: these are the steps to add the FeedSync Service image-processing cron to a Kinsta site. Kinsta has no cron screen, so it's done over SSH and takes about five minutes. Still on legacy FeedSync, installed on your own server? Its last release was 3.9, support ends 5 December 2026 and the connected server switches off on 31 December: see the FeedSync Service plans.
On the FeedSync Service: WordPress Integration (FeedSync documentation) · Set up a server-side cron for image processing · Do I need Run Sync or a cron?
On Kinsta hosting each site runs in its own container with its own crontab, and the only way to edit it is over SSH (or ask Kinsta support in chat to add the line for you). Kinsta's guide: Cron jobs.
Before you start: copy your Process Job URL
In your FeedSync dashboard, go to Sites, open your site, then Cron Job Management, and copy the Process Job URL. It already includes your site's key and looks like this:
https://yoursite.com.au/wp-json/feedsync/v1/cron/process-queue?auth_key=YOUR_SITE_KEY
Add the cron over SSH
- Log in to MyKinsta, go to Sites and open your site.

- On the site's Info page, scroll to Primary SFTP/SSH user. Copy the SSH terminal command, and copy the Password too: you'll need it in a moment.

- Open Terminal (Mac) or PowerShell (Windows: click Start and type PowerShell). Paste the SSH command and press Enter.

- When it asks for the password, paste it and press Enter. Nothing shows as you type or paste: that's normal. (The first time, it may ask if you trust the host: type
yes.)

- You're in when you see Kinsta's welcome. Type
crontab -eand press Enter to open your site's cron list. If it asks for an editor, pick nano.

- Use the arrow keys to go to the very bottom of the file and paste this as a new line, with your Process Job URL between the quotes. Leave the lines above it alone: Kinsta manages those.
*/5 * * * * wget -q -O /dev/null "PASTE_YOUR_PROCESS_JOB_URL_HERE" # FeedSync Image Processing
- Save and close: press Ctrl+O (Write Out), then Enter, then Ctrl+X (Exit). You'll see
crontab: installing new crontab.

- Optional: run
crontab -lto check your line is there, then typeexitto log out.
Kinsta's shortest interval is every 5 minutes (*/5). That's fine: each run works through several images. Keep the quotes around the URL.
Last, back in Cron Job Management in your FeedSync dashboard, turn off the external cron so the two don't both run.
Test it
Paste your Process Job URL into your browser's address bar.
- Working:
"success": true, with a line like1 queue item(s) completed, 4 image(s) processed, orProcessed 1 chunk(s), items still in progresswith"pending": "0"(nothing was waiting: every image is done). - Not working:
"code":"rest_forbidden"with"status":401. Your site is turning the key away: press Refresh Key in Cron Job Management, then put the new URL in your crontab. More in Set up a server-side cron for image processing.
Legacy FeedSync (on your own server)
For legacy FeedSync and WP All Import, the lines were in this format (https://localhost/ is correct on Kinsta):
*/5 * * * * curl -kILs -H 'Host: www.YOUR_HOST.com.au' "https://localhost/XML/feedsync/core/cron.php" >/dev/null 2>&1
5 * * * * curl -kILs -H 'Host: www.YOUR_HOST.com.au' "https://localhost/wp-load.php?import_key=YOUR_IMPORT_KEY&import_id=YOUR_IMPORT_ID&action=trigger" >/dev/null 2>&1
*/5 * * * * curl -kILs -H 'Host: www.YOUR_HOST.com.au' "https://localhost/wp-load.php?import_key=YOUR_IMPORT_KEY&import_id=YOUR_IMPORT_ID&action=processing" >/dev/null 2>&1