Skip to content

Either localhost nor 0.0.0.0 are valid addresses for local dashboard and parse server #782

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

Closed
3 tasks done
MichelBahl opened this issue Oct 17, 2017 · 2 comments
Closed
3 tasks done
Labels
state:wont-fix Won’t be fixed with a clearly stated reason

Comments

@MichelBahl
Copy link

MichelBahl commented Oct 17, 2017

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

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

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

Issue

Run parse dashboard without users works fine with localhost as serverURL,
if users were defined localhost break the dashboard, to fix this I have to enter a
static ip.

Environment Setup

Raspberry pi jessie 8.0
node 7.4.0
Parse Server 2.6.3
Parse Dashboard 1.1.0

Steps to reproduce

This won't work:

{
  "apps": [
    {
      "serverURL": "http://localhost:1337/parse",
      "appId": "myAppId",
      "masterKey": "myMaster",
      "appName": "myAppTest"
    }
  ],
  "users": [
    {
      "user":"test",
      "pass":"test",
      "apps": [{"appId": "myAppId"}]
    }
  ]
}

This will work as expected:

{
  "apps": [
    {
      "serverURL": "http://192.168.0.2:1337/parse",
      "appId": "myAppId",
      "masterKey": "myMaster",
      "appName": "myAppTest"
    }
  ],
  "users": [
    {
      "user":"test",
      "pass":"test",
      "apps": [{"appId": "myAppId"}]
    }
  ]
}

This will work too:

{
  "apps": [
    {
      "serverURL": "http://localhost:1337/parse",
      "appId": "myAppId",
      "masterKey": "myMaster",
      "appName": "myAppTest"
    }
  ]
}

Logs/Trace

Note: If you get a browser JS error please run npm run dev. This will provide source maps and a much more useful stack trace.

@somq
Copy link

somq commented Apr 25, 2018

@MichelBahl @natanrolnik Any news on this one ?

@stale
Copy link

stale bot commented Jan 10, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the state:wont-fix Won’t be fixed with a clearly stated reason label Jan 10, 2019
@stale stale bot closed this as completed Jan 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:wont-fix Won’t be fixed with a clearly stated reason
Projects
None yet
Development

No branches or pull requests

2 participants