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

Gitea gets served at the apex domain #540

Open
AbdulrhmnGhanem opened this issue Jan 4, 2023 · 5 comments
Open

Gitea gets served at the apex domain #540

AbdulrhmnGhanem opened this issue Jan 4, 2023 · 5 comments
Labels
bug Something isn't working

Comments

@AbdulrhmnGhanem
Copy link
Member

https://master.staging.kitspace.dev/

This happened several times, so I don't think this is a random thing.

@AbdulrhmnGhanem AbdulrhmnGhanem added the bug Something isn't working label Jan 4, 2023
@AbdulrhmnGhanem AbdulrhmnGhanem added this to the alpha-2 milestone Jan 4, 2023
@AbdulrhmnGhanem
Copy link
Member Author

The gitea subdomain serves the frontend

image

@AbdulrhmnGhanem
Copy link
Member Author

I couldn't find anything in the logs. But restarting the nginx container fixed the issues.
So far we have seen several issues that gets solved by the restarting nginx. So I will add healthcheck that checks the web services (gitea, frontend, meilisearch) if restart nginx if one of them is inaccissible.

@kasbah
Copy link
Member

kasbah commented Jan 5, 2023

One thing that might be related is that Gitea and frontend are both on port 3000 on their respective containers. Maybe we can work around this by using a different port for the frontend?

@AbdulrhmnGhanem
Copy link
Member Author

If this is the case then there's something wrong with the docker network layer; we use the service name.

proxy_pass http://gitea:3000;

I will change the port anyways, just in case.

@kasbah kasbah changed the title Gitea get served at the apex domain Gitea gets served at the apex domain Jan 9, 2023
@kasbah kasbah removed this from the alpha-2 milestone Jul 4, 2023
@kasbah
Copy link
Member

kasbah commented Jul 4, 2023

Working around it with healthcheck restarting Nginx for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants