Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TypeError: Invalid URL when calling Frames built using Next.js #319

Open
michalkvasnicak opened this issue Apr 17, 2024 · 3 comments
Open

Comments

@michalkvasnicak
Copy link
Collaborator

michalkvasnicak commented Apr 17, 2024

If you built frames using Next.js and have that application behind multiple proxies you can get an error ⨯ TypeError: Invalid URL.

This happens because of multiple x-forwarded-proto headers. In order to get around this issue user has to downgrade to next@14.0.1.

See vercel/next.js#58914

@michalkvasnicak michalkvasnicak changed the title Frames behind Proxy built using Next.js don't work when multiple x-forwarded-proto headers are used. TypeError: Invalid URL when calling Frames built using Next.js Apr 17, 2024
@0x6e6f6c61
Copy link

i got this error following the 5 minute speedrun video on youtube to a T

@kurodenjiro
Copy link

add DEBUGGER_URL="http://localhost:3010" to .env file

@fabriguespe
Copy link

fabriguespe commented May 1, 2024

Same for me! i added the .env file but still

CleanShot 2024-04-30 at 21 30 29@2x

@davidfurlong davidfurlong added the Frames.js label Aug 27, 2024 — with Linear
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants