3

curl'ing link-ip getting internalServerError (500)

Over the weekend I began getting 500s when curling my link-ip address:

$ curl 'https://link-ip.nextdns.io/$MAGIC_STUFF'
{"errors":[{"code":"internalServerError"}]}

The link works in my web browser.  It turns out not specifying an `Accept` header results in the 500; if specified, it works.

$ curl 'https://link-ip.nextdns.io/$MAGIC_STUFF -H 'Accept: text/html''
$MY_IP_ADDRESS

(i.e. it works)

8replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • I have same issue. Specifying the 'Accept' header with curl doesn't work for me.

    And also that shouldn't be necessary, so seems like something changed in the server setup.

    Like
  • Ok, experimented a bit. This seems to work for me:

    curl -XPOST -H 'Accept: text/html' 'https://link-ip.nextdns.io/$MAGIC_STUFF'

    Like
      • Boris Bock
      • Boris_Bock
      • 10 mths ago
      • Reported - view

      Tobias Biehl 
      Thanks Mate! Works for me again now 👍

      Like
  • I've started getting this `{"errors":[{"code":"internalServerError"}]}` when updating my linked IP from my mobile since a few hours ago.

     

    I thought it was temporary, but since no one else seems to be having this issue right now, or they're simply not reporting it here, I'm suspecting that it could be because of the new IP address that I dynamically got(ie. DHCP), like, perhaps it's in a bad list or something? Because I've never had this issue happen before and I can confirm that my linked IP is indeed not updating.

     

    None of the above solutions work for me.

     

    Is there a status page that I could check to see if nextdns' servers (especially these link-ip.nextdns.io ones in every country, google hosted it seems) are functioning normally or not ?

     

    Right now link-ip.nextdns.io resolves to 172.217.17.147 or ghs4.googlehosted.com via these DNS Servers:

    45.90.28.230

    45.90.30.230

     

    Normally when updating the linked IP I'd get Status Code 200 and my real IP as text, but now it's status code 500 and that json:

     

    {"errors":[{"code":"internalServerError"}]}

     

    I tried with like 4 different clients, like curl and firefox.

    Any ideas?

     

    EDIT: for what is worth, everything is green here for every tab(like Overview, Europe): https://status.cloud.google.com/index.html but I'm not sure if that's where I should be checking for googlehosted hostnames.

    Like
    • Emanuel same same problem here. I think there should be technical support in place for this but I'm not finding anything, and it's really disappointing :/

      Like 1
      • Emanuel
      • Emanuel
      • 2 wk ago
      • Reported - view

      it got fixed, thanks!

      Like
      • Emanuel
      • Emanuel
      • 2 wk ago
      • Reported - view

      So, there's still a problem: even though the linked IP now gets updated correctly, the logs show no new entries and DNS requests that should've been blocked (ie. return 0.0.0.0) are not so! It's as if the linked IP wasn't actually updated, ie. all protection is off.

      Like
      • Emanuel
      • Emanuel
      • 2 wk ago
      • Reported - view

      Alright, it started working the instant I changed my IP and I've noticed that the difference is that a new key named "profile" was added when viewing the text at https://test.nextdns.io compared to before when protection was off, and of course the logs are now updating and the IPs that shouldn't resolve aren't. My guess is that some piece of code that turned on protection only executed when it detected that the currently updated linked IP is different than the last updated linked IP and for some reason my previous IP must've been already updated from before the Error 500 got fixed.

      Like
Like3 Follow
  • 3 Likes
  • 2 wk agoLast active
  • 8Replies
  • 173Views
  • 7 Following