Gitea Web UI is not accessible still on v4.0.0-beta.434

[tunazorlu]

When I try to deploy Gitea Service on my coolify server I can not access it by the default port 3000

Steps To Reproduce
1 Go to coolify
2 deploy Gitea
3 try to open Gitea web UI

Version
v4.0.0-beta.434

Update: this bug does not exists now ( using v4.0.0-beta.347 )

Originally posted by @harish2704 in #985

Well i encounter the same issue on v4.0.0-beta.434 and did the same thing as what you said here: #985 (comment) and it works that way.

[Cinzya]

I can't really reproduce your problem, it seems to work out of the box for me without any changes needed. Which template in specific are you trying to deploy? Coolify offers 4 different Gitea templates.

[ShadowArcanist]

Just now I tested all 4 templates we have for Gitea and all of them are working fine out of the box

[madLinux7]

I'm encountering the same problem with Gitea Services.

I'm not exactly sure why it works seamlessly for other people like @Cinzya and @ShadowArcanist out-of-the-box. Personally I self-host my Coolify using an Alpine VPS.

Anyways, I found a way to resolve the issue by editing the docker compose file:

services-> gitea

The gitea service is missing a traefik label, add (replace ${RESOURCE_ID} with your actual resource ID as Coolify won't to it automatically):

labels:
 - traefik.http.services.${RESOURCE_ID}-gitea.loadbalancer.server.port=3000

networks

At the very bottom add:

networks:
  coolify:
    external: true

After applying these manual changes I am able to access the the Web UI on port 3000 like expected.

[Cinzya]

@tunazorlu @madLinux7 what is the exact problem you are facing with Gitea?
Any error messages?

[tunazorlu]

@tunazorlu @madLinux7 what is the exact problem you are facing with Gitea? Any error messages?

While some of us have no issues, others are experiencing problems with the Gitea Server publishing to the relevant domain/subdomain. This is because when we create the compose file by default and access the relevant domain/subdomain, it appears as if Gitea has never been published.

However, if we define "labels: - traefik.http.services.${RESOURCE_ID}-gitea.loadbalancer.server.port=3000" in the compose field, the Gitea server successfully publishes with the relevant domain/subdomain.

[harish2704]

I can imagine one possible reason for this issue ( ie, some people facing problem while others are not ).

while setting up an instance, we will see a dialog box where we need to enter our domain name address.
The default value in the input box will look similar to this
https:3234532456sdrgsd.example.com:3000

Please note the port number specified in this url.

While entering our own domain value, some people may remove the port number from the URL and others may not .

To work everything as expected, the port number should be there.

For those who remove that port number, the service will not work as expected.

For eg: If i want to use "https://git.harishk.in", I have to enter https://git.harishk.in:3000 in the input box instead of "https://git.harishk.in"

Can anyone confirm whether this is the problem or not ?

[Cinzya]

@harish2704 you are correct. The container label mentioned by @tunazorlu is automatically set by Coolify depending on the port you give the domain in the domain field. If you remove the port from it, the labels will also disappear.

[harish2704]

@Cinzya If that is the case , it would be better to inform this information to end user via some tool tip or info message while entering the custom domain.