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

[michalkvasnicak]

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 [email protected].

See https://github.com/vercel/next.js/issues/58914

[0x6e6f6c61]

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

[kurodenjiro]

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

[humanagent]

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

[redbmk]

This happens because of multiple x-forwarded-proto headers.

I've been trying to reproduce this locally for a while. I just tested sending mulitple x-forwarded-proto headers (without a proxy) and didn't have any issues, even if they were different. However, when I added multiple x-forwarded-host headers, I did start seeing an error: Error: Invalid Server Actions request.

But that still isn't the same issue I was seeing in a deployed instance, which is TypeError: Invalid URL

This is on Next 14.2.4