Blank screen opening localhost:4040

[BloomSN]

Hi,

might be completely stupid question but still, i am trying to set up this on windows server 2012 r2 with npm 3.8.1 and Node.js 4.3.2 all goes well but when i am trying to access dashboard (i have set link to app hosted on parse.com) i get white screen on localhost:4040. Any idea?

Thanks a lot.

[peterdotjs]

@BloomSN can you provide a screen shot of any console errors you see in the browser? As well as any logs/errors you see in the terminal that is running the server?

[BloomSN]

Here are both screens. Hope it helps, if you need more i will get more :)

Thanks

[drew-gross]

I've seen this issue before, it's due to the express app serving index.html even when the request is for dashboard.bundle.js. I haven't had the chance to track down the error yet.

[flovilmart]

Should be fixed with #65 https://github.com/ParsePlatform/parse-dashboard/pull/65/files#diff-7a1c52248764301345435dccf3ec051eR31

[thamer898]

@flovilmart how to update parse server example to be 2.1.4 without any errors ?

[BloomSN]

Great the fix works :) Thanks

[natanrolnik]

I'm having the same Unexpected token < when deploying to Heroku.
On localhost, it works fine and I can see my apps. On Heroku, I'm setting PARSE_DASHBOARD_ALLOW_INSECURE_HTTP to 1. I'm using version 1.0.9, and Parse Server v. 2.2.6.

Any ideas why I'm having this error?

[drew-gross]

That usually means the dashboard never got built. If you follow the instructions in the README and install from npm you should get the already-built dashboard.

[natanrolnik]

So instead of deploying the fork of this repo, I setup a new project using the parse-dashboard npm package, and it's working great, deployed to Heroku. I also added a CNAME dns record on my domain, so I can have parse.mydomain.com 😃