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

ODK collect connection failure #4

Open
burakku opened this issue Apr 21, 2015 · 5 comments
Open

ODK collect connection failure #4

burakku opened this issue Apr 21, 2015 · 5 comments

Comments

@burakku
Copy link

burakku commented Apr 21, 2015

The setup steps are followed by the instruction from the documentation on ELMO's website. The procedures are tested working with the test drive server, but it fails with the one on AWS we setup.
Here are the screen shot of the ODK collect setup and the error page:

screenshot_2015-04-21-11-12-25
screenshot_2015-04-21-11-12-35

@CoolestNerdIII
Copy link
Contributor

For some reason I am unable to see "Other Platform Settings". Try these 2 things:

@burakku
Copy link
Author

burakku commented Apr 21, 2015

Since we use ELMO as our platform, I choose the Platform setting to "other". If you did the same you can see "General Setting" -> "Other Platform Settings".
I tried to change the path to /forms and it doesn't work either. Actually the path /formList works with the test drive server that's why I keep it. The documentation on ELMO's website is correct. If you follow the steps you can get forms from the test drive. For some reasons it doesn't work with ours.

@CoolestNerdIII
Copy link
Contributor

Well on the site it also mentions that the link could be different than what is shown on the test drive

Note: The URL of the database to be used by a mission depends on what host the mission is using. Missions outside of the Carter Center will likely have their own hosting services and need to use a different URL from the one in the example above.

If you add the /en before /m you will get an error about not being logged in. Just try a different variation. Also instead of admin, create an account and password and try it that way.

@CoolestNerdIII
Copy link
Contributor

Ok I see the error looking up a fix

@CoolestNerdIII
Copy link
Contributor

Ok so your error is that you are using https. We do not currently have ssl setup so you will have to use http instead.

There is another error though in that it won't allow me to log in

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants