YouTrack and Gitea Integration Issue with Docker Containers #14291

New Issue

GiteaMirror · 2025-11-02T11:08:50-06:00

GiteaMirror commented

2025-11-02 11:08:50 -06:00

Originally created by @Zabrane on GitHub (Mar 23, 2025).

Description

YouTrack and Gitea Integration Issue with Docker Containers

I'm experiencing difficulties connecting YouTrack 2025.1.64291 with Gitea 1.23.5 in a Docker environment. Both services are running on the same Ubuntu 22.04 LTS machine within a bridge network, with Nginx handling SSL termination for both services.

When attempting to configure a new VCS Integration in YouTrack, I consistently receive an HTTP 403 Forbidden error. This occurs despite carefully reviewing my configuration settings, which appear to be correctly set up according to documentation.

Examining the Gitea logs reveals the following error message:

2025/03/23 07:24:49 ...eb/routing/logger.go:102:func1() [I] router: completed POST /api/v1/repos/company/avaro/hooks for 172.17.0.3:0, 403 Forbidden in 80.0ms @ v1/api.go:297(v1.Routes.func2.tokenRequiresScopes.29)

The error message suggests there might be an issue with token permissions or scopes. The specific reference to tokenRequiresScopes in the error path indicates that the API token I'm using may not have the necessary permissions to create webhooks.

Has anyone successfully integrated these specific versions of YouTrack and Gitea in a similar Docker setup? What specific permission scopes does the Gitea access token need for proper YouTrack integration? Are there any particular configuration adjustments needed for containers communicating over a bridge network?

Any guidance would be greatly appreciated!

Gitea Version

1.23.5

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

Git Version

No response

Operating System

Ubuntu 22.04 LTS

How are you running Gitea?

I'm running Gitea 1.23.5 in a Docker environment

Database

None

Originally created by @Zabrane on GitHub (Mar 23, 2025). ### Description # YouTrack and Gitea Integration Issue with Docker Containers I'm experiencing difficulties connecting `YouTrack 2025.1.64291` with `Gitea 1.23.5` in a Docker environment. Both services are running on the same `Ubuntu 22.04 LTS` machine within a bridge network, with `Nginx` handling SSL termination for both services. When attempting to configure a new VCS Integration in YouTrack, I consistently receive an **HTTP 403 Forbidden** error. This occurs despite carefully reviewing my configuration settings, which appear to be correctly set up according to documentation. Examining the `Gitea logs` reveals the following error message: ``` 2025/03/23 07:24:49 ...eb/routing/logger.go:102:func1() [I] router: completed POST /api/v1/repos/company/avaro/hooks for 172.17.0.3:0, 403 Forbidden in 80.0ms @ v1/api.go:297(v1.Routes.func2.tokenRequiresScopes.29) ``` The error message suggests there might be an issue with token permissions or scopes. The specific reference to `tokenRequiresScopes` in the error path indicates that the API token I'm using may not have the necessary permissions to create webhooks. Has anyone successfully integrated these specific versions of `YouTrack` and `Gitea` in a similar Docker setup? What specific permission scopes does the `Gitea` access token need for proper `YouTrack` integration? Are there any particular configuration adjustments needed for containers communicating over a bridge network? Any guidance would be greatly appreciated! ### Gitea Version 1.23.5 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots ![Image](https://github.com/user-attachments/assets/b02eb5f5-b677-47b3-b990-de0f2d0f1c79) ### Git Version _No response_ ### Operating System Ubuntu 22.04 LTS ### How are you running Gitea? I'm running Gitea 1.23.5 in a Docker environment ### Database None

GiteaMirror added the issue/not-a-bug label 2025-11-02 11:08:50 -06:00

GiteaMirror closed this issue

2025-11-02 11:08:50 -06:00

GiteaMirror commented

2025-11-02 11:08:51 -06:00

@Zabrane commented on GitHub (Mar 23, 2025):

I figured out the issue.
repository has to be Read and Write and all remaining options can can be set to Read

@Zabrane commented on GitHub (Mar 23, 2025): I figured out the issue. `repository` has to be `Read and Write` and all remaining options can can be set to `Read` ![Image](https://github.com/user-attachments/assets/d7993eac-00fb-4df5-bb4b-d37df5f6fccc)

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#14291