Failed to load resource: the server responded with a status of 500 (Internal Server Error)
this is the error on console
A 500 Internal Server Error typically indicates that something has gone wrong on the server side. Since your new site becomes unresponsive after a few minutes and you're seeing this error in the console, here are some common causes and steps to troubleshoot:
Server-Side Script Errors
A bug in your backend code (e.g., PHP, Node.js, Python) could be causing the server to crash or return an error.
Resource Exhaustion
The server might be running out of memory, CPU, or hitting a timeout due to inefficient code or too many requests.
Misconfigured Server or Hosting Environment
If the new site is linked to the old site's Website Record, there might be configuration mismatches (e.g., environment variables, database connections).
Database Issues
If the site relies on a database, a failing query or connection issue could trigger a 500 error.
Error in .htaccess or Server Config Files
If you're using Apache or Nginx, a misconfigured .htaccess
or server block could cause this.
Check Server Logs
Look at your web server logs (e.g., Apache error.log
, Nginx error.log
, or application logs) for detailed error messages.
Reproduce the Issue
Try to identify what action or request causes the site to become unresponsive.
Check Resource Usage
Monitor CPU, memory, and disk usage on the server to see if it's being overwhelmed.
Review Recent Changes
Since this is a new site, review any recent code or configuration changes that might be causing instability.
Test API or Backend Endpoints
Use tools like Postman or curl to test backend endpoints directly and see if they return errors.
If you can share:
🏷️ Tag me if you have any further questions or if the issue persists.
✅ Click "Accept as Solution" if my post helped resolve your issue—it helps others facing similar problems.
❤️ Give it a Like if you found the approach useful in any way.