Cannot get passed initial configuration #9248

Closed
opened 2025-11-02 08:33:13 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @tamis-laan on GitHub (Jul 21, 2022).

Description

Using docker (compose) to host gitea:

version: '3'

services:
  gitea:
    image: gitea/gitea:1.16.8
    environment:
      - GITEA__server__PROTOCOL=http
      # - GITEA__server__ROOT_URL=https://git.mydomain.com/
      - GITEA__service__DISABLE_REGISTRATION=1
      - GITEA__repository__DEFAULT_PRIVATE=private
      - GITEA__database__DB_TYPE=sqlite3
    volumes:
      - gitea:/data
      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
    ports:
      - '3002:3000'
    restart: unless-stopped

volumes:
  gitea:
    name: serv-gitea

On http://server:3002 I find the initial configuration screen. There I add the administrator user, password and email. Pressing the Install Gitea button starts the browser loading but nothing happens. A refresh again shows the initial configuration screen.

Gitea Version

1.16.8

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

Docker container

Database

SQLite

Originally created by @tamis-laan on GitHub (Jul 21, 2022). ### Description Using docker (compose) to host gitea: ``` yaml version: '3' services: gitea: image: gitea/gitea:1.16.8 environment: - GITEA__server__PROTOCOL=http # - GITEA__server__ROOT_URL=https://git.mydomain.com/ - GITEA__service__DISABLE_REGISTRATION=1 - GITEA__repository__DEFAULT_PRIVATE=private - GITEA__database__DB_TYPE=sqlite3 volumes: - gitea:/data - /etc/timezone:/etc/timezone:ro - /etc/localtime:/etc/localtime:ro ports: - '3002:3000' restart: unless-stopped volumes: gitea: name: serv-gitea ``` On http://server:3002 I find the initial configuration screen. There I add the administrator user, password and email. Pressing the `Install Gitea` button starts the browser loading but nothing happens. A refresh again shows the initial configuration screen. ### Gitea Version 1.16.8 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? Docker container ### Database SQLite
GiteaMirror added the issue/needs-feedback label 2025-11-02 08:33:13 -06:00
Author
Owner

@wxiaoguang commented on GitHub (Jul 22, 2022):

Please provide logs.

I guess your container can not write files to your volume.

@wxiaoguang commented on GitHub (Jul 22, 2022): Please provide logs. I guess your container can not write files to your volume.
Author
Owner

@tamis-laan commented on GitHub (Jul 22, 2022):

I managed to find the problem, apparently GITEA__database__DB_TYPE=sqlite3 is not allowed. Removing this line reverts to the default which is also sqlite3. Kind of strange that this breaks gitea.

@tamis-laan commented on GitHub (Jul 22, 2022): I managed to find the problem, apparently `GITEA__database__DB_TYPE=sqlite3` is not allowed. Removing this line reverts to the default which is also `sqlite3`. Kind of strange that this breaks gitea.
Author
Owner

@zeripath commented on GitHub (Jul 22, 2022):

Removing GITEA__database__DB_TYPE=sqlite3 from the configuration is extremely unlikely to be relevant or have solved anything in and of itself.

Logging would have told us what was happening - and without logs we cannot tell you what has happened or provide any advice.

I'm going to close this - please reopen if you can provide logs.

@zeripath commented on GitHub (Jul 22, 2022): Removing `GITEA__database__DB_TYPE=sqlite3` from the configuration is extremely unlikely to be relevant or have solved anything in and of itself. Logging would have told us what was happening - and without logs we cannot tell you what has happened or provide any advice. I'm going to close this - please reopen if you can provide logs.
Author
Owner

@wxiaoguang commented on GitHub (Jul 22, 2022):

I think I find the problem now.

You are using '3002:3000', then you visit 127.0.0.1:3002 to install.

However , after installation, Gitea will auto redirect you to localhost:3000 (aka ROOT_URL), then you will see another fresh Gitea instance.

It's a bug of Gitea's ROOT_URL mechanism.

@wxiaoguang commented on GitHub (Jul 22, 2022): I think I find the problem now. You are using `'3002:3000'`, then you visit `127.0.0.1:3002` to install. However , after installation, Gitea will auto redirect you to `localhost:3000` (aka ROOT_URL), then you will see another fresh Gitea instance. It's a bug of Gitea's ROOT_URL mechanism. * https://github.com/go-gitea/gitea/issues/19345 * https://github.com/go-gitea/gitea/issues/20089
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#9248