Home → Support →

Issue with GITBASH PUSH - error: RPC failed; HTTP 404 curl 22 The requested URL returned error: 404 Not Found

• Edit

plumma

13 Mar, 2017 06:26 PM

For some unknown reason I am not unable to push my website to the server anymore, this was working fine then stopped working.

Matt@PC MINGW64 ~/Documents/DEV Projects/IT Assets DB/ITAssetsDatabase (master)
$ git push itservice master
Counting objects: 3844, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (3700/3700), done.
Writing objects: 100% (3844/3844), 120.25 MiB | 8.09 MiB/s, done.
Total 3844 (delta 421), reused 0 (delta 0)
error: RPC failed; HTTP 404 curl 22 The requested URL returned
error: 404 Not Found
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date

To troubleshoot I deleted the application from the Appharbor server and removed the .git directory from the local application folder.

I then went about recreating the local repository and recreating the application, I then pushed it to appharbor again and same issue.

I created another local project called blog as a test and this pushed OK so permissions seem ok, I'm running this from home and using GITBASH.

I've googled this all day but no joy, I also tried:-

git config --global http.postBuffer 1048576000

This made no difference and just seemed to make it hang at this line for a long time before the error comes up.
Total 3844 (delta 421), reused 0 (delta 0)

Although the problems seemed to start happening when I was testing out Sourcetree and Sourcetree came up with a similar error, also I think there were from SSH errors coming up but I can't remember the exact wording,

Can someone explain, if I remove the local repository and the application from AH, then there must be another file location affecting what's happening here, any ideas?

Thanks,

1. Support Staff 1 Posted by rune on 13 Mar, 2017 08:06 PM

   

   Hi,

   It looks like a type of error that can be returned when making a single large push of a repository. You may be able to push the repository gradually (e.g. push earlier revisions step by step), but for repositories of this size I'd recommend integrating with a third party repository host using for instance our Bitbucket or GitHub integrations -- they accept very large repositories, and can easily be integrated with your AppHarbor apps.

   In some cases repositories grow large over time if binaries are checked in and committed, or if large static files are included in the repository. In the first case I'd recommend resetting the repository to exclude these files, and add binaries to your .gitignore files so they're not committed, as this will reduce the footprint of the repository. In the latter case it's often more desirable to remove large static files (such as images, movies etc) from the repository, and instead host them at a third party cloud storage service such as Amazon S3 -- this can also help serving the files as such services are designed serving large objects in a cloud-scalable environment, and reduce the logic required for that in your AppHarbor applications.

   Have you considered these alternatives yet? Feel free to let share more information about the contents of your repository if these don't address your use case and I'll be happy to provide more tailored advice for your use case.

   Best,
   Rune

   • Edit

2. 2 Posted by plumma on 14 Mar, 2017 04:38 PM

   

   Hi Rune,

   Excellent stuff, I switched to GitHub and it's all working like a dream now.

   Perhaps you might like to mention the repository size issue in the getting started guide, as it might save another unsuspecting character a lot of time.

   Again, much appreciated.

   Matt.

   • Edit

3. Support Staff 3 Posted by rune on 15 Mar, 2017 12:39 AM

   

   Hi Matt,

   Yep that's a good idea - a hard limit isn't currently enforced as many repositories hosted on the platform have repositories larger than the limit for individual pushes. Will make sure to make a note on this.

   Good to hear the GitHub integration helped address the issue though, and thanks for the heads up. Let me know if there's anything else I can help with!

   Best,
   Rune

   • Edit