Provide environment information
System:
- OS: Linux 7.0 Ubuntu 26.04 LTS 26.04 LTS (Resolute Raccoon)
- CPU: (4) x64 Intel(R) Core(TM) i3-1005G1 CPU @ 1.20GHz
- Memory: 8.01 GB / 14.89 GB
- Container: Yes
- Shell: 5.3.9 - /bin/bash
Binaries:
- Node: 24.15.0 - /home/naresh/.nvm/versions/node/v24.15.0/bin/node
- npm: 11.12.1 - /home/naresh/.nvm/versions/node/v24.15.0/bin/npm
- pnpm: 10.33.2 - /home/naresh/.nvm/versions/node/v24.15.0/bin/pnpm
- bun: 1.3.14 - /home/naresh/.bun/bin/bun
Browsers:
- Brave Browser: 149.1.91.180
- Chrome: 149.0.7827.200
- Firefox: 152.0.5
- Firefox Developer Edition: 152.0.5
npmPackages:
- @remix-run/changelog-github: ^0.0.5 => 0.0.5
- @trigger.dev/database: workspace:* => 0.0.2
Describe the bug
When running Trigger.dev locally, signing in with the email magic link flow does not automatically navigate to the generated magic link after the authentication request succeeds.
The server successfully processes the login request, but the browser remains on the /login page, making it appear that authentication failed.
This issue is reproducible in local development.
Reproduction repo
N/A (reproduced using a fresh local checkout of the repository)
To reproduce
-
Clone the repository.
-
Install dependencies.
-
Start the local webapp.
pnpm run dev --filter webapp
-
Open http://localhost:3030/login.
-
Enter a valid email address.
-
Click Continue with Email.
Expected
The browser navigates to the generated magic link and completes authentication.
Actual
The login request succeeds, but the browser remains on /login. The page briefly refreshes/reloads and the user is not logged in.
Additional information
Server logs
webapp:dev: {"email":"naresh@trigger.dev","magicLinkVerify":false,"http":{"requestId":"vb2FxTFesLyu_mB4jlr3o","path":"/login/magic?_data=routes%2Flogin.magic","host":"localhost","method":"POST","abortController":{}},"timestamp":"2026-07-09T15:57:25.639Z","name":"webapp","message":"Magic link user authenticated","level":"info"}
webapp:dev: POST /login/magic?_data=routes%2Flogin.magic 204 - - 22.246 ms
The server indicates that authentication succeeds, suggesting the issue occurs after the login request completes.
I have been able to reproduce this consistently during local development.
http://localhost:3030/login?redirectTo=%2F
redirectTo=%2F, this appears in the address bar but doesn't redirect automatically
Provide environment information
System:
Binaries:
Browsers:
npmPackages:
Describe the bug
When running Trigger.dev locally, signing in with the email magic link flow does not automatically navigate to the generated magic link after the authentication request succeeds.
The server successfully processes the login request, but the browser remains on the
/loginpage, making it appear that authentication failed.This issue is reproducible in local development.
Reproduction repo
N/A (reproduced using a fresh local checkout of the repository)
To reproduce
Clone the repository.
Install dependencies.
Start the local webapp.
Open
http://localhost:3030/login.Enter a valid email address.
Click Continue with Email.
Expected
The browser navigates to the generated magic link and completes authentication.
Actual
The login request succeeds, but the browser remains on
/login. The page briefly refreshes/reloads and the user is not logged in.Additional information
Server logs
The server indicates that authentication succeeds, suggesting the issue occurs after the login request completes.
I have been able to reproduce this consistently during local development.
http://localhost:3030/login?redirectTo=%2F
redirectTo=%2F, this appears in the address bar but doesn't redirect automatically