Communicate by Emitting 404 on redirect

Tell us what’s happening:
when i verify myself with github it redirects to the callback and says NotFound which is the default 404 msg in the routes.

i did this socket.io stuff a couple of days ago and have tried c/p full pages over to work out where the error is occurring however it always says not found. the callback is correct and the env variables setup

i must of done something really stupid for this 2 be so hard to troubleshot by myself

edit: i turned off the authcheck on the route /chat and went to /chat and it loaded without an issue
Your code so far
https://glitch.com/edit/#!/yellow-podium-0wgzkj8xzg?path=app/routes.js:27:11

Your browser information:

User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.117 Safari/537.36.

Challenge: undefined

Link to the challenge:
https://www.freecodecamp.org/learn/information-security-and-quality-assurance/advanced-node-and-express/communicate-by-emitting

You can redirect a web page via JavaScript using a number of methods. If you want a cross-browser compliant JavaScript redirect script, better to use the following scripts.

window.location.href = "http://anotherdomain.com";

Also, You can use window.location object to load another page in JavaScript.

window.location = "http://anotherdomain.com";

A pure HTML alternative is the following tag in your HTML :

<meta http-equiv="refresh" content="0;http://anotherdomain.com">

The 0 is here the amount of seconds the page has to stay open before redirecting.

Hi @linehammer !

Thank you for your response but this post is over a year old.

Please try to participate in newer topics.

Thanks!