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

Where to find appID and masterkey when mongoDB is installed on AWS EC2 Machine #538

Closed
naveenksingh opened this issue Sep 21, 2016 · 1 comment
Labels
state:wont-fix Won’t be fixed with a clearly stated reason

Comments

@naveenksingh
Copy link

hello, I have mongoDB installed on AWS EC2 instance from where I am trying to connect Parse Server installed on my local pc. when I try to connect parse server to parse.com apps using their appid and masterkey it just works fine. but when I try to connect to my mongoDB instance on EC2 then it says "Server not reachable: unable to connect to server".

capture

I already started the server using mongod command on the terminal.
I checked the securityGroup it is open to all requests.
I checked the database it exist with data in it.
I have the following code in configuration file to connect

{
  "apps": [
    {
      "serverURL": "https://api.parse.com/1",
      "appId": "TWxCk7***************************JZ32k3",
      "masterKey": "S*********t3234*******************i",
      "appName": "ParseServer"
    },
    {
      "serverURL": "https://api.parse.com/1",
      "appId": "x544******************4343************SPtRO",
      "masterKey": "8B4******************Y32fkiiU782IL",
      "appName": "ParseServer 2"
    },
    {
      "serverURL": "http://dbuser:Password@ec2-**4-2**-**4-1*9.compute-1.amazonaws.com:27017/db",
      "appId": "x544******************4343************SPtRO",
      "masterKey": "8B4******************Y32fkiiU782IL",
      "appName": "AWS"
    }
  ]
}

Note: ParseServer2 and AWS apps have same key because the db on EC2 is migrated from it.

Help me please. thanks in advance

@stale
Copy link

stale bot commented Jan 11, 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.

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

1 participant