Hi @Richestsoft , did you view the diagnostic resources? It would help to have a more detailed error message to fix. In the meantime please try the following steps and let me know if they resolve the issue:
- Check the logs: Access the log files to get more information about the error. You can find the logs in the
LogFilesfolder, typically located at
- Verify the startup file: Ensure that your
web.configfile has the correct settings, including the correct path to your main script file and the
- Check for uncaught exceptions: If your application is throwing uncaught exceptions, you can find details in the
logging-errors.txtfile located in the
- Cold start: If your application takes too long to start, it may result in a 500 error. You can try increasing the values of
namedPipeConnectionRetryDelaysettings to prevent iisnode from timing out.
- Memory consumption: If your application is consuming too much memory, it may affect other processes. You can profile your application for memory leaks or scale up to a larger VM if needed.
Please let me know if you have any questions and I can help you further.
If this answer helps you please mark it as "Verified" so other users can reference it.