Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Hoodie App Tracker - 401 Unauthorized from client.js - signout and edit email error

See original GitHub issue

I did a fresh install via git clone https://github.com/hoodiehq/hoodie-app-tracker.git and then npm install. I am running via npm start and it shows me the cute little dog, which I’m assuming means all systems are green. Adding items is fine and I can create an account fine. However when I sign out or edit my email, I get a 401 error. I attached the screenshots. I have a hunch the client is not sending an Authorization header.

screen shot 2016-10-29 at 12 25 18 pm

screen shot 2016-10-29 at 12 24 38 pm

Details:

I have not installed CouchDB and I don’t have a PouchDB backend. I think the username and password info gets created within browser. I don’t see how that could be a problem but I’m noting it here.
I am using node v6.8.1 and npm v3.10.8 and I am on Mac OS X: El Capitan.
Results from npm ls | grep hoodie

Lean-Mean-Machine:hoodie-app-tracker michael$ npm ls | grep hoodie
hoodie-app-tracker@ /Users/michael/JSProjects/hoodie/hoodie-app-tracker
├─┬ hoodie@24.3.0
│ ├─┬ @hoodie/account@2.0.1
│ │ ├── @hoodie/account-client@4.4.0
│ │ └─┬ @hoodie/account-server@4.0.5
│ ├─┬ @hoodie/admin@1.2.2
│ ├─┬ @hoodie/client@5.0.7
│ │ ├── @hoodie/account-client@2.8.0
│ │ ├─┬ @hoodie/connection-status@3.0.0
│ │ ├── @hoodie/log@2.1.0
│ │ ├─┬ @hoodie/store-client@1.0.0
│ │ │ ├── hoodie-zuul-config@2.0.0
│ │ │ ├─┬ pouchdb-hoodie-api@1.6.4
│ │ │ └── pouchdb-hoodie-sync@1.4.1
│ ├─┬ @hoodie/server@21.1.1
│ │ ├─┬ @hoodie/store-server@2.1.5
│ ├─┬ @hoodie/store@1.0.4
│ │ └─┬ @hoodie/store-client@5.0.12

Issue Analytics

State:
Created 7 years ago
Reactions:1
Comments:12 (10 by maintainers)

Top GitHub Comments

3reactions

Stickswordcommented, Nov 1, 2016

@gr2m not a problem! I did a fresh npm install and everything seems fine. I’ll continue to poke around and eventually contribute, code-wise, to Hoodie 😃

0reactions

gr2mcommented, Nov 1, 2016

thanks for checking Michael!

Top Results From Across the Web

401 Error: 5 Ways to Troubleshoot and Fix It - Hostinger

The 401 Unauthorized error is triggered by unauthenticated requests made to a WordPress web server. Learn how to identify and fix the issue....

HTTP 401 Unauthorized Error | What Is and How to Fix?

401 Unauthorized Error is an HTTP response status code indicating the request sent by the user couldn't be authenticated.

Untitled

Ochca intranet, Phase 6 desktop einfrieren, New holland c190 track skid steer? Prada luggage bag, Oscar naibei, Maeve and liz, Doug middlebrook wiki?...

Untitled

Mysql order by 0 asc, Uaap cdc 2012, Film kinowy dragon ball 2015, Xblues, Calcare roccia sedimentaria, Dirt track racing games for ps3,...

Untitled

#Psoriasis Tips for mistake free dieting, Takshitapaleis utrecht, Les cadeaux d'anniversaire pour amis, Food consumer trends 2016, Hallow crown, ...