Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Gitea Web UI is not accessible (again) #5287

Open
shageman opened this issue Mar 5, 2025 · 0 comments
Open

[Bug]: Gitea Web UI is not accessible (again) #5287

shageman opened this issue Mar 5, 2025 · 0 comments

Comments

@shageman
Copy link

shageman commented Mar 5, 2025

FWIW I just had to do the below on v4.0.0-beta.394 after I ran into the same issue after a restart of the gitea container.

Hello Coolify team,

I am still facing this bug while running a fresh Gitea instance .

Coolify version: v4.0.0-beta.325

I solved this by problem by adding a proper label in docker-compose file . That is,


services:

  gitea:

    image: 'gitea/gitea:latest'

    labels:

      - "traefik.http.services.gitea.loadbalancer.server.port=3000"

where, "gitea" is the random name I given to the service .

Please note that , I checked the documentation of traefik proxy and found that above mentioned bug is expected as per the documentation of traefik.

As per the https://doc.traefik.io/traefik/providers/docker/#port-detection,

they say

If a container exposes multiple ports, then Traefik uses the lowest port. E.g. if 80 and 8080 are exposed, Traefik will use 80.

As the above rule, this bug is possible. I think it will affect similar services also ( like gitlab )

Originally posted by @harish2704 in #985

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant