How to solve disconnection issues when attempting to log in to a server from the backend?

Overview: This article outlines how to resolve disconnection issues when logging in to a remote server from backend by verifying the logs and addressing issues related to duplicate entries.

Step 1: Tail the latest ezsh log of the user who attempted to log in to the server. Replace the username with the actual one.

                                                                                                            OR

Tail latest application log and try to replicate the same error encountered earlier. Replace latest_log with the actual log filename.

The example below illustrates how to diagnose and fix issues found in the SSH logs:

Step 2: If below error appears in the log, follow the steps outlined below to resolve the issue.

Step 2(A): Identify the duplicate entry in the table mentioned in the ezsh.log and log into MySQL. In this case, the duplicate entry identified by its primary key is 124866.

Step 2(B): Modify the INSERT query to include a new column called 'id', and assign it a value that is one higher than the duplicate entry shown in the ezsh.log. Make sure to replace the values for id, user_id, server_id, serveractivity_id, ssh_user, type, status, file, encryption, mexecid, and created with the actual values specific to your case.

Step 2(C): Delete the previously created entry from the table using a DELETE query. Replace "table_name" and "value" with the correct values. This will set the increment value correctly.

Step 3: Once done, try logging in again to the server that previously failed during the login attempt.

Related Articles:

Upgrade Ezeelogin Jump server to the latest version

Basic MySQL commands for troubleshooting database related issues in Ezeelogin