Troubleshooting Connection Issues - archimatetool/archi-modelrepository-plugin GitHub Wiki

Troubleshooting

Connecting to Git repositories is not always straightforward. There can be many factors involved - authentication, proxy settings, tokens, and so on. This page attempts to document some of the issues and offers some suggestions to solve them.

If you have solved any of these issues please add your comments to this page.

When using HTTPS a Personal Access Token may be needed

Some git hosting providers such as GitHub require the use of a Personal Access Token for HTTPS authentication

Here are some examples on how to create a PAT:

Make sure you use your username and your 'personal access token' as your password.

I get this error message

"git-upload-pack not permitted on..."

This error message can occur for a number of reasons. Unfortunately, this message is not very helpful and is a general purpose message from JGit the git library.

Some things to check:

  • Proxy configuration (if in use) - "did the proxy block the http-post?"
  • Git server using a self-signed certificate or one from a custom PKI (in such case the certificate must be manually added to the JVM's truststore) - "did https fail on connect?"
  • Access rights in Git platform - "does this user/id actually have permissions?"
  • Git platform access management based on user/password on the web frontend but requiring a token for repositories
  • Git platform access management based on SSO on the web frontend but requiring a user/password or a token for repositories
  • On some occasions, JGit (the Java based implementation of Git) can try to use your local and native git client, leading to some issues
  • Possible issues related to MTU when working through a VPN
  • Enable SSO on my token (with a company account) - "did you 'authorize' the token against your sso provider after you created it?"

Issue Tracker references

https://github.com/archimatetool/archi-modelrepository-plugin/issues/117