-
Notifications
You must be signed in to change notification settings - Fork 19
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
Firehose check error #69
Comments
I've set it up your way for now :-) |
Validator needs fix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I got 2 errors regarding Firehose
port is non-standard (not using 443) and may be unusable by some applications, field=<node[3].ssl_endpoint>, api_url=https://boid-firehose.animusystems.com:9000, port=<9000>, timeout=<2 s>
and
received unexpected content_type, value=<text/plain>, field=<node[3].ssl_endpoint>, api_url=https://boid-firehose.animusystems.com:9000, elapsed time=<0.6 s>, timeout=<2 s>, validated at=<2021-05-15 13:04 UTC>
I thought the idea is to use standarized port 9000 - that's already setup on my end
not sure why is 2nd error showing as I tested it multiple times and it returns proper data
it's connected to firehose setup on telos chain
https://validate.eosnation.io/telos/producers/bp.boid.html
The text was updated successfully, but these errors were encountered: