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

Repository default hook pre-receive.bak not able to resolve localhost #13124

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

Originally created by @Linkyrex on GitHub (Jun 10, 2024).

Description

Having set LOCAL_ROOT_URL = http://localhost:3000/ in the app.ini will result in the error: "The change was rejected by the server. Please check Git Hooks. Full Rejection Message: Gitea: Internal Server Connection Error" when pushing to a repository. According to the logs the hook pre-receive.bak was declined.
remote: Gitea: Internal Server Connection Error To /var/lib/gitea/data/gitea-repositories/org/myrepo.git ! [remote rejected] aae73a9fef44476b0666fff9f238472213057df7 -> main (pre-receive hook declined) error: failed to push some refs to '/var/lib/gitea/data/gitea-repositories/org/myrepo'

This Issue went away after setting: LOCAL_ROOT_URL = http://127.0.0.1:3000/

Gitea Version

1.22.0

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

CentOS9

How are you running Gitea?

Build from Source and as a service.

Database

PostgreSQL

Originally created by @Linkyrex on GitHub (Jun 10, 2024). ### Description Having set `LOCAL_ROOT_URL = http://localhost:3000/` in the app.ini will result in the error: "The change was rejected by the server. Please check Git Hooks. Full Rejection Message: Gitea: Internal Server Connection Error" when pushing to a repository. According to the logs the hook pre-receive.bak was declined. `remote: Gitea: Internal Server Connection Error To /var/lib/gitea/data/gitea-repositories/org/myrepo.git ! [remote rejected] aae73a9fef44476b0666fff9f238472213057df7 -> main (pre-receive hook declined) error: failed to push some refs to '/var/lib/gitea/data/gitea-repositories/org/myrepo'` This Issue went away after setting: `LOCAL_ROOT_URL = http://127.0.0.1:3000/` ### Gitea Version 1.22.0 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System CentOS9 ### How are you running Gitea? Build from Source and as a service. ### Database PostgreSQL
GiteaMirror added the issue/needs-feedback label 2025-11-02 10:31:49 -06:00
GiteaMirror commented 2025-11-02 10:31:50 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jun 10, 2024):

Please test you can visit localhost from the shell of git.

@lunny commented on GitHub (Jun 10, 2024): Please test you can visit `localhost` from the shell of git.
GiteaMirror commented 2025-11-02 10:31:51 -06:00
Author
Owner
Copy Link

@Linkyrex commented on GitHub (Jun 10, 2024):

localhost itself resolved fine. Other aspects of Gitea were also working as expected. The issue seemed to be unique for the hook pre-receive.bak.

@Linkyrex commented on GitHub (Jun 10, 2024): localhost itself resolved fine. Other aspects of Gitea were also working as expected. The issue seemed to be unique for the hook pre-receive.bak.
GiteaMirror commented 2025-11-02 10:31:51 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Jun 10, 2024):

The .bak is suspicious as by default hooks don't have that as an extension. I'm wondering if maybe someone edited a hook and made a backup and now it is still being run. Could you try removing that file from the hooks directory for that repo?

@techknowlogick commented on GitHub (Jun 10, 2024): The .bak is suspicious as by default hooks don't have that as an extension. I'm wondering if maybe someone edited a hook and made a backup and now it is still being run. Could you try removing that file from the hooks directory for that repo?
GiteaMirror commented 2025-11-02 10:31:51 -06:00
Author
Owner
Copy Link

@GiteaBot commented on GitHub (Jul 11, 2024):

We close issues that need feedback from the author if there were no new comments for a month. 🍵

@GiteaBot commented on GitHub (Jul 11, 2024): We close issues that need feedback from the author if there were no new comments for a month. :tea:
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#13124
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?