#Random bug appearing on Next.JS Deployment for certain users

5 messages · Page 1 of 1 (latest)

brittle vault
#

When users try to access the main page, the logs show that the server throws a 500 error for only some users, with this being the nextjs log:

TypeError: Invalid URL
at new URL (node:internal/url:796:36)
at V (/var/task/.next/server/chunks/641.js:7:10417)
at eh (/var/task/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:134786)
at e (/var/task/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:137671)
at ek (/var/task/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:138145)
at Array.toJSON (/var/task/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:135755)
at stringify (<anonymous>)
at eR (/var/task/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:142219)
at eE (/var/task/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:142698)
at Timeout._onTimeout (/var/task/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:135475) {
code: 'ERR_INVALID_URL',
input: 'undefined',
digest: '2226716650'
}

Is there any way to fix this, or this is a bug inside of Next.JS itself? Everything was always fine until at some point it appeared.

rugged onyxBOT
#

🔎 This post has been indexed in our web forum and will be seen by search engines so other users can find it outside Discord

🕵️ Your user profile is private by default and won't be visible to users outside Discord, if you want to be visible in the web forum you can add the "Public Profile" role in id:customize

✅ You can mark a message as the answer for your post with Right click -> Apps -> Mark Solution
(if you don't see the option, try refreshing Discord with Ctrl + R)

quaint pendant
#

this doesn't directly solve your problem, but it reliably happens 100% of the time when i clear my cookies on your site
opening a new incognito tab and going to the url will always 500 on the first request, after refresh it works

#

specifically the signal-url cookie being empty causes 500

brittle vault
#

Yes, I've had a look and I indeed found the error really quickly! Thank you so much! ❤️