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

502 Bad Gateway - no resolver defined #49

Closed
brylie opened this issue Nov 13, 2014 · 3 comments
Closed

502 Bad Gateway - no resolver defined #49

brylie opened this issue Nov 13, 2014 · 3 comments
Milestone

Comments

@brylie
Copy link
Contributor

brylie commented Nov 13, 2014

I was able to get a basic query to work using the Getting Started guide, after some minor tweaking of the URL parameters.

When I add a second API and call its URL, I get a 502 Bad Gateway.

@brylie
Copy link
Contributor Author

brylie commented Nov 13, 2014

After further consideration, I realized this seems like a router issue. The tail of the router_error.log contains the following:

2014/11/13 10:12:37 [error] 20278#0: *209 no resolver defined to resolve api_umbrella_6de92ad1-1994-4fbf-9faa-bec521025e70_backend, client: 109.240.164.253, server: _, request: "GET /tags HTTP/1.1", host: "api.avoindata.net"

How do I define a resolver to resolve api.avoindata.net?

@brylie brylie changed the title 502 Bad Gateway - nginx 502 Bad Gateway - no resolver defined Nov 13, 2014
@brylie
Copy link
Contributor Author

brylie commented Nov 13, 2014

OK... I found out where I went wrong. On the Step 2: Add a new backend: I neglected to enter a server. Oops :)

@brylie brylie closed this as completed Nov 13, 2014
@GUI GUI added this to the v0.7 milestone Feb 10, 2015
@GUI
Copy link
Member

GUI commented Feb 10, 2015

As a quick heads up, the new v0.7 packages that have been released should solve this issue with much better error validation surrounding the API Backend forms. Now you won't be able to save the form without filling in the backend section (and we've made a variety of other changes to try to improve the flow and error handling).

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