MDB Pro CLI Install login loop

Topic: MDB Pro CLI Install login loop

MonizDave pro premium priority asked a year ago

Expected behavior

I run the cmd from the instructions (with my token):npm install git+

And it installs.

Actual behavior

I run the cmd from the instructions (with my token):npm install git+

I get prompted for my username and password, which I provide and it asks again repeatedly on a seemingly infinite loop.

Resources (screenshots, code snippets etc.)

Below is the log - I replaced my access token with ACCESS_TOKEN

0 verbose cli [

0 verbose cli '/usr/bin/node',

0 verbose cli '/usr/bin/npm',

0 verbose cli 'i',

0 verbose cli 'git+'

0 verbose cli ]

1 info using npm@7.14.0

2 info using node@v16.2.0

3 timing npm:load:whichnode Completed in 0ms

4 timing config:load:defaults Completed in 1ms

5 timing config:load:file:/usr/lib/node_modules/npm/npmrc Completed in 0ms

6 timing config:load:builtin Completed in 0ms

7 timing config:load:cli Completed in 1ms

8 timing config:load:env Completed in 0ms

9 timing config:load:file:/home/dave/Development/Workspace/mdbpro/angular-src/.npmrc Completed in 0ms

10 timing config:load:project Completed in 0ms

11 timing config:load:file:/home/dave/.npmrc Completed in 0ms

12 timing config:load:user Completed in 0ms

13 timing config:load:file:/usr/etc/npmrc Completed in 0ms

14 timing config:load:global Completed in 0ms

15 timing config:load:validate Completed in 0ms

16 timing config:load:credentials Completed in 1ms

17 timing config:load:setEnvs Completed in 0ms

18 timing config:load Completed in 3ms

19 timing npm:load:configload Completed in 3ms

20 timing npm:load:setTitle Completed in 0ms

21 timing npm:load:setupLog Completed in 1ms

22 timing npm:load:cleanupLog Completed in 1ms

23 timing npm:load:configScope Completed in 0ms

24 timing npm:load:projectScope Completed in 0ms

25 timing npm:load Completed in 5ms

26 timing config:load:flatten Completed in 1ms

27 timing arborist:ctor Completed in 0ms

28 verbose shrinkwrap failed to load node_modules/.package-lock.json out of date, updated: node_modules

29 timing idealTree:init Completed in 341ms

30 timing idealTree Completed in 1321ms

31 timing command:install Completed in 1323ms

32 verbose stack Error: command failed

32 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/index.js:64:27)

32 verbose stack at ChildProcess.emit (node:events:365:28)

32 verbose stack at maybeClose (node:internal/child_process:1067:16)

32 verbose stack at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)

33 verbose cwd /home/dave/Development/Workspace/mdbpro/angular-src

34 verbose Linux 5.12.5-arch1-1

35 verbose argv "/usr/bin/node" "/usr/bin/npm" "i" "git+"

36 verbose node v16.2.0

37 verbose npm v7.14.0

38 error code 128

39 error command failed

40 error command git --no-replace-objects ls-remote

41 error remote: HTTP Basic: Access denied

41 error fatal: Authentication failed for ''

42 verbose exit 128

MonizDave pro premium priority commented a year ago

Interesting! So I just tried again and I noticed this new aspect... if I purposefully enter incorrect credentials it denies me immediately and errors out. However if I enter the correct credentials it processes a little bit and asks again, this process repeats about 5 times but it eventually errors out again right before it finishes

Arkadiusz Idzikowski staff commented 12 months ago

@MonizDave Please take a look at this thread:

If you have a similar problem, please try to update Git to the latest version.

MonizDave pro premium priority commented 12 months ago

My problem sounds similar, however it's worth noting they used Windows and I'm not. However I did create the token correctly using your video and I'm on git --version 2.31.1.

Issue persists.

MonizDave pro premium priority commented 12 months ago

I've been running this inside VSCode, when I run it directly in Konsole (default console for KDE) I receive code 128 immediately (remote: HTTP Basic: Access denied).

I can provide a log if you want.

Arkadiusz Idzikowski staff commented 12 months ago

We checked your access to the package and it looks like everything is working correctly. Please add the log to your first post, maybe the additional information will help us to resolve this problem.

I removed the attached screenshot because it contained information about your private token.

MonizDave pro premium priority commented 12 months ago

My apologies I scratched it out in one place, didn't notice the others.

I have attached the log.

MonizDave pro premium priority commented 12 months ago

I work for YRDSB and they just got a team licence. I installed it on one of their Windows machines with their token with no problem. The entire process was the same. I suspect something to do with the Linux side of things is what is making this an issue.

MonizDave pro premium priority commented 12 months ago

Someone just changed/reset my password for - please confirm this was you

MonizDave pro premium priority commented 12 months ago

I was able to complete the installation with this account on a windows machine. Something is wrong with the way the credentials are managed (either within VSCode or git) on Linux.

You can stop looking into this now I guess, it'll just be a problem I'll have to route out on my own.

Arkadiusz Idzikowski staff commented 12 months ago

@MonizDave The password has been reset by our team, we wanted to make sure that the access to the repository was granted correctly.

We will be happy to help with this problem, but we could not reproduce it on our end (I double-checked that using Linux and built-in/VSCode terminal).

MonizDave pro premium priority commented 12 months ago

What distro and what DE did you use?

MonizDave pro premium priority answered 12 months ago

In most cases the details in this thread should help you:

However in my case being on a custom install of Arch Linux (with KDE) I didn't account for lack of gnome-keyring that I'm used to - and kwallet wasn't living up to all I wanted it to.

Anyways following these steps below (plus a reboot before trying again for good measure). You should be able to enter the credentials just once and everything will resolve itself correctly.

$ sudo pacman -S gnome-keyring libgnome-keyring
$ cd /usr/share/git/credential/gnome-keyring
$ make
$ git config --global credential.helper /usr/share/git/credential/gnome-keyring/git-credential-gnome-keyring

Arkadiusz Idzikowski staff commented 12 months ago

@MonizDave Did you manage to install our library without any problems after these changes?

MonizDave pro premium priority commented 12 months ago

@Arkadiusz Idzikowski Yes! Finally! That is why I chose to post that information as an "answer" and not a "comment". Thank you for your time and patience. But do remember this thread for the next member using KDE Plasma (and/or with Arch Linux) as by default there is insufficient management of Git Credentials

Dave Moniz pro premium priority answered 11 months ago

Had to do a full wipe of my machine and the solution I found worked perfectly after a fresh install.

Closing this now.


Hire our experts to build a dedicated project. We'll analyze your business requirements, for free.



Specification of the issue
  • User: Pro
  • Premium support: Yes
  • Technology: MDB Angular
  • MDB Version: MDB5 1.0.0-beta3
  • Device: PC
  • Browser: N/A
  • OS: Arch Linux
  • Provided sample code: No
  • Provided link: Yes