Hello! I'm AppySmithBot, your helpful assistant for Appsmith-related queries.
When you encounter the "Fingerprint sha256 has already been taken" error on
GitLab, it suggests that a previous SSH deploy key generated by AppSmith has
been used on a different repository within GitLab, and cannot be reused. Please
follow these steps to create a new valid SSH deploy key that Appsmith will
recognize: 1. Log in to your Appsmith instance. 2. Navigate to the 'Profile'
section, where your SSH keys are managed. 3. Generate a new SSH key pair
(usually, there will be an option or button to regenerate or create new keys).
4. Once the new SSH keys are generated, copy the new public SSH key. 5. Go to
your self-hosted GitLab instance, to the repository settings, and then to the
'Deploy Keys' section. 6. Add the new public SSH key as a new deploy key. If you
are unsure of how to navigate to the SSH key management in Appsmith, could you
let me know if you need more specific instructions? If you don't find my
response helpful, you can request to speak to a human agent
#Fingerprint sha256 has already been taken
storm pumiceBOT
median roost
I not sure how to navigate to the SSH key management in appsmith.
storm pumiceBOT
To navigate to the SSH key management in Appsmith and create a new SSH deploy
key, follow these steps: 1. Open your Appsmith instance and log in. 2. Go to the
'Settings' page by clicking on the 'Settings' gear icon on the bottom left of
the Appsmith Dashboard. 3. Look for a section related to 'Version Control' or
'Git Configuration'. 4. Within this area, there should be an option to manage
SSH keys. You might find a 'Regenerate Keys', 'Generate SSH Keys', or similar
button. 5. Click on it to create a new SSH key pair. 6. After the keys are
generated, copy the new public SSH key. Once you have the new public SSH key,
you can proceed to add it to your GitLab repository by going to your GitLab
instance, the repository's settings, and the 'Deploy Keys' section where you can
remove the old key (if necessary) and add the new one. Remember to save or apply
changes in both Appsmith and GitLab. If you require more detailed instructions
or encounter any issues, please let me know. If you don't find my response
helpful, you can request to speak to a human agent
median roost
speak to human agent
storm pumiceBOT
Someone from our team will reach out to you on this thread. If you change your
mind, you can ask to speak to an AI agent at any time.
median roost
can I generate a new ssh key in appsmith?
i already has a previously gitlab repository that was connected to my appsmith. But somehow the key loses access. I need a new key but keeping the repo.
storm pumiceBOT
Hello!
Can you elaborate on what you mean when you say you lost repository access in
Appsmith and confirm your current version of Appsmith? Disconnecting an app from
git is an irreversible action, and you will need to re-import your application
from git to resolve this issue.
median roost
Appsmith v1.9.56
The helm app restarted. When it came back, the git control version settings doesn't has access to my repository anymore.
When I copy de SSH key, gitlab says "fingerprint sha256 has already been taken". But I already removed any previous deploy key.