Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parse-Server v2.2.11 unauthorized error #391

Closed
DazChong opened this issue Jun 2, 2016 · 5 comments
Closed

Parse-Server v2.2.11 unauthorized error #391

DazChong opened this issue Jun 2, 2016 · 5 comments

Comments

@DazChong
Copy link

DazChong commented Jun 2, 2016

As topic, parse-server previous version 2.2.10 are working fine.

As for version parse-server 2.2.11, iOS SDK and CURL test are working fine too. I inspect the error from the Chrome Dev Tools and discovered that parse-dashboard POST to serverInfo,_User, & _Installation are throwing error 403.

Not sure is parse-server issue or parse-dashboard.

Reverted back to parse-server 2.2.10 and parse-dashboard working again.

@drew-gross
Copy link
Contributor

Can you show your server logs please? 403 unauthorized usually means incorrect master key or something like that.

@DazChong
Copy link
Author

DazChong commented Jun 2, 2016

Ah.. I had it reverted and now testing on another app on other server within same dashboard.

I suspect the error came from _Installation or _User class as the error do not occurred on this app.

The app that I having issue does not require _Installation, _User, or _Session as it serve as my personal development database.

Are both (including _Session) required as default?

@DazChong
Copy link
Author

DazChong commented Jun 2, 2016

Follow up, same unauthorized issue appear again once I updated parse-server to 2.2.11.

Server side does not log anything even I turned on VERBOSE

iOS, PHP, CURL all working but not on parse-dashboard.

I created a new empty database instance to test but seem's like empty database doesn't affected. Will update again after more digging.

@theill
Copy link

theill commented Jun 3, 2016

I suspect parse-community/parse-server@03108e6 to be the issue. I'm having the same issue and in my case I'm running ParseServer behind an already basic authenticated route and thus the appId and masterKey will now be replaced with your username and password.

@DazChong
Copy link
Author

It seems like the error no longer an issue upon 2.2.12 update, running fine for few days since. Closing issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants