-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[remote rejected] main -> main (pre-receive hook declined) #21528
Comments
You can enable RUN_MODE as dev and try again to take a look at what's the error. |
Output with RUN_MODE set to dev git push origin main
Enumerating objects: 3, done.
Counting objects: 100% (3/3), done.
Writing objects: 100% (3/3), 209 bytes | 209.00 KiB/s, done.
Total 3 (delta 0), reused 3 (delta 0), pack-reused 0
remote:
remote: Gitea: Internal Server Error
remote: Unable to contact gitea: Post "http://localhost:3000/api/internal/hook/pre-receive/user/test": dial tcp: lookup localhost on 1.1.1.1:53: no such host
To http://192.168.1.99:3000/user/test.git
! [remote rejected] main -> main (pre-receive hook declined)
error: failed to push some refs to 'http://192.168.1.99:3000/user/test.git' |
Ahh I see, looks like a post request is made with localost in the URL, that should be the IP address, not sure how to fix though. |
Because the host don't know what |
I added this line to /etc/hosts
Works like a charm now, thank you so much @lunny |
on windows platform, it has the same error :Gitea: Internal Server Error I've modified C:\Windows\System32\drivers\etc\hosts, and added |
It's a domain problem. |
I have the same problem. How can I solve it? |
I solved this problem: I will LOCAL_ ROOT_ The URL is changed to be the same as ROOT_ URL consistency. |
I have the same problem. what is "LOCAL_ ROOT_ "? I can not find a LOCAL_ in my app.ini.
|
https://github.com/go-gitea/gitea/blob/main/custom/conf/app.example.ini |
THOSE EXPERIENCING THIS ON WINDOWS IN 1.18 - YOU ARE EXPERIENCING A DUPLICATE OF #22370Please see #22370 (comment) DESCRIPTIONThis bug is due to a change in Go's handling of the We were bitten by this because we build our static precompiled binaries with #22467 and #22468 should fix this for 1.18.1 and 1.19-dev. WORKAROUNDFor 1.18.0 set the Builds of what will become 1.18.1 are available now on https://dl.gitea.io/gitea/1.18 |
In our case, bringing our server from gitea-1.16.9-linux-amd64 to gitea-1.17.4-linux-amd64, we needed to remove that parameter:
Maybe is not just a windows problem? @zeripath |
@gilbertoca on 1.18 this bug was one of a cluster of issues opened due to a change in the way Golang handles the build tag Whatever issue you were experiencing is different and if you're still experiencing you should consider opening a separate bug report with complete information about what your experience is. However, 1.17 is now out of support so you would need to show that your problem existed on 1.18 too. On 1.17 as was originally experienced this was due to missing alias for 127.0.0.1 in /etc/hosts. The other thing to note - is that your problem was solved by doing the opposite to how this bug was worked around for others. That your solution requires the opposite says that the problem is likely a different thing. In any case I'm going to lock this conversation - this bug is resolved and was a duplicate of #22730 |
Description
Git push always fails with error:
Gitea Version
Gitea version 1.17.3+4-g19df07f02 built with GNU Make 4.1, go1.18.7 : bindata, sqlite, sqlite_unlock_notify
Git Version
2.37.3
Operating System
Arch Linux
How are you running Gitea?
Binary download, fresh install, no containers.
Database
SQLite
The text was updated successfully, but these errors were encountered: