57 lines
4.8 KiB
Markdown
57 lines
4.8 KiB
Markdown
---
|
|
tags:
|
|
- Documentation
|
|
- Bookstack
|
|
- Notes
|
|
---
|
|
# Troubleshooting
|
|
|
|
# Create Directory structure with subdirectories
|
|
|
|
It looks like your Git client (likely GitAhead, GitHub Desktop, or a similar GUI tool) ran into a credential roadblock while trying to clone that repository. Since you're dealing with a `Docker-Boilerplates` repo, getting this sorted quickly so you can deploy is the priority.
|
|
|
|
Here is how to troubleshoot and fix this, depending on how you connect to GitHub.
|
|
|
|
## 1. The Most Common Fix: Personal Access Tokens (HTTPS)
|
|
|
|
If you are cloning via **HTTPS** (a URL starting with `https://github.com/...`), GitHub **no longer accepts your standard account password** for Git operations.
|
|
|
|
### Step 1: Generate a PAT on GitHub
|
|
|
|
<div class="container" id="bkmrk-go-to-your-github-ac"><div class="markdown markdown-main-panel tutor-markdown-rendering enable-luminous-fast-follows stronger enable-updated-hr-color" dir="ltr">1. Go to your GitHub account **Settings** > **Developer Settings** > **Personal Access Tokens** (Tokens classic).
|
|
2. Click **Generate new token**.
|
|
3. Give it a descriptive name (e.g., "Homelab Desktop") and select the **`repo`** scope (this gives full control of private repositories).
|
|
4. Click **Generate token** and **copy it immediately** (you won't see it again).
|
|
|
|
</div></div>### Step 2: Use it in your Git Client
|
|
|
|
When your Git GUI prompts you for your password during the retry, **paste the PAT instead of your actual GitHub password**.
|
|
|
|
## 2. The SSH Route (If you use `git@github.com:...`)
|
|
|
|
If you are cloning via **SSH**, GitHub doesn't use passwords at all. Instead, it relies on your local SSH key.
|
|
|
|
<div class="container" id="bkmrk-check-your-active-ke"><div class="markdown markdown-main-panel tutor-markdown-rendering enable-luminous-fast-follows stronger enable-updated-hr-color" dir="ltr">- **Check your active keys:** Open a terminal and run `ssh-add -l` to see if your private key is loaded into your SSH agent.
|
|
- **Add your key:** If it isn't listed, add it using:
|
|
|
|
<div class="code-block ng-tns-c2069566202-321 ng-animate-disabled ng-trigger ng-trigger-codeBlockRevealAnimation"><div class="formatted-code-block-internal-container ng-tns-c2069566202-321"><div class="animated-opacity ng-tns-c2069566202-321"><div class="code-block-decoration header-formatted gds-emphasized-body-m ng-tns-c2069566202-321 ng-star-inserted"><span class="ng-tns-c2069566202-321">Bash</span><div class="buttons ng-tns-c2069566202-321 ng-star-inserted"></div></div></div></div></div>```
|
|
ssh-add ~/.ssh/id_ed25519
|
|
|
|
```
|
|
|
|
<div class="code-block ng-tns-c2069566202-321 ng-animate-disabled ng-trigger ng-trigger-codeBlockRevealAnimation"><div class="formatted-code-block-internal-container ng-tns-c2069566202-321"><div class="animated-opacity ng-tns-c2069566202-321"></div></div></div>*(Replace `id_ed25519` with the actual name of your private key file).*
|
|
- **Verify connection:** Test your connection to GitHub directly via terminal:
|
|
|
|
<div class="code-block ng-tns-c2069566202-322 ng-animate-disabled ng-trigger ng-trigger-codeBlockRevealAnimation"><div class="formatted-code-block-internal-container ng-tns-c2069566202-322"><div class="animated-opacity ng-tns-c2069566202-322"><div class="code-block-decoration header-formatted gds-emphasized-body-m ng-tns-c2069566202-322 ng-star-inserted"><span class="ng-tns-c2069566202-322">Bash</span><div class="buttons ng-tns-c2069566202-322 ng-star-inserted"></div></div></div></div></div>```
|
|
ssh -T git@github.com
|
|
|
|
```
|
|
|
|
<div class="code-block ng-tns-c2069566202-322 ng-animate-disabled ng-trigger ng-trigger-codeBlockRevealAnimation"><div class="formatted-code-block-internal-container ng-tns-c2069566202-322"><div class="animated-opacity ng-tns-c2069566202-322"></div></div></div>If it says *"Hi \[YourUsername\]! You've successfully authenticated..."*, your SSH setup is perfect, and the issue is just your Git GUI not pointing to the correct key.
|
|
|
|
</div></div>## 3. Quick Sanity Checks
|
|
|
|
<div class="container" id="bkmrk-are-you-logged-in-wi"><div class="markdown markdown-main-panel tutor-markdown-rendering enable-luminous-fast-follows stronger enable-updated-hr-color" dir="ltr">- **Are you logged in within the app?** If this is a GUI like GitAhead or GitHub Desktop, go to **File > Options (or Preferences) > Accounts** and verify your GitHub account is actively signed in. If it is, **log out and log back in** to force a token refresh.
|
|
- **Repository Permissions:** Double-check that the repository actually exists at that exact URL and that your account hasn't lost access (or that it hasn't been archived by the owner).
|
|
|
|
</div></div><div class="container" id="bkmrk-"><div class="markdown markdown-main-panel tutor-markdown-rendering enable-luminous-fast-follows stronger enable-updated-hr-color" dir="ltr" id="bkmrk--1"></div></div> |