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.

Sign up for GitHub

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

Jump to bottom

PUBLIC FREME: external services fails because of "Bad Gateway" #37

Closed

andish opened this issue Sep 5, 2016 · 1 comment

Contributor

andish commented Sep 5, 2016

For e-Terminology and E-Translation:

{
  "exception": "eu.freme.common.exception.ExternalServiceFailedException",
  "path": "/e-translation/tilde",
  "message": "java.net.UnknownHostException: services.tilde.com: unknown error",
  "error": "Bad Gateway",
  "status": 502,
  "timestamp": 1473059257744
}

For E-entity:
https://api.freme-project.eu/current/e-entity/freme-ner/documents?language=en&dataset=dbpedia&mode=all

{
  "exception": "eu.freme.bservices.filter.proxy.exception.BadGatewayException",
  "path": "/e-entity/freme-ner/documents",
  "message": "Proxy failed: java.net.UnknownHostException: rv2622.1blu.de: unknown error",
  "error": "Bad Gateway",
  "status": 502,
  "timestamp": 1473059069456
}

Tested with public version - Full documentation:
http://api.freme-project.eu/doc/current/api-doc/full.html#!/e-Terminology/e_terminology

Member

jnehring commented Sep 5, 2016

I could fix this through a restart of FREME live. This is a dublicate of this bug: freme-project/FREMECommon#22

jnehring closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment