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

Push fails with ! [remote rejected] main -> main (pre-receive hook declined) #13374

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

Originally created by @automatize1 on GitHub (Aug 7, 2024).

Description

Much like other (closed) issues pointed out, I can't seem to push a test repo (containing only one commit regarding the creation of the README file). But unlike the closed issues, I couldn't fix the problem with the suggested approaches. This is the output on the client side:

pi@raspberrypi:~/gitea/teste $ git push -u origin main
Username for 'http://192.168.0.99:3000': gabriel.monteiro
Password for 'http://gabriel.monteiro@192.168.0.99:3000':
Enumerating objects: 3, done.
Counting objects: 100% (3/3), done.
Writing objects: 100% (3/3), 217 bytes | 217.00 KiB/s, done.
Total 3 (delta 0), reused 0 (delta 0), pack-reused 0
To http://192.168.0.99:3000/gabriel.monteiro/teste.git
 ! [remote rejected] main -> main (pre-receive hook declined)
error: failed to push some refs to 'http://192.168.0.99:3000/gabriel.monteiro/teste.git'

Things I've already tried:

  1. Setting LOCAL_ROOT_URL to 127.0.0.1
  2. Deleting and recreating hooks on the repo's folder

I don't know if it helps, but here's my app.ini file:

APP_NAME = Gitea: Git with a cup of tea
RUN_USER = git
RUN_MODE = prod
WORK_PATH = /var/lib/gitea

[repository]
ROOT = /var/lib/gitea/git/repositories

[repository.local]
LOCAL_COPY_PATH = /tmp/gitea/local-repo

[repository.upload]
TEMP_PATH = /tmp/gitea/uploads

[server]
APP_DATA_PATH = /var/lib/gitea
SSH_DOMAIN = 192.168.0.99
HTTP_PORT = 3000
ROOT_URL = http://192.168.0.99:3000/
DISABLE_SSH = false
; In rootless gitea container only internal ssh server is supported
START_SSH_SERVER = true
SSH_PORT = 2222
SSH_LISTEN_PORT = 2222
BUILTIN_SSH_SERVER_USER = git
LFS_START_SERVER = true
DOMAIN = 192.168.0.99
LFS_JWT_SECRET = 18t9XG-KlFpTuTiIA_FqwLRhsOamoQYQH4vQkMB9kcU
OFFLINE_MODE = true

[database]
PATH = /var/lib/gitea/data/gitea.db
DB_TYPE = sqlite3
HOST = localhost:3306
NAME = gitea
USER = root
PASSWD = 
SCHEMA = 
SSL_MODE = disable
LOG_SQL = false

[session]
PROVIDER_CONFIG = /var/lib/gitea/data/sessions
PROVIDER = file

[picture]
AVATAR_UPLOAD_PATH = /var/lib/gitea/data/avatars
REPOSITORY_AVATAR_UPLOAD_PATH = /var/lib/gitea/data/repo-avatars

[attachment]
PATH = /var/lib/gitea/data/attachments

[log]
ROOT_PATH = /var/lib/gitea/data/log
MODE = console
LEVEL = info

[service]
DISABLE_REGISTRATION = false
REQUIRE_SIGNIN_VIEW = false
REGISTER_EMAIL_CONFIRM = false
ENABLE_NOTIFY_MAIL = false
ALLOW_ONLY_EXTERNAL_REGISTRATION = false
ENABLE_CAPTCHA = false
DEFAULT_KEEP_EMAIL_PRIVATE = false
DEFAULT_ALLOW_CREATE_ORGANIZATION = true
DEFAULT_ENABLE_TIMETRACKING = true
NO_REPLY_ADDRESS = noreply.localhost

[lfs]
PATH = /var/lib/gitea/git/lfs

[mailer]
ENABLED = false

[openid]
ENABLE_OPENID_SIGNIN = true
ENABLE_OPENID_SIGNUP = true

[cron.update_checker]
ENABLED = false

[repository.pull-request]
DEFAULT_MERGE_STYLE = merge

[repository.signing]
DEFAULT_TRUST_MODEL = committer

UPDATE It seems to be an issue with cifs. When I host the volumes locally on the raspberrypi, it works

Gitea Version

1.22.1

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

https://gist.github.com/automatize1/637a4b3f2df2c15fc9ae848a75a6cc54

Screenshots

No response

Git Version

2.39.2

Operating System

RaspberryPi OS 64

How are you running Gitea?

I'm running gitea from Docker. I guess the only uncommon configuration is that the my container volumes are hosted on another machine and accessed with cifs.

Database

SQLite

Originally created by @automatize1 on GitHub (Aug 7, 2024). ### Description Much like other (closed) issues pointed out, I can't seem to push a test repo (containing only one commit regarding the creation of the README file). But unlike the closed issues, I couldn't fix the problem with the suggested approaches. This is the output on the client side: ``` pi@raspberrypi:~/gitea/teste $ git push -u origin main Username for 'http://192.168.0.99:3000': gabriel.monteiro Password for 'http://gabriel.monteiro@192.168.0.99:3000': Enumerating objects: 3, done. Counting objects: 100% (3/3), done. Writing objects: 100% (3/3), 217 bytes | 217.00 KiB/s, done. Total 3 (delta 0), reused 0 (delta 0), pack-reused 0 To http://192.168.0.99:3000/gabriel.monteiro/teste.git ! [remote rejected] main -> main (pre-receive hook declined) error: failed to push some refs to 'http://192.168.0.99:3000/gabriel.monteiro/teste.git' ``` Things I've already tried: 1. Setting `LOCAL_ROOT_URL` to 127.0.0.1 2. Deleting and recreating hooks on the repo's folder I don't know if it helps, but here's my app.ini file: ``` APP_NAME = Gitea: Git with a cup of tea RUN_USER = git RUN_MODE = prod WORK_PATH = /var/lib/gitea [repository] ROOT = /var/lib/gitea/git/repositories [repository.local] LOCAL_COPY_PATH = /tmp/gitea/local-repo [repository.upload] TEMP_PATH = /tmp/gitea/uploads [server] APP_DATA_PATH = /var/lib/gitea SSH_DOMAIN = 192.168.0.99 HTTP_PORT = 3000 ROOT_URL = http://192.168.0.99:3000/ DISABLE_SSH = false ; In rootless gitea container only internal ssh server is supported START_SSH_SERVER = true SSH_PORT = 2222 SSH_LISTEN_PORT = 2222 BUILTIN_SSH_SERVER_USER = git LFS_START_SERVER = true DOMAIN = 192.168.0.99 LFS_JWT_SECRET = 18t9XG-KlFpTuTiIA_FqwLRhsOamoQYQH4vQkMB9kcU OFFLINE_MODE = true [database] PATH = /var/lib/gitea/data/gitea.db DB_TYPE = sqlite3 HOST = localhost:3306 NAME = gitea USER = root PASSWD = SCHEMA = SSL_MODE = disable LOG_SQL = false [session] PROVIDER_CONFIG = /var/lib/gitea/data/sessions PROVIDER = file [picture] AVATAR_UPLOAD_PATH = /var/lib/gitea/data/avatars REPOSITORY_AVATAR_UPLOAD_PATH = /var/lib/gitea/data/repo-avatars [attachment] PATH = /var/lib/gitea/data/attachments [log] ROOT_PATH = /var/lib/gitea/data/log MODE = console LEVEL = info [service] DISABLE_REGISTRATION = false REQUIRE_SIGNIN_VIEW = false REGISTER_EMAIL_CONFIRM = false ENABLE_NOTIFY_MAIL = false ALLOW_ONLY_EXTERNAL_REGISTRATION = false ENABLE_CAPTCHA = false DEFAULT_KEEP_EMAIL_PRIVATE = false DEFAULT_ALLOW_CREATE_ORGANIZATION = true DEFAULT_ENABLE_TIMETRACKING = true NO_REPLY_ADDRESS = noreply.localhost [lfs] PATH = /var/lib/gitea/git/lfs [mailer] ENABLED = false [openid] ENABLE_OPENID_SIGNIN = true ENABLE_OPENID_SIGNUP = true [cron.update_checker] ENABLED = false [repository.pull-request] DEFAULT_MERGE_STYLE = merge [repository.signing] DEFAULT_TRUST_MODEL = committer ``` **UPDATE** It seems to be an issue with cifs. When I host the volumes locally on the raspberrypi, it works ### Gitea Version 1.22.1 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist https://gist.github.com/automatize1/637a4b3f2df2c15fc9ae848a75a6cc54 ### Screenshots _No response_ ### Git Version 2.39.2 ### Operating System RaspberryPi OS 64 ### How are you running Gitea? I'm running gitea from Docker. I guess the only uncommon configuration is that the my container volumes are hosted on another machine and accessed with cifs. ### Database SQLite
GiteaMirror added the type/bugissue/needs-feedback labels 2025-11-02 10:40:21 -06:00
GiteaMirror commented 2025-11-02 10:40:23 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Aug 7, 2024):

Yes, cifs is tricky as sometimes pushes can fail due to disruption on the link and the hooks not executing, as well some OSes mount cifs as noexec.

@techknowlogick commented on GitHub (Aug 7, 2024): Yes, cifs is tricky as sometimes pushes can fail due to disruption on the link and the hooks not executing, as well some OSes mount cifs as noexec.
GiteaMirror commented 2025-11-02 10:40:24 -06:00
Author
Owner
Copy Link

@GiteaBot commented on GitHub (Sep 17, 2024):

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

@GiteaBot commented on GitHub (Sep 17, 2024): We close issues that need feedback from the author if there were no new comments for a month. :tea:
GiteaMirror commented 2025-11-02 10:40:24 -06:00
Author
Owner
Copy Link

@pragathiacharya commented on GitHub (Sep 20, 2024):

Facing the same issue for me, while pushing the merge request. Any suggession or solution?

@pragathiacharya commented on GitHub (Sep 20, 2024): Facing the same issue for me, while pushing the merge request. Any suggession or solution?
GiteaMirror commented 2025-11-02 10:40:24 -06:00
Author
Owner
Copy Link

@automatize1 commented on GitHub (Sep 20, 2024):

Facing the same issue for me, while pushing the merge request. Any suggession or solution?

My issue was completely related to the cifs, I don't know if that's your case. My solution was to configure the cifs on the docker-compose.yml file, like so:

volumes:
  gitea-data:
    driver: local
    driver_opts:
      type: cifs
      o: username=${CIFS_USERNAME},password=${CIFS_PASSWORD},domain=${CIFS_DOMAIN},nobrl,vers=2.0,uid=1000,gid=1000,file_mode=0770,dir_mode=0770
      device: "${CIFS_DEVICE}/gitea/data"
  gitea-config:
    driver: local
    driver_opts:
      type: cifs
      o: username=${CIFS_USERNAME},password=${CIFS_PASSWORD},domain=${CIFS_DOMAIN},vers=2.0,uid=1000,gid=1000,file_mode=0770,dir_mode=0770
      device: "${CIFS_DEVICE}/gitea/config"
@automatize1 commented on GitHub (Sep 20, 2024): > Facing the same issue for me, while pushing the merge request. Any suggession or solution? My issue was completely related to the cifs, I don't know if that's your case. My solution was to configure the cifs on the `docker-compose.yml` file, like so: ``` volumes: gitea-data: driver: local driver_opts: type: cifs o: username=${CIFS_USERNAME},password=${CIFS_PASSWORD},domain=${CIFS_DOMAIN},nobrl,vers=2.0,uid=1000,gid=1000,file_mode=0770,dir_mode=0770 device: "${CIFS_DEVICE}/gitea/data" gitea-config: driver: local driver_opts: type: cifs o: username=${CIFS_USERNAME},password=${CIFS_PASSWORD},domain=${CIFS_DOMAIN},vers=2.0,uid=1000,gid=1000,file_mode=0770,dir_mode=0770 device: "${CIFS_DEVICE}/gitea/config" ```
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 type/bug
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#13374
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?