System Error Reference & Troubleshooting Guide
1. 400 Bad Request
Why this error occurs: This error happens when the server cannot process the request due to malformed request syntax, invalid parameters, or corrupted data sent from the browser/client.
How to fix this error: Refresh the page, clear your browser cache and cookies, or check if the input data format sent to the API is correct and well-formed.
2. 401 Unauthorized
Why this error occurs: This occurs when you try to access a protected feature, route, or cloud synchronization module without valid authentication credentials or login session.
How to fix this error: Ensure you are logged into your account with proper authentication, re-authenticate your session, or check if your security token has expired.
3. 403 Forbidden
Why this error occurs: The server understands the request, but refuses to authorize it. This triggers when blocked non-Google bots, scrapers, or unauthorized users attempt to access restricted directories or server endpoints.
How to fix this error: Verify that your IP or User-Agent is permitted, check your file permission settings, or ensure you are not violating the strict crawler security firewall.
4. 404 Not Found
Why this error occurs: This happens when the requested page, asset file, script, or API route does not exist on the server or has been moved/deleted.
How to fix this error: Double-check the URL spelling and path, ensure all portfolio files are deployed correctly, or return to the home page.
5. 405 Method Not Allowed
Why this error occurs: This occurs when a request method (like GET, POST, PUT) is used on an API endpoint that does not support or allow that specific method.
How to fix this error: Check the API route handler configuration in the backend server code to ensure the correct HTTP method mapping is implemented.
6. 415 Unsupported Media Type
Why this error occurs: This is triggered during file uploads (such as data analysis or document parsing) when the uploaded file format or MIME type is not supported by the parser.
How to fix this error: Upload valid supported document formats (such as genuine .docx, .pptx, .xlsx, or .txt files) and ensure proper content-type headers are sent.
7. 429 Too Many Requests
Why this error occurs: This error appears when rate-limiting thresholds are exceeded—such as sending too many chat requests within the 5-hour quota limit or executing rapid code runner loops.
How to fix this error: Wait for the cooldown period or quota reset timer to expire before sending subsequent requests to the server.
8. 500 Internal Server Error
Why this error occurs: A generic catch-all error indicating that an unexpected unhandled exception or coding bug occurred inside the backend server (`server.js`) during execution.
How to fix this error: Inspect server console logs and stack traces, debug the faulty function in the backend code, and restart the Node.js server instance.
9. 502 Bad Gateway
Why this error occurs: This happens when the hosting gateway or proxy server receives an invalid response from an upstream server while processing the request.
How to fix this error: Check if the upstream Node.js process is running correctly, verify network gateway configurations, and reload the application.
10. 503 Service Unavailable
Why this error occurs: The server is currently unable to handle the request due to temporary overloading, server maintenance, or entering sleep/idle mode.
How to fix this error: Wait a few moments for the server to spin back up from sleep mode, check cloud resource scaling, and try your action again.
11. 504 Gateway Timeout
Why this error occurs: This occurs when the server fails to get a timely response from an external API (like Gemini API) or database operation within the allowed time limit.
How to fix this error: Optimize the payload size, increase the timeout limit in server settings, or check your internet and cloud connection speed.
12. Client-Side Runtime & Network Error
Why this error occurs: This happens due to sudden internet disconnection, local JavaScript runtime crashes, or blocked sandbox execution in the browser.
How to fix this error: Check your internet connection status, inspect browser developer console logs for script errors, and reload the web app interface.