WordPress database error: [Can't create/write to file '/tmp/#sql-temptable-4db-13bb9d-131.MAI' (Errcode: 28 "No space left on device")]SELECT p.* FROM wp_mdb_forum_posts AS p LEFT JOIN wp_mdb_forum_posts AS q ON( q.Id = p.ParentId AND p.Id = q.AcceptedAnswerId ) WHERE p.PostTypeId = 2 AND p.ParentId = 104282 GROUP BY p.Id ORDER BY CASE WHEN q.Id IS NOT NULL THEN 1 ELSE 0 END DESC, p.UpvoteCount DESC, p.CreationDate ASC
Topic: Access denied after license renewed
We just renewed our license for 1 more year but install via npm still gives Access denied error. Do we need a new GIT token after each renewal?
Error from terminal: npm ERR! remote: HTTP Basic: Access denied
Closed
This topic is closed.
FREE CONSULTATION
Hire our experts to build a dedicated project. We'll analyze your business requirements, for free.
Closed
- User: Free
- Premium support: No
- Technology: MDB Angular
- MDB Version: 8.7.0
- Device: PC
- Browser: Chrome
- OS: Mac
- Provided sample code: No
- Provided link: No
Mateusz Leciejewski staff pro premium priority commented 6 years ago
@ffdev No, it doesn't work that way. We'll check what happened & get back to you tomorrow.
ffdev commented 6 years ago
@Mateusz Leciejewski Any update on this? Our CI is getting error because of this.
Mateusz Leciejewski staff pro premium priority commented 6 years ago
@ffdev sorry for my lack in response. Are you able to sign in at your gitlab account?
ffdev commented 6 years ago
@Mateusz Leciejewski We can both log onto your gitlab repo yes. Should we generate a new personal token and try with that instead?
Bartłomiej Malanowski staff pro premium commented 6 years ago
Could you please try to regenerate your token?
ffdev commented 6 years ago
@Bartłomiej Malanowski After generated new token we are reciving a new error:
fatal: unable to access 'https://oauth2/:newgeneratedtoken.mdbootstrap.com/mdb/angular/ng-uikit-pro-standard.git/': Could not resolve host: oauth2
ffdev commented 6 years ago
@Bartłomiej Malanowski @Mateusz Leciejewski Any update on this?
ffdev commented 6 years ago
It was our fault that we had some typos on the link, everything now works again after new token generated.