-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
Nothing happens when using the initial configuration page #23986
Comments
I have tested your docker-compose.yaml :
After a few seconds, I can see the login UI. The log looks like this:
From your log , I can see:
Just FYI, I have no more idea about this issue at the moment. |
Does your cookie/domain/browser work correctly? (Just a guess, I am not sure) Maybe there is an error message, but the wrong cookie setting may cause the error message wouldn't be displayed, so you didn't get the error feedback? |
Thank you for testing! Your logs gave me the idea to see if the app.ini was created and it was. I then tried settting the DOMAIN and SSH_DOMAIN from localhost to my servers domain name and see if anything changes. But the result was the same. I also tried with INSTALL_LOCK = true to see any changes and the ORM tried to initialize, but after waiting for the mysql server, it didn't try again, although there were some attempts left. I also tried with a fresh browser. The behaviour was the same. As the logs say, the installer is very slow. Takes my machine more than 60 seconds to finish the POST request. May be my machine, but seems a little odd (in your case 10 seconds). I have no idea what else to try right now. :) |
Hmm ... no idea either. Could the "slow" be the problem? What's your environment (hardware) & limitation? Is there enough CPU and memory resrouce? |
I'm using a Synology DS920+. The performance is ok and I'm running some other docker containers without a problem. I thought Gitea is lightweight and should work. :) I will monitor the CPU and memory the next time I try the install. But since the logs say that the POST request completed, I assume that this is not the problem. Thanks again for your help! |
Looks like it's normal from the provided logs. |
@KuenzelIT Out of curiosity, are you running the docker container on a volume that is using btrfs? I'm encountering something similar in my install as well. However, I'm using a dedicated MariaDB instance running on the Syn box by way of their package center. The install is progressing as I can see it periodically making new tables in my DB, but it is taking its sweet time. I did a bit of digging around and it seems that btrfs and the data checksum checking of files in those shares may be the root of the problem here. See:
To ensure service quality, we recommend not enabling data checksum when the shared folder will be used for the following services: |
Thanks for the idea. Unfortunately I'm not using btrfs. I also haven't tried to install gitea in a while, maybe I'll try again in a few days. |
@KuenzelIT I am currently facing the same issues on a Synology DS224+. I am also running other docker containers without any problems. RAM and CPU load are both under 10% and I am not using btrfs as well. The difference in my environment is, that I use an already installed MySQL instance and no docker container for it. And I use the latest version of gitea not 1.19.0 (didn´t check if the latest is 1.19.0). Did you find any solution? |
I did not find a solution and dropped trying it for now, sorry :( |
I am not sure how I got it working, but I did the installation on my Mac. After loading for a few minutes, I tried to open the webpage on one of my servers. In this moment, the installation was done and I got forwarded to homepage of Gitea. I dn´t know if it was luck or if this is the solution. |
Description
After clicking on "Install Gitea" in the initial configuration the page is loading for a few seconds and then nothing happens and the initial configuration page is still shown, even after visiting the gitea url again. I did not change any options.
Gitea Version
1.19.0
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
https://gist.github.com/KuenzelIT/20f406fc2edf5378d1d1dd4ad9e88cbc
Screenshots
No response
Git Version
No response
Operating System
Synology DSM
How are you running Gitea?
Docker Compose on a Synology:
version: "3"
networks:
gitea:
external: false
services:
server:
image: gitea/gitea:1.19.0
container_name: gitea
environment:
- USER_UID=1026
- USER_GID=100
- GITEA__database__DB_TYPE=mysql
- GITEA__database__HOST=db:3306
- GITEA__database__NAME=gitea
- GITEA__database__USER=gitea
- GITEA__database__PASSWD=gitea
restart: always
networks:
- gitea
volumes:
- ./gitea:/data
- /etc/TZ:/etc/timezone:ro
- /etc/localtime:/etc/localtime:ro
ports:
- "3000:3000"
- "222:22"
depends_on:
- db
db:
image: mysql:8
restart: always
environment:
- MYSQL_ROOT_PASSWORD=gitea
- MYSQL_USER=gitea
- MYSQL_PASSWORD=gitea
- MYSQL_DATABASE=gitea
networks:
- gitea
volumes:
- ./mysql:/var/lib/mysql
Database
MySQL
The text was updated successfully, but these errors were encountered: