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

Issues with ROOT_URL and Gitea base URL not updating in Synology Docker instance #10870

New Issue
Closed
opened 2025-11-02 09:20:45 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-02 09:20:45 -06:00
Owner
Copy Link

Originally created by @tfraley on GitHub (May 18, 2023).

Description

Good day,

I have a Docker instance running Gitea on a Synology device. I am encountering an issue where the ROOT_URL specified in app.ini is different from the URL being accessed, resulting in potential web functionality issues. Although the error message suggests editing app.ini, I am modifying var/packages/gitea/var/conf.ini instead. I am unsure if these files are equivalent. Additionally, the updated Gitea base URL is not reflected on the admin/config page, despite changes being visible in the conf.ini file. Is this a caching issue or a bug?

Gitea Version

1.17.3

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

CleanShot 2023-05-18 at 11 27 48@2x
CleanShot 2023-05-18 at 10 02 40@2x

Git Version

No response

Operating System

No response

How are you running Gitea?

Docker on synology

Database

None

Originally created by @tfraley on GitHub (May 18, 2023). ### Description Good day, I have a Docker instance running Gitea on a Synology device. I am encountering an issue where the ROOT_URL specified in app.ini is different from the URL being accessed, resulting in potential web functionality issues. Although the error message suggests editing app.ini, I am modifying var/packages/gitea/var/conf.ini instead. I am unsure if these files are equivalent. Additionally, the updated Gitea base URL is not reflected on the admin/config page, despite changes being visible in the conf.ini file. Is this a caching issue or a bug? ### Gitea Version 1.17.3 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots ![CleanShot 2023-05-18 at 11 27 48@2x](https://github.com/go-gitea/gitea/assets/1166064/f216c767-b61b-4ad4-bfa6-70b13e7ada12) ![CleanShot 2023-05-18 at 10 02 40@2x](https://github.com/go-gitea/gitea/assets/1166064/92365e51-a3e5-498e-a19a-778f177a9cd8) ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? Docker on synology ### Database None
GiteaMirror added the issue/needs-feedback label 2025-11-02 09:20:45 -06:00
GiteaMirror commented 2025-11-02 09:20:46 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (May 19, 2023):

I think maybe you missed the s? It's https://xxx not http://xxx.

@lunny commented on GitHub (May 19, 2023): I think maybe you missed the `s`? It's `https://xxx` not `http://xxx`.
GiteaMirror commented 2025-11-02 09:20:46 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (May 19, 2023):

Have you restarted the service after updating the config?

@techknowlogick commented on GitHub (May 19, 2023): Have you restarted the service after updating the config?
GiteaMirror commented 2025-11-02 09:20:46 -06:00
Author
Owner
Copy Link

@tfraley commented on GitHub (May 19, 2023):

I think maybe you missed the s? It's https://xxx not http://xxx.

I added the S but didn't take

@tfraley commented on GitHub (May 19, 2023): > I think maybe you missed the `s`? It's `https://xxx` not `http://xxx`. I added the S but didn't take
GiteaMirror commented 2025-11-02 09:20:46 -06:00
Author
Owner
Copy Link

@tfraley commented on GitHub (May 19, 2023):

Have you restarted the service after updating the config?

I stoped and started both containers and restarted docker it self

@tfraley commented on GitHub (May 19, 2023): > Have you restarted the service after updating the config? I stoped and started both containers and restarted docker it self
GiteaMirror commented 2025-11-02 09:20:46 -06:00
Author
Owner
Copy Link

@yp05327 commented on GitHub (May 22, 2023):

Did you set the environment variable GITEA__server__ROOT_URL?

@yp05327 commented on GitHub (May 22, 2023): Did you set the environment variable `GITEA__server__ROOT_URL`?
GiteaMirror commented 2025-11-02 09:20:47 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (May 22, 2023):

You can try to set APP_NAME in your config file (shown as the Site Title in the config page) to other values to see whether you are editing the correct config file.

In history, almost all similar issues are caused by the user edited wrong config file.

@wxiaoguang commented on GitHub (May 22, 2023): You can try to set `APP_NAME` in your config file (shown as the Site Title in the config page) to other values to see whether you are editing the correct config file. In history, almost all similar issues are caused by the user edited wrong config file.
GiteaMirror commented 2025-11-02 09:20:47 -06:00
Author
Owner
Copy Link

@tfraley commented on GitHub (May 22, 2023):

Figured it out.. Feel free to close thank you

@tfraley commented on GitHub (May 22, 2023): Figured it out.. Feel free to close thank you
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 issue/needs-feedback
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#10870
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?