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

Links in repo issues doesn't change automatically on web URL change. #8374

New Issue
Closed
opened 2025-11-02 08:04:08 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 08:04:08 -06:00
Owner
Copy Link

Originally created by @CkovMk on GitHub (Jan 18, 2022).

Gitea Version

1.15.9

Git Version

No response

Operating System

No response

How are you running Gitea?

Official docker image, arch=x86-64

Database

MySQL

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Description

The Gitea instance is deployed in LAN and accessed via http://ip-address:port/ .
I Changed the host ip address from 192.168.8.21 to 10.25.5.21 (for instance), but links in repo issue page still remains the old address, which is apparently inaccessible. Change the ip address manually to new one results in a success though.

One more thing, I have some of the issues added to a project. Issue links in the project seems working normally.

Screenshots

No response

Originally created by @CkovMk on GitHub (Jan 18, 2022). ### Gitea Version 1.15.9 ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? Official docker image, arch=x86-64 ### Database MySQL ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Description The Gitea instance is deployed in LAN and accessed via http://ip-address:port/ . I Changed the host ip address from 192.168.8.21 to 10.25.5.21 (for instance), but links in repo issue page still remains the old address, which is apparently inaccessible. Change the ip address manually to new one results in a success though. One more thing, I have some of the issues added to a project. Issue links in the project seems working normally. ### Screenshots _No response_
GiteaMirror added the type/question label 2025-11-02 08:04:08 -06:00
GiteaMirror commented 2025-11-02 08:04:09 -06:00
Author
Owner
Copy Link

@KN4CK3R commented on GitHub (Jan 18, 2022):

Which "links in repo issue page" exactly?

@KN4CK3R commented on GitHub (Jan 18, 2022): Which "links in repo issue page" exactly?
GiteaMirror commented 2025-11-02 08:04:09 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jan 18, 2022):

Have you changed your ROOT_URL setting?

@zeripath commented on GitHub (Jan 18, 2022): Have you changed your ROOT_URL setting?
GiteaMirror commented 2025-11-02 08:04:09 -06:00
Author
Owner
Copy Link

@CkovMk commented on GitHub (Jan 20, 2022):

An update: ROOT_URL setting has been updated and solved the problem. Thanks and sorry for the inconvenience.
ps: Need to update those values in docker ENV! urrrrrrrrrh.

@CkovMk commented on GitHub (Jan 20, 2022): An update: ROOT_URL setting has been updated and solved the problem. Thanks and sorry for the inconvenience. ps: Need to update those values in docker ENV! urrrrrrrrrh.
GiteaMirror commented 2025-11-02 08:04:09 -06:00
Author
Owner
Copy Link

@CkovMk commented on GitHub (Jan 20, 2022):

An update: ROOT_URL setting has been updated and solved the problem. Thanks and sorry for the inconvenience.
ps: Need to update those values in docker ENV! urrrrrrrrrh.

@CkovMk commented on GitHub (Jan 20, 2022): An update: ROOT_URL setting has been updated and solved the problem. Thanks and sorry for the inconvenience. ps: Need to update those values in docker ENV! urrrrrrrrrh.
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 type/question
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#8374
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?