Skip to content

Commit e8ae33c

Browse files
committed
connection error troubleshoot
1 parent 4c986ad commit e8ae33c

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

docs/troubleshooting.mdx

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -45,6 +45,14 @@ The Yarn Plug'n'Play manifest forbids importing "@trigger.dev/core" here because
4545

4646
And you're using Yarn v1.22 or another package manager, check if you have a `.pnp.cjs` file in your home directory. This can happen if you previously had Yarn Plug'n'Play enabled globally. Remove the `.pnp.cjs` file to resolve the issue.
4747

48+
### `Connection error` when logging in
49+
50+
If you see "Connection error" when running `trigger login` (or "Failed to create authorization code"), try these in order:
51+
52+
1. **Clear saved auth and retry:** `npx trigger.dev@latest logout`, then `npx trigger.dev@latest login` again. Sometimes an invalid config is cached.
53+
2. **VPN or firewall:** Disconnect from VPN or check firewall/proxy; try `npx trigger.dev@latest login -l debug` for more detail.
54+
3. **TLS / certificate store:** Node may use a different CA store than your OS (e.g. `curl` works but the CLI fails). Try `export NODE_EXTRA_CA_CERTS=/etc/ssl/cert.pem` (macOS/Linux) then login again, or reinstall Node so it gets updated certs. Behind a corporate proxy or custom CA? Set `NODE_EXTRA_CA_CERTS` to that CA file.
55+
4856
## Deployment
4957

5058
Running the [trigger.dev deploy] command builds and deploys your code. Sometimes there can be issues building your code.

0 commit comments

Comments
 (0)