#Facing issue with connecting to trigger.dev from local

1 messages · Page 1 of 1 (latest)

worthy vector
#

Trigger.dev (4.0.1)

Key: Version | Task | Run

○ Building local worker…
○ Local worker ready [node] -> 20250828.19 | Test tasks | View runs

It shows connected on local but in ui its showing dev server isnt connected and tasks arent getting processed

tough reefBOT
#

Hi @worthy vector. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

It looks like your local dev server is running, but the dashboard isn’t detecting it. The docs don’t list a specific “connected but UI says not connected” fix, but here are the supported checks based on what we have:

  • Ensure you’re using the latest CLI: run with npx trigger.dev@latest dev, which also performs an update check to prevent version mismatches (you’ll be prompted to upgrade if needed) (CLI dev).
  • Clear local build cache: stop the dev server, delete the hidden .trigger folder in your project, then restart the dev server (Troubleshooting).
  • Verify environment: TRIGGER_SECRET_KEY must be set in your local .env (or framework-specific env file) so your app can authenticate; also set TRIGGER_API_URL if you’re on a self-hosted instance (Manual setup).
  • Keep dev server online: in dev mode, scheduling is handled by Trigger.dev’s server but your code runs locally; the UI shows connectivity only while the dev server is running and reachable (How it works – Dev mode).
  • If using self-hosted: confirm the API URL you passed to the CLI matches your instance, and that you’re logged in to the right profile/project (use --api-url/--profile) (The CLI, Manual setup – CLI auth).
  • If issues persist, stop the dev server, run npm cache clean --force (only if you saw EACCES or cache issues), then restart. Also ensure Yarn PnP isn’t interfering (remove a stray ~/.pnp.cjs if present) (Troubleshooting).
#

If none of the above helps, I’m sorry, but the knowledge sources don’t include more specific steps for this exact symptom. Please try the general Troubleshooting page for further guidance (Troubleshooting).

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@worthy vector Kapa.ai is still learning and improving, please let me know how I did by reacting below.

nimble moat
#

Plus 1 - Pretty sure they are having down time

#

@worthy vector Let me know if you're able to fix this!

cyan juniper
#

Having the same issue for about 20 minutes now

feral wind
#

Same here.

nimble moat
worthy vector