Local Dev server not connecting to Trigger.dev

[warped current]

Hi,

I'm having trouble connecting the local server with Trigger dev, I'm getting this message in the paltform despite having the local server indicate "Local wroker ready [node]".

"Your local dev server is not connected to Trigger.dev"

What I've tried:

• Version matching, playing around with a couple different versions
• Restarting the local server
• Restarting the computer
• No VPNs, stable internet connection
• Deleted .trigger & node_modules and started again
• Re-run initialization command

[abstract canopy]

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

[warped current]

Env vars were fine too and no version mismatch

[abstract canopy]

---

Based on the knowledge sources, here are some troubleshooting steps and considerations for when your local dev server shows "Local worker ready [node]" but the Trigger.dev platform says "Your local dev server is not connected to Trigger.dev":

1. Clear Build Cache
   Stop your local dev server, then delete the hidden .trigger folder in your project directory. After that, restart your local dev server. This can resolve issues related to stale or corrupted build artifacts that may prevent proper connection between your local server and the Trigger.dev platform.
   Common problems

2. Check Environment Variables
   Ensure your TRIGGER_SECRET_KEY is correctly set in your environment file (e.g., .env or .env.local). This key is required for authenticating your local server with Trigger.dev. If you are using a self-hosted instance, also verify the TRIGGER_API_URL is set correctly.
   Manual setup

3. Version Matching
   You mentioned trying different versions, but ensure that both the CLI and SDK versions match exactly. The CLI will warn you about mismatches, but double-check your package.json and installed versions.
   How to upgrade the Trigger.dev packages

4. Network Requirements
   The local dev server requires an active internet connection to communicate with the Trigger.dev platform. Offline mode is not supported, so ensure there are no firewalls or network restrictions blocking outgoing connections.
   Dev mode

5. Restart and Re-authenticate
   Try logging out and back in with the CLI:

   npx trigger.dev@latest login
   

   Then restart the dev server:

   npx trigger.dev@latest dev
   

   Manual setup

6. Check for Permission Issues
   If you see permission errors (e.g., EACCES), follow the steps to clear the npm cache and fix permissions as described in the troubleshooting guide.
   Common problems

If you have tried all of the above and the issue persists, the knowledge sources recommend checking the Troubleshooting page for more details or reaching out for support.

I'm sorry, but the knowledge sources do not provide a more specific solution for this exact error message. If none of these steps resolve your issue, it may be necessary to contact Trigger.dev support or check for updates in their documentation.

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

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