Gitlab Failed to get username: Internal API unreachable - gitlab

for long time i have a private gitlab.
But now i transfert my gitlab to a domain name with ssl certificate.
Since i make this, i have this error when i tried to clone a repository.
I make some checks, I'm correctly logged
debug1: Authentication succeeded (publickey).
But I get a
remote:
remote: ========================================================================
remote:
remote: Failed to get username: Internal API unreachable
remote:
remote: ========================================================================
remote:
Can someone help me to understand what is it ? and why i have this error.
Thanks, have a nice day.

Related

"Error decoding the received TLS packet" when cloning into git repository

I am experiencing an error when trying to clone into the https://github.com/zulip/zulip.git repository.
As far as I have looked this question has not been answered yet.
-I have tried raising the http/https buffer without success using:
git config --global http.postBuffer 524288000
git config --global https.postBuffer 524288000
-The error always occurs #53% arround 100MiB in.
Cloning into 'zulip'...
remote: Enumerating objects: 342136, done.
remote: Counting objects: 100% (1589/1589), done.
remote: Compressing objects: 100% (719/719), done.
error: RPC failed; curl 56 GnuTLS recv error (-9): Error decoding the received TLS packet.
fatal: the remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
EDIT:
I have done a bit testing and I seem to be getting this error whenever I try to clone a very large repository.
-I tried cloning the https://github.com/dagster-io/dagster repository and got the same error;
-Then I tried with an old and very small repository of mine (https://github.com/LFBianchi/RPyNCalc) and it works like a charm;
-Just to be sure I forked the github.com/zulip/zulip.git and tried cloning it from my version and got the same exact error.
This was solved by switching to SSH instead of HTTPS.

Deployment on heroku failed

I want to deploy my exiting project on heroku, but it gives me an error.
structure of my file:
___instagram
__backend
_controllers
_images
_middleware
_models
_node_modules
_routes
_utiles
.gitignore
app.js
package-lock.json
package.json
Procfile
__ui
...
commands:
E:\Coding\projects\instagram>git add .
E:\Coding\projects\instagram>git commit -m "update controllers"
[master 086d891] update controllers
1 file changed, 1 insertion(+), 1 deletion(-)
E:\Coding\projects\instagram>cd backend
E:\Coding\projects\instagram\backend>git push -f heroku master
after the last command (git push -f heroku master) i got this error:
E:\Coding\projects\instagram\backend>git push -f heroku master
Enumerating objects: 16, done.
Counting objects: 100% (16/16), done.
Delta compression using up to 4 threads
Compressing objects: 100% (9/9), done.
Writing objects: 100% (10/10), 956 bytes | 956.00 KiB/s, done.
Total 10 (delta 4), reused 0 (delta 0), pack-reused 0
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Building on the Heroku-20 stack
remote: -----> Using buildpack: heroku/nodejs
remote: -----> App not compatible with buildpack: https://buildpack-registry.s3.amazonaws.com/buildpacks/heroku/nodejs.tgz
remote:
remote: ! ERROR: Application not supported by 'heroku/nodejs' buildpack
remote: !
remote: ! The 'heroku/nodejs' buildpack is set on this application, but was
remote: ! unable to detect a Node.js codebase.
remote: ! A Node.js app on Heroku requires a 'package.json' at the root of
remote: ! the directory structure.
remote: !
remote: ! If you are trying to deploy a Node.js application, ensure that this
remote: ! file is present at the top level directory. This directory has the
remote: ! following files:
remote: !
remote: ! backend/
remote: ! ui/
remote: !
remote: ! If you are trying to deploy an application written in another
remote: ! language, you need to change the list of buildpacks set on your
remote: ! Heroku app using the 'heroku buildpacks' command.
remote: !
remote: ! For more information, refer to the following documentation:
remote: ! https://devcenter.heroku.com/articles/buildpacks
remote: ! https://devcenter.heroku.com/articles/nodejs-support#activation
remote:
remote:
remote: More info: https://devcenter.heroku.com/articles/buildpacks#detection-failure
remote:
remote: ! Push failed
remote: Verifying deploy...
remote:
remote: ! Push rejected to ins-app-clone.
remote:
To https://git.heroku.com/ins-app-clone.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com/ins-app-clone.git'
Heroku buildpack looks at the top-level (root) for package.json.
The solution here is to use git sub-trees. I too was facing this issue where I had a Monorepo MERN codebase in which I wanted to deploy my server using Heroku and client via Vercel.
I have written a blog post regarding this, I'm sure you'll get an idea regarding a solution to this.
Link to Blog Post

git clone deletes everything in my project

I am facing an issue with git.
I was cloning my git repo with git clone
However, i get this error message.
and the project folder is empty.
When i search about this issue online, people suggested git reset
but i got an error saying
error: invalid path 'nodejs/blog_mvc/public /style.css'
fatal: make_cache_entry failed for path 'nodejs/blog_mvc/public /style.css'
I am not getting what this error message is telling me to do.
Cloning into 'WebApps'...
remote: Enumerating objects: 488, done.
remote: Counting objects: 100% (488/488), done.
remote: Compressing objects: 100% (272/272), done.
remote: Total 5294 (delta 201), reused 426 (delta 142), pack-reused 4806
Receiving objects: 100% (5294/5294), 10.40 MiB | 2.91 MiB/s, done.
Resolving deltas: 100% (1361/1361), done.
error: invalid path 'nodejs/blog_mvc/public /style.css'
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'
and as it suggested, i did git restore --source=HEAD :/
and i got this error.
error: invalid path 'nodejs/blog_mvc/public /style.css'
when i checked git status, everything in the project was deleted.
But on my github account, everything is still there as usual.
Can someone tell me what is going on?
I am not sure if the best solution is rollback to the previous commit and start from there or if i could figure out in a better way, please let me know. that would help me.
Thank you in advance.

Running Python Worker on Heroku - Push Failed

my scope is to run a python script (it does scrap text from websites and save it in csv files) in the cloud through cron job.
For this I chose Heroku.
I am stuck because when I try to deploy the worker I get a Push rejection.
Here is what i do:
I put my scrapit.py and Procfile ('worker: node scrapit.py') in a directory.
Then after I create an app in heroku, I send the following commands from the directory of above:
$ heroku login
$ git init
$ heroku git:remote -a app-name-on-heroku
$ git add .
$ git commit -am "nth time :("
$ git push heroku master
I get the following message:
Counting objects: 41, done. Delta compression using up to 4 threads.
Compressing objects: 100% (36/36), done. Writing objects: 100%
(41/41), 12.97 KiB | 0 bytes/s, done. Total 41 (delta 6), reused 0
(delta 0) remote: Compressing source files... done. remote: Building
source: remote: remote: -----> App not compatible with buildpack:
https://codon-buildpacks.s3.amazonaws.com/buildpacks/heroku/python.tgz
remote: More info:
https://devcenter.heroku.com/articles/buildpacks#detection-failure
remote: remote: ! Push failed remote: Verifying deploy...
remote: remote: ! Push rejected to app-name-on-heroku. remote: To
https://git.heroku.com/app-name-on-heroku.git ! [remote rejected]
master -> master (pre-receive hook declined) error: failed to push
some refs to 'https://git.heroku.com/app-name-on-heroku.git'
after the error I sent this command:
heroku buildpacks:set heroku/python
but still the push gets rejected
Every Heroku buildpack specifies a bin/detect file, which lets the platform know if that buildpack can be used with that app or not.
The python buildpack requires either: requirements.txt, setup.py or Pipfile to be present.
You need to create (and properly configure) one of those files to be able to have your python app built.

OpenShift/nodejs: Failed to execute: 'control start'

After I do git push I receive the following error:
remote: Activation failed for the following gears:
remote: 57af58352d52718047000135 (Error activating gear: CLIENT_ERROR: Failed to execute: 'control start' for /var/lib/openshift/57af58352d52718047000135/nodejs
remote: #<IO:0x00000001e5a2d0>
remote: #<IO:0x00000001e5a258>
The previous responses to this question all say to try again, but that's not working so maybe it's something I'm doing? I'm not even sure where to start to fix this.

Resources