Start free trial

Cron, WP-CLI, caching, SSL and REST troubleshooting (401, 403, 404)

Help Center

New to VisionScaper?
Start here

Help Center › API keys & connections › Cron, WP-CLI, caching, SSL and REST troubleshooting (401, 403, 404)

Cron, WP-CLI, caching, SSL and REST troubleshooting (401, 403, 404)

Keep scheduled jobs running, avoid cache problems, require https, and fix REST 401, 403 and 404 errors.

On this page

Cron (scheduled jobs)

VisionScaper uses WordPress cron. It drives alerts, reminders, marketing sends, syncs, erase requests and housekeeping.

Hook How often
dreamscaper_crm_tick every 5 minutes (the main tick: follow-ups, alert checks)
dreamscaper_int_hourly hourly (Google Contacts and QuickBooks syncs)
dreamscaper_ops_cron, dreamscaper_tr_daily, dreamscaper_subs_daily hourly
dreamscaper_data_daily, dreamscaper_sec_daily, dreamscaper_msg_daily daily
dreamscaper_postcard_tick every 5 minutes

WordPress only runs jobs when someone visits. For dependable timing, add a real server cron every 5 minutes: wget -q -O - https://YOURSITE/wp-cron.php?doing_wp_cron >/dev/null 2>&1, and add define( 'DISABLE_WP_CRON', true ); to wp-config.php. The Marketing page shows this advice when its last run is old.

WP-CLI

The plugin adds no commands of its own (none found in the code). You can use WordPress’s own, for example wp cron event list and wp cron event run dreamscaper_crm_tick. Not tested here.

Caching

  • Do not cache /wp-json/ or pages using ?dreamscaper_oauth=, ?ds_ics= or ?ds_tile=.
  • Many plugin responses send no-cache headers. Map tiles are cached on purpose.
  • Exclude the Designer and Hub pages from page caching if screens look stale.
  • After changing a key or a switch, clear your cache.

SSL (https)

  • Use https:// on the live site. Alerts must go to https:// addresses. OSRM must be https://.
  • Sign-in cookies are set secure when the site is on https.
  • Provider webhooks (Stripe, Twilio, Retell and others) need a public https address.

REST troubleshooting

401 Unauthorized
– API keys: missing, mistyped or turned-off key. See API errors and rate limits.
– Signed-in screens: your login session ended. Sign in again.
– The Authorization header is stripped by your host. Ask them to pass it through.

403 Forbidden
– API keys: the key lacks the scope named in required_scope.
– Alert answers 403 “Bad signature” (messaging webhooks): the webhook secret is wrong.
– A security plugin or firewall is blocking /wp-json/.

404 Not Found
1. Save Settings → Permalinks once to refresh rules.
2. Try ?rest_route=/dreamscaper/v1/api/v1/ping.
3. Check the path: /wp-json/dreamscaper/v1/api/v1/....
4. Check the record exists for your business.

Tips

  • Keep PHP OpenSSL enabled. It stores secrets.
  • Quote X-Request-Id when asking for help.

If something goes wrong

Alerts late or reminders missing almost always means cron is not firing. Fix cron first.

Related articles

Still need help?

Tell us what you were trying to do and a person will reply.

Contact support