echoip: Cloudflare stops the API access

While trying to access the curl ifconfig.co/ I’m getting cloudlfare challenge that is impossible to do in curl. The “How do I get this programmatically?” section does not work.

<!DOCTYPE html>
<html lang="en-US">
<head>
    <title>Just a moment...</title>
...
        <h2 class="h2" id="challenge-running">
            Checking if the site connection is secure
        </h2>

Remove the cloudflare, of this website is not usable for its intended purpose.

About this issue

  • Original URL
  • State: open
  • Created a year ago
  • Reactions: 3
  • Comments: 19 (1 by maintainers)

Most upvoted comments

Yes, the service is worthless as is, but fortunately there are alternatives that actually work:

curl https://api.ipify.org/
curl -6 https://api64.ipify.org/

@hydrargyrum It is intentional since we could not check tor exit nodes against IPv6 exit nodes. If some amount of donation is received will host another instance under a new domain that will support both IPv4 and IPv6.

For anyone finding the same problem I made the host of https://ifconfig.la which is cloudflare-free.

I don’t think this will be done. It would expose the origin server and lose ddos protection. The compromise is to toggle “bot fighting mode” off.

im asking to disable cloudflare for the main website

Sourcing from 35.79.238.0/24, but im not asking to whitelist this subnet. Cloudlfare defeats the purpose of API access, cloudflare needs to be removed?