maxking / maxking/forgejo-vscode

Authentication errors (troubleshooting section did not help)

Open
#23 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
44m
Merged PRs (30d)
2

Description

Migrated from Codeberg issue #34. Originally opened by Codeberg user RandomPenguin on 2026-09-06T14:46:06+02:00.


I installed this extension on my Code - OSS instance today and wanted to add it to my Codeberg account to interface with private repositories. I followed the instructions to create a PAT using the command palette, here are the options I did:

  • Instance URL: https://codeberg.org
  • Token: <my private token>
    • The application has all repository access and has read:issue and write:repository permissions
  • The connection test fails here.

I tried the troubleshooting section on the README (regenerating the token, changing write:repository to read:repository), but the connection test fails instantly. Here's the error message:

✗ Failed to connect to Codeberg. Check your token and instance URL.

I don't know what I would be missing...

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the README troubleshooting section and the command-palette flow used to create a PAT, then reproduce the failing connection test against Codeberg with the reported permissions. Trace the authentication request from that entry point and identify why it fails instantly; done means the connection test succeeds for a private repository or reports the actual cause.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
authentication
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.