Unable to access the apps that were connected to git (internal server error) after redeployment

[spare whale]

Hi Appsmith Team, we redeployed appsmith to modify some environment variable. Now we are unable to access the apps that were connected to git (getting internal server error). Same error also appears when trying to add a new repo. The place where SSH key should be is blank.
Version : Appsmith Community v1.11

[carmine meteor]

Hello! I'm AppyCoder, your Appsmith support bot. Let's try to address the
problem with Git integration after redeploying your instance. Typically, an
internal server error when trying to access repos connected to Git in Appsmith
might be related to a misconfiguration of the Git service within the Appsmith
setup. Since your SSH key area is blank, it seems like your SSH keys used for
Git operations may have been lost or not correctly set after the redeployment.
Here are some steps to troubleshoot the issue: 1. Check if the environment
variables related to Git are correctly set and if they have been properly loaded
by the Appsmith instance. 2. Ensure that the SSH key for Git is present in the
appropriate directory and that the Appsmith instance has the correct permissions
to access it. 3. Restart the services to ensure that all your new changes and
environment variables are in effect. 4. Check the logs for any errors related to
Git operations. The logs may provide more insights into what might be going
wrong. Please check these points and let me know if you need further assistance
or if you encounter any specific errors in the process. If the issue persists
and it's urgent, we can escalate this to a human agent. If you don't find my
response helpful, you can request to speak to a human agent

[carmine meteor]

Hello! I'm Amelia with Appsmith Support. 👋
Please try the below steps and provide us with the required information:

1. Recreate the deploy key and see if that helps.
2. If you are using a self-hosted instance, go to the server container and ping
   the Git repository URL to verify that access is not blocked for some reason.
3. To further debug the issue, please share a loom.com screen recording
   demonstrating the steps leading up to the error.
4. Please send us the server logs by following the steps from this guide:
   https://docs.appsmith.com/learning-and-resources/how-to-guides/how-to-get-container-logs).

[spare whale]

This Internal server error is happening when i am trying to connect to new git repos as well.

[carmine meteor]

If you're encountering an internal server error when trying to connect to new
Git repositories as well, it appears that the issue is not just with the
existing Git connections but also with the Git configuration or service on your
Appsmith instance. Here's what we should do next: - Verify that the Git service
inside your Appsmith deployment is setup properly. - Check that the correct SSH
private key is available in the deployment and that Appsmith has permissions to
use it. - Look into the Appsmith server logs to identify any Git-related error
messages. This can provide clues to what might be causing the internal server
error. In the case of an internal server error, detailed logs are essential to
diagnosing the problem. Please check the server logs, which can usually be found
depending on how you deployed Appsmith (Docker, Kubernetes, etc.). If you
continue to face issues, it would be best for a human support agent to take a
closer look at your specific setup and logs. Let me know if you would like to be
transferred to one. If you don't find my response helpful, you can request to
speak to a human agent

[spare whale]

FYI, yes this is a self-hosted instance

1. I can't reach that step. Internal server error comes before that step.
2. It's not blocked. Still will check. It was connecting just fine before the redeployment.
3. Loom recording : https://www.loom.com/share/3491a0ab4c8f4496bae902b4fc70be09?sid=7a0ea61f-e726-4dd7-88d0-72dc29c34e4c
4. Will share if required (as information security team's approval is required for that).

[carmine meteor]

It seems there might be a problem with the configuration of your self-hosted
Appsmith instance after redeployment. Since you're experiencing the issue before
even reaching the step where the SSH key is needed and given the internal server
error, examining the logs should be the next step. If you still have access to
the server where Appsmith is running, please follow these steps to check the
logs: 1. Access the server where Appsmith is deployed. 2. Locate the logs for
Appsmith. If you used Docker for deployment, you can use a command like docker logs to retrieve the logs from the container. Please check for error messages
particularly around the Git operations and SSH key handling. If any specific
message stands out, it could guide us toward a solution. Considering the
security protocols at your organization, if you need approval to share
information, please go through the necessary process to get the logs. If
additional help is needed or you prefer to have a human take a direct look at
this, please let me know. If you don't find my response helpful, you can request
to speak to a human agent

[spare whale]

requesting to speak to a human agent

[carmine meteor]

Someone from our team will reach out to you on this thread. In the meantime, you
can have a look at our documentation to try & resolve your query
https://docs.appsmith.com?utm=bot

[carmine meteor]

Hello! I'm Amelia with Appsmith Support. 👋
We will need the server logs to be able to investigate this further. Please send
them via email to [email protected], add the link to this thread as a
reference, and let us know here once you sent them so we can check.

[carmine meteor]

@spare whale Gentle reminder.