Where is default admin password? #1857

New Issue

GiteaMirror · 2025-11-02T04:15:22-06:00

GiteaMirror commented

2025-11-02 04:15:22 -06:00

Originally created by @zloidemon on GitHub (Jun 4, 2018).

Gitea version (or commit ref):
Git version:
Operating system:
Database (use [x]):
- [ X] PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- [X ] Not relevant
Log gist:

Description

Hello, after installation into docker by compose i still don't understand how to login into admin panel. Google didn't help me find default admin password on your web site.

Screenshots

Originally created by @zloidemon on GitHub (Jun 4, 2018).  - Gitea version (or commit ref): - Git version: - Operating system: - Database (use `[x]`): - [ X] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [X ] Not relevant - Log gist: ## Description Hello, after installation into docker by compose i still don't understand how to login into admin panel. Google didn't help me find default admin password on your web site. ## Screenshots

GiteaMirror added the type/question label 2025-11-02 04:15:22 -06:00

GiteaMirror closed this issue

2025-11-02 04:15:22 -06:00

GiteaMirror commented

2025-11-02 04:15:23 -06:00

@l0go commented on GitHub (Jun 4, 2018):

Just use the password for the first account you made

@l0go commented on GitHub (Jun 4, 2018): Just use the password for the first account you made

GiteaMirror commented

2025-11-02 04:15:23 -06:00

@techknowlogick commented on GitHub (Jun 4, 2018):

@zloidemon There is no default password during the install process you would be prompted to create a user, otherwise the first user registered to Gitea becomes the admin.

@techknowlogick commented on GitHub (Jun 4, 2018): @zloidemon There is no default password during the install process you would be prompted to create a user, otherwise the first user registered to Gitea becomes the admin.

GiteaMirror commented

2025-11-02 04:15:23 -06:00

@zloidemon commented on GitHub (Jun 4, 2018):

@techknowlogick thank you. Found at bottom on the install page. I seem better add checking that form before installing with modal window to avoid installation.

@zloidemon commented on GitHub (Jun 4, 2018): @techknowlogick thank you. Found at bottom on the install page. I seem better add checking that form before installing with modal window to avoid installation.

GiteaMirror commented

2025-11-02 04:15:23 -06:00

@lqhuang commented on GitHub (Jun 15, 2019):

Hey. But if I have set DISABLE_REGISTRATION=true from docker environment, how can I login as admin? I can't create a new user. And localhost:3000/install page is not available (404) to access.

@lqhuang commented on GitHub (Jun 15, 2019): Hey. But if I have set `DISABLE_REGISTRATION=true` from docker environment, how can I login as `admin`? I can't create a new user. And `localhost:3000/install` page is not available (`404`) to access.

GiteaMirror commented

2025-11-02 04:15:23 -06:00

@zeripath commented on GitHub (Jun 15, 2019):

Use the command line tool gitea admin create-user. Ensure you have set the config values correctly in particular the -c option for the app.ini.

See https://docs.gitea.io/en-us/command-line/

@zeripath commented on GitHub (Jun 15, 2019): Use the command line tool `gitea admin create-user`. Ensure you have set the config values correctly in particular the -c option for the app.ini. See https://docs.gitea.io/en-us/command-line/

GiteaMirror commented

2025-11-02 04:15:24 -06:00

@lqhuang commented on GitHub (Jun 17, 2019):

@zeripath Thanks. Yeah, for now, I did this to initialized manually after creating docker successfully. But it still need do some extra "hack in" work, which cannot left everything in a single yaml configuration.

In docker-compose, there is still no post-run/postUp/onrun feature to execute custom action after container is ready. I think that would be a much better way to initialize. See docker-compose issue#1510 and docker-compose issue#1809 for more discussions.

Or let gitea add a specific process to handle this DISABLE_REGISTRATION=TRUE case while using docker.

Regards:)

@lqhuang commented on GitHub (Jun 17, 2019): @zeripath Thanks. Yeah, for now, I did this to initialized manually after creating docker successfully. But it still need do some extra "hack in" work, which cannot left everything in a single `yaml` configuration. In `docker-compose`, there is still no `post-run`/`postUp`/`onrun` feature to execute custom action after container is ready. I think that would be a much better way to initialize. See [docker-compose issue#1510](https://github.com/docker/compose/issues/1510) and [docker-compose issue#1809](https://github.com/docker/compose/issues/1510) for more discussions. Or let `gitea` add a specific process to handle this `DISABLE_REGISTRATION=TRUE` case while using `docker`. Regards:)

GiteaMirror referenced this issue

2025-11-02 12:02:58 -06:00

[PR #1931] [CLOSED] fix #1857 trim Windows line ending #16129

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#1857