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

Via error while trying to annotate a page on CloudFlare #2909

Closed
lenazun opened this Issue Feb 3, 2016 · 3 comments

Comments

Projects
None yet
4 participants
@lenazun
Contributor

lenazun commented Feb 3, 2016

Steps to repro:

Go to
https://via.hypothes.is/cafe.com
https://via.hypothes.is/https://medium.com/@nayafia/we-re-in-a-brave-new-post-open-source-world-56ef46d152a3

Expected: via loads with the page
Actual: You will get an error message:

Please enable cookies.
Error 1000 Ray ID: 26ef2a0da3261e5f • 2016-02-03 15:28:12 UTC

DNS points to prohibited IP

What happened?

You've requested a page on a website (cafe.com) that is on the CloudFlare network. Unfortunately, it is resolving to an IP address that is creating a conflict within CloudFlare's system.

What can I do?

If you are the owner of this website:
you should login to CloudFlare and change the DNS A records for cafe.com to resolve to a different IP address.

CloudFlare Ray ID: 26ef2a0da3261e5f • Your IP: 54.219.24.245 • Performance & security by CloudFlare

@lenazun lenazun added the P2: Urgent label Feb 3, 2016

@nickstenning

This comment has been minimized.

Show comment
Hide comment
@nickstenning

nickstenning Feb 5, 2016

Contributor

This is, as suggested by the document above, caused by the CloudFlare edge detecting and aborting what they think is an infinite loop in the routing.

In this case it isn't, and we convince them of that by stripping the CF-specific headers from the request before we pass it through via. Adding the following to the via nginx configuration has fixed this issue:

more_clear_input_headers CF-Connecting-IP;
more_clear_input_headers CF-Ray;
more_clear_input_headers CF-Visitor;
more_clear_input_headers CF-Ipcountry;
Contributor

nickstenning commented Feb 5, 2016

This is, as suggested by the document above, caused by the CloudFlare edge detecting and aborting what they think is an infinite loop in the routing.

In this case it isn't, and we convince them of that by stripping the CF-specific headers from the request before we pass it through via. Adding the following to the via nginx configuration has fixed this issue:

more_clear_input_headers CF-Connecting-IP;
more_clear_input_headers CF-Ray;
more_clear_input_headers CF-Visitor;
more_clear_input_headers CF-Ipcountry;
@dwhly

This comment has been minimized.

Show comment
Hide comment
@dwhly

dwhly Feb 5, 2016

Member

Awesome!

Member

dwhly commented Feb 5, 2016

Awesome!

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