Jobs are no longer displaying in Parse Dashboard after latest update

[richarddwalsh]

Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Dashboard!

• You're running version >=1.0.19 of Parse Dashboard.

• You're running version >=2.2.24 of Parse Server.

• You've searched through existing issues. Chances are that your issue has been reported or resolved before.

Environment Setup

Mac OS X 10.12.1

Steps to reproduce

Start up dashboard from config:
parse-dashboard --config ~/parse-dashboard-config.json
The dashboard is now available at http://0.0.0.0:4040/

Browse to dashboard url http://0.0.0.0:4040/
Click to Jobs,
screen is blank

Dev tools output is:
POST http://localhost:1337/parse/cloud_code/jobs?per_page=50 403 (Forbidden)
POST http://localhost:1337/parse//apps/MITGA/cloud_code/jobs/data 403 (Forbidden)
POST http://localhost:1337/parse/releases/latest 403 (Forbidden)
POST http://localhost:1337/parse/cloud_code/jobs?per_page=50 403 (Forbidden)
POST http://localhost:1337/parse/cloud_code/jobs?per_page=50 403 (Forbidden)

Logs/Trace

Note: If you get a browser JS error please r

un npm run dev. This will provide source maps and a much more useful stack trace.

[richarddwalsh]

I've also noticed that I can't view config either.

[mario]

Try setting javascriptKey in the dashboard config.

[richarddwalsh]

I have set it:
{ "serverURL": "http://localhost:1337/parse", "databaseURI": "mongodb://localhost:27017/mcara-dev", "appName": "MUTFA", "appId": "myAppId", "masterKey": "myMasterKey", "javascriptKey": "myJavascriptKey", "restAPIKey": "myRestApiKey", "clientKey": "myClientKey" }

[anashalb]

I am facing the same issue.. Were you able to resolve it?

[richarddwalsh]

@anashalb Nope I have not been able to resolve it yet. I think it may have something to do with the fact that it is triggering a POST method instead of GET??

I've even updated bother server and dashboard to the latest versions, still no fix.

[dstarke]

The request to get the job list is not being issued with the master key. See JobStore.js line 33.

I think adding the {useMasterKey:true} option there should fix it.

Looking at #575, though, that may not ultimately be the correct answer, and I'm not sure why it works in some environments and not in others.

[dstarke]

Another way to resolve this is to remove the javascriptKey (and maybe also the clientKey) from your configuration. The job request then gets issued correctly. This is why it was working for me in some environments and not in others.

[natanrolnik]

This was fixed in the latest release.