General Queries

Port already in use/ Unable to start the server (ID: GQ1)

The error message "port already in use" occurs when an application attempts to bind to a network port that is already being used by another process. This means that the port number the application is trying to use is already assigned to another application or service, and both applications cannot use the same port simultaneously. 

For this type of issue, where you see one of the keywords: eaddrinuse, already in use, errno: -98, etc. You can run one of the following commands in the terminal. Please replace the <PORT NO> which you want to kill. 

1. npx kill-port <PORT NO> (Sometimes, you may need to do it twice.)

2. lsof -t -i tcp:<PORT NO> | xargs kill -9

The above steps will kill the port that was previously taken by some process and is now free to use. After running the command, you can start the backend using npm start. So that you can use it.

Deployed backend to Render but now backend is not working again (ID: GQ2)

If you are facing the issue that previously the backend was working and now, it’s not working then, this type of issue arises when we don’t use the API. This happens because we are using the free services and if we don’t use them for services, then our deployed backend service goes into standby mode. 

To resolve this issue, you should follow the below-mentioned steps:

1. Go to Render’s Website.

2. Click on the Web Server.

3. On the right-hand side, you’ll find these options:

4. Click on the Manual Deploy option and then, click on the “Clear build cache & deploy”.

5. It’ll redeploy your website and your backend will be back again.