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.

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

502 Proxy Error using tnrs_match_names #109

Closed
marknovak opened this issue Apr 22, 2018 · 4 comments
Closed

502 Proxy Error using tnrs_match_names #109

marknovak opened this issue Apr 22, 2018 · 4 comments

Comments

@marknovak
Copy link

Hi,
I'm trying to run tnrs_match_names on just over 1000 taxa and am receiving the following 502 proxy error. This seems to be a new issue as it didn't occur for me ~6 months ago when I last ran my analyses. It's not 100% consistent in that it did work once in ~20 attempts. It also happens far less frequently or not at all when I run much smaller batches of taxa. (Unfortunately the output can't be merged...see #101.)

More than 100 taxa to match. ... Error: HTTP failure: 502
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>502 Proxy Error</title>
</head><body>
<h1>Proxy Error</h1>
<p>The proxy server received an invalid
response from an upstream server.<br />
The proxy server could not handle the request <em><a href="/v3/tnrs/match_names">POST&nbsp;/v3/tnrs/match_names</a></em>.<p>
Reason: <strong>Error reading from remote server</strong></p></p>
<hr>
<address>Apache/2.4.10 (Debian) Server at api.opentreeoflife.org Port 443</address>
</body></html>

Am I right in guessing that this problem is not on your (rOTL) end but rather the OTL itself? (I hope not!)

Oh, I'm pulling the package from GitHub, am running R 3.3.3 on a Max (OS 10.12.6), and have tried it on two different machines...in case that's relevant.

thanks
@josephwb
Copy link
Contributor

@marknovak This definitely sounds like an OT issue. I'll ping them.

@josephwb
Copy link
Contributor

Looks like the API was down. Can you try again @marknovak?

@fmichonneau
Copy link
Member

FWIW another user noticed me about this issue and told me that it was working again now.

@marknovak
Copy link
Author

It is indeed working again! Thanks to you both.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@josephwb @marknovak @fmichonneau