{"action":"opened","issue":{"url":"https://api.github.com/repos/ParsePlatform/parse-server/issues/1060","repository_url":"https://api.github.com/repos/ParsePlatform/parse-server","labels_url":"https://api.github.com/repos/ParsePlatform/parse-server/issues/1060/labels{/name}","comments_url":"https://api.github.com/repos/ParsePlatform/parse-server/issues/1060/comments","events_url":"https://api.github.com/repos/ParsePlatform/parse-server/issues/1060/events","html_url":"https://github.com/ParsePlatform/parse-server/issues/1060","id":141330782,"number":1060,"title":"Cannot access API","user":{"login":"nitrag","id":197010,"avatar_url":"https://avatars.githubusercontent.com/u/197010?v=3","gravatar_id":"","url":"https://api.github.com/users/nitrag","html_url":"https://github.com/nitrag","followers_url":"https://api.github.com/users/nitrag/followers","following_url":"https://api.github.com/users/nitrag/following{/other_user}","gists_url":"https://api.github.com/users/nitrag/gists{/gist_id}","starred_url":"https://api.github.com/users/nitrag/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nitrag/subscriptions","organizations_url":"https://api.github.com/users/nitrag/orgs","repos_url":"https://api.github.com/users/nitrag/repos","events_url":"https://api.github.com/users/nitrag/events{/privacy}","received_events_url":"https://api.github.com/users/nitrag/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-03-16T16:42:10Z","updated_at":"2016-03-16T16:42:10Z","closed_at":null,"body":"Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!\r\n\r\n- [x] You've met the [prerequisites](https://github.com/ParsePlatform/parse-server/wiki/Parse-Server-Guide#prerequisites).\r\n\r\n- [x] You're running the [latest version](https://github.com/ParsePlatform/parse-server/releases) of Parse Server.\r\n\r\n- [x] You've searched through [existing issues](https://github.com/ParsePlatform/parse-server/issues?utf8=%E2%9C%93&q=). Chances are that your issue has been reported or resolved before.\r\n\r\n#### Environment Setup\r\n\r\nAWS Elastic Beanstalk v2.1.6 \r\nLocalhost v2.1.6\r\nJS SDK 1.7.1\r\nREST/cURL\r\n\r\n#### Steps to reproduce\r\n\r\nAny queries\r\n\r\n#### Logs/Trace\r\n\r\n[Screenshot](http://i.imgur.com/NbzbXBP.jpg)\r\n\r\nOkay! Another \"Cannot GET\" error.\r\n\r\nI have been using parse-server for over a month now so this isn't a newbie issue. I get the error on any and all API requests. \"Cannot GET /1/classes/****\" 403 Error. This all started (I noticed several hours later) after I got a message from Compose.io saying one of my Mongo servers restarted.\r\n\r\n1. I've been testing parse-server locally and on AWS elastic beanstalk for weeksnow. Never seen this issue. I've reverted code back to a known working version.\r\n2. I've deleted node_modules folder in parse-server-example and \"npm install\"\r\n3. Parse Hosted API works. I've verified the connection strings match. I've verified username/password on the database. I've reverted database back 4+ days. New user/password.\r\n4. The nodejs log is completely blank. VERBOSE=1\r\n5.  My mount is /1 but when I goto http://localhost:1337 I should see a welcome message. It says \" {\"error\":\"unauthorized\"}\" instead. I didn't use to get this. \r\n6. Tested cURL with master key (see [here](http://i.imgur.com/NbzbXBP.jpg)) and it still fails. I've verified cURL keys work.\r\n7. I've reverted parse-server to 2.1.5, and 2.1.4. No difference.\r\n8. I've reset cloud code to default to make sure there are no errors there.\r\n\r\nHow can I get the nodejs to be even more descriptive/trace? "}}