You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, I try to push my code to repo but it says pre-receive hook declined. Currently, I'm using Ingres, but I also try with node port ( I also tried simple docker installation of gitea but the error persists). It always comes with this error. I found that some people face this same problem with gitea, they say go to site administration and click on Resynchronize pre-receive, update and post-receive hooks of all repositories will solve the issue but no success in my case.
→ git push origin master
Enumerating objects: 4, done.
Counting objects: 100% (4/4), done.
Delta compression using up to 6 threads
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 364 bytes | 364.00 KiB/s, done.
Total 3 (delta 0), reused 0 (delta 0), pack-reused 0
remote: Gitea: Internal Server Error
remote: Unable to contact gitea: Post http://0.0.0.0:31867/api/internal/hook/pre-receive/hacstac/Test--Repo: dial tcp 0.0.0.0:31867: connect: connection refused
To http://gitea.skynet.local/hacstac/Test--Repo.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'http://gitea.skynet.local/hacstac/Test--Repo.git'
can you please help me? how should I resolve this issue??
The text was updated successfully, but these errors were encountered:
Hey, I try to push my code to repo but it says pre-receive hook declined. Currently, I'm using Ingres, but I also try with node port ( I also tried simple docker installation of gitea but the error persists). It always comes with this error. I found that some people face this same problem with gitea, they say go to site administration and click on
Resynchronize pre-receive, update and post-receive hooks of all repositories
will solve the issue but no success in my case.can you please help me? how should I resolve this issue??
The text was updated successfully, but these errors were encountered: