github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-18 14:12:40 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Gitea in Synology docker restarts and enters the setup page after setting the boot setup page (using MySQL). Using SQLite does not have this problem #8218

New Issue
Closed
opened 2025-11-02 07:58:02 -06:00 by GiteaMirror · 13 comments
GiteaMirror commented 2025-11-02 07:58:02 -06:00
Owner
Copy Link

Originally created by @caifenglin on GitHub (Dec 6, 2021).

Gitea Version

1.15.7

Operating System

Docker x86

Browser Version

Chrome 96.0.4664.45

Can you reproduce the bug on the Gitea demo site?

No

Description

Can you provide a tutorial for synology to install gitea? I install gitea through synology's docker. I normally enter the setting page. After setting the parameters, I can't find the page. After restarting gitea, I'm still on the setting page. What should I do? The version is 1.15.7。Gitea in Synology docker restarts and enters the setup page after setting the boot setup page (using MySQL). Using SQLite does not have this problem

Screenshots

image
image
Gitea.csv

Originally created by @caifenglin on GitHub (Dec 6, 2021). ### Gitea Version 1.15.7 ### Operating System Docker x86 ### Browser Version Chrome 96.0.4664.45 ### Can you reproduce the bug on the Gitea demo site? No ### Description Can you provide a tutorial for synology to install gitea? I install gitea through synology's docker. I normally enter the setting page. After setting the parameters, I can't find the page. After restarting gitea, I'm still on the setting page. What should I do? The version is 1.15.7。Gitea in Synology docker restarts and enters the setup page after setting the boot setup page (using MySQL). Using SQLite does not have this problem ### Screenshots ![image](https://user-images.githubusercontent.com/78671821/144851298-2d4dedb2-773e-4eb0-ae6d-11a610877f66.png) ![image](https://user-images.githubusercontent.com/78671821/144851393-39823a5b-317f-4550-84ff-8b946181621d.png) [Gitea.csv](https://github.com/go-gitea/gitea/files/7660875/Gitea.csv)
GiteaMirror commented 2025-11-02 07:58:03 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Dec 6, 2021):

We need to see the logs.

@zeripath commented on GitHub (Dec 6, 2021): We need to see the logs.
GiteaMirror commented 2025-11-02 07:58:04 -06:00
Author
Owner
Copy Link

@caifenglin commented on GitHub (Dec 7, 2021):

The log folder is empty. Synology logs are like gitea.csv above

@caifenglin commented on GitHub (Dec 7, 2021): The log folder is empty. Synology logs are like gitea.csv above
GiteaMirror commented 2025-11-02 07:58:05 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Dec 7, 2021):

It's not really fair to provide logs in a nonstandard format.

The provided logs in gitea.csv only appear to show that gitea gets killed by Synology when it tries to talk to the mysql server.

This implies to me that you haven't allowed the docker to talk to the mysql server or haven't provided a mysql docker for it to run with.

@zeripath commented on GitHub (Dec 7, 2021): It's not really fair to provide logs in a nonstandard format. The provided logs in gitea.csv only appear to show that gitea gets killed by Synology when it tries to talk to the mysql server. This implies to me that you haven't allowed the docker to talk to the mysql server or haven't provided a mysql docker for it to run with.
GiteaMirror commented 2025-11-02 07:58:05 -06:00
Author
Owner
Copy Link

@caifenglin commented on GitHub (Dec 7, 2021):

My MySQL service is in another docker environment. What you said is very possible, but how can I deal with this situation to avoid being prohibited from communicating by Synology

@caifenglin commented on GitHub (Dec 7, 2021): My MySQL service is in another docker environment. What you said is very possible, but how can I deal with this situation to avoid being prohibited from communicating by Synology
GiteaMirror commented 2025-11-02 07:58:06 -06:00
Author
Owner
Copy Link

@caifenglin commented on GitHub (Dec 7, 2021):

Should I try to let MySQL use the host network and report the results when my test is completed

@caifenglin commented on GitHub (Dec 7, 2021): Should I try to let MySQL use the host network and report the results when my test is completed
GiteaMirror commented 2025-11-02 07:58:07 -06:00
Author
Owner
Copy Link

@caifenglin commented on GitHub (Dec 7, 2021):

Can anyone provide a tutorial on the installation of Synology gitea，Thank you very mach

@caifenglin commented on GitHub (Dec 7, 2021): Can anyone provide a tutorial on the installation of Synology gitea，Thank you very mach
GiteaMirror commented 2025-11-02 07:58:07 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Dec 7, 2021):

You may join the QQ Group 328432459 to find more users to ask for help. I will close this issue since it is not a bug, but it's environment related.

@wxiaoguang commented on GitHub (Dec 7, 2021): You may join the QQ Group 328432459 to find more users to ask for help. I will close this issue since it is not a bug, but it's environment related.
GiteaMirror commented 2025-11-02 07:58:07 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Dec 7, 2021):

ps: if you see the install page again and again (while you have ever installed it), I think it might be caused by that the generated config file app.ini is lost during restart. Some files of Gitea need to be stored correctly. I would suggest you try to install Gitea in a simple Linux server to get familiar to it and then debug the installation in Synology Nas.

@wxiaoguang commented on GitHub (Dec 7, 2021): ps: if you see the install page again and again (while you have ever installed it), I think it might be caused by that the generated config file `app.ini` is lost during restart. Some files of Gitea need to be stored correctly. I would suggest you try to install Gitea in a simple Linux server to get familiar to it and then debug the installation in Synology Nas.
GiteaMirror commented 2025-11-02 07:58:08 -06:00
Author
Owner
Copy Link

@caifenglin commented on GitHub (Dec 7, 2021):

image
image
image
image
I still failed. I don't know how you can do it. I used MySQL with GIT and root users, but they didn't work. 21 tables were generated, which seems wrong

@caifenglin commented on GitHub (Dec 7, 2021): ![image](https://user-images.githubusercontent.com/78671821/145032626-2e09c670-e601-4b5b-8fcf-12eca014e546.png) ![image](https://user-images.githubusercontent.com/78671821/145032667-e48a7a1c-a63c-4f92-b33a-cb3bbc84790f.png) ![image](https://user-images.githubusercontent.com/78671821/145032691-50c11ffa-ea05-4055-8959-3df7ed07c05a.png) ![image](https://user-images.githubusercontent.com/78671821/145032727-3c39e31f-9776-45f4-96f4-f4c663e32620.png) I still failed. I don't know how you can do it. I used MySQL with GIT and root users, but they didn't work. 21 tables were generated, which seems wrong
GiteaMirror commented 2025-11-02 07:58:09 -06:00
Author
Owner
Copy Link

@caifenglin commented on GitHub (Dec 7, 2021):

The app.in file has content. It is indeed mounted in the / data directory, and the data also has content

@caifenglin commented on GitHub (Dec 7, 2021): The app.in file has content. It is indeed mounted in the / data directory, and the data also has content
GiteaMirror commented 2025-11-02 07:58:09 -06:00
Author
Owner
Copy Link

@caifenglin commented on GitHub (Dec 7, 2021):

Originally, I wanted to ask a question. I wanted someone to help my platform. It seems that the problem can't be solved well, so it was closed. I'm sorry I can't understand this kind of behavior of solving the problem in order to close it

@caifenglin commented on GitHub (Dec 7, 2021): Originally, I wanted to ask a question. I wanted someone to help my platform. It seems that the problem can't be solved well, so it was closed. I'm sorry I can't understand this kind of behavior of solving the problem in order to close it
GiteaMirror commented 2025-11-02 07:58:10 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Dec 7, 2021):

GitHub issues are mainly used for bug reports and feature discussions. You should have read https://github.com/go-gitea/gitea/issues/new/choose

If you have read the documents (https://docs.gitea.io/en-us/seek-help/ , https://docs.gitea.io/zh-cn/seek-help/ ), you could understand that Discord / Discourse Forum / QQ Group are the places for questions and helps.

@wxiaoguang commented on GitHub (Dec 7, 2021): GitHub issues are mainly used for bug reports and feature discussions. You should have read https://github.com/go-gitea/gitea/issues/new/choose If you have read the documents (https://docs.gitea.io/en-us/seek-help/ , https://docs.gitea.io/zh-cn/seek-help/ ), you could understand that Discord / Discourse Forum / QQ Group are the places for questions and helps.
GiteaMirror commented 2025-11-02 07:58:10 -06:00
Author
Owner
Copy Link

@caifenglin commented on GitHub (Dec 7, 2021):

I'm sorry

@caifenglin commented on GitHub (Dec 7, 2021): I'm sorry
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#8218
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?