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)
8 replies
-
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.
-
Ok, experimented a bit. This seems to work for me:
curl -XPOST -H 'Accept: text/html' 'https://link-ip.nextdns.io/$MAGIC_STUFF'
-
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.
Content aside
-
3
Likes
- 2 yrs agoLast active
- 8Replies
- 377Views
-
7
Following