Encountering the “OAuth2.0 /authorized not found” issue is quite common.

Upon successfully testing the frontend on localhost, I proceeded to deploy it to a VPS. Appreciate the assistance of Samuel Sprickerhoff and Sree Ashwini in swiftly setting up the VPS server in two days with Alma Linux 9, allowing me to experiment with Next.js 14.

However, after deploying to the VPS, I encountered the “/authorized” error. I initially tried to manually add routes, but found that the current create-react-app framework couldn’t accommodate this. This led me to encounter concepts such as Isomorphic React and Server-Side Rendering (SSR) and I invested some time in understanding how ReactJs 18 implements these and how webpack bundles styles and TypeScript, totally costing me about one week.

Sebastian Vittersø suggested exploring Next.js. After discussing with my supervisor, we decided to give it a try. Next.js appears to address my previous concerns as well, including caching, faster page loading speeds, server-side rendering, and route management. It’s straightforward to get started with, and its official documentation offers clear instructions. To get started, just run npx create-next-app@latest, then npm run dev, and visit the website at http://localhost:3000.

My version of configuration is as follows:

nvm --version
0.39.7

node --version
v22.2.0

npm --version
10.7.0

next --version
Next.js v14.2.3