502 Bad Gateway

by tnys on

Hi

When connecting to api.flukso.net on iOS, I tend to receive 502 Bad Gateway responses while e.g. querying

https://www.flukso.net/api/sensor/91f8991e2d96b408320f32beab385df6?versi...

with proper token and version set in HTTP headers. This is the response I'm getting:

  1. <html>
  2.         <head><title>502 Bad Gateway</title></head>
  3.         <body bgcolor="white">
  4.         <center><h1>502 Bad Gateway</h1></center>
  5.         <hr><center>nginx/1.0.10</center>
  6.         </body>
  7. </html>

Any clue?

Thanks
Tom

‹ a possible widget for the flukso displaying charts in javascript Problem with dash in Chrome (Versie 40.0.2214.115) in Windows 8.1 ›
icarus75's picture
icarus75 |

That's rather strange. There hasn't been any server fault condition or maintenance window recently. This curl command works like a charm on my box:

  1. icarus75@cirrus:~ $ curl -v -X GET -H "Accept: application/json" -H "X-Version: 1.0" -H "X-Token: d8a8ab8893ea73f768b66b45234b5c3a" "https://www.flukso.net/api/sensor/c1411c6b4f9910bbbab09f145f8533b9?interval=hour&unit=watt"

icarus75's picture
icarus75 |

Should be fixed now. Can you confirm?

Ciarly's picture
Ciarly |

Hi
I think I have the same error

curl -k -v -X GET -H "Accept: application/json" -H "X-Version: 1.0" -H "X-Token: mytoken" "https://api.flukso.net/sensor/mysensor? interval=hour&unit=watt"

response
...
> User-Agent: curl/7.40.0
> Host: api.flukso.net
> Accept: application/json
> X-Version: 1.0
> X-Token: mytoken
>
< HTTP/1.1 502 Bad Gateway
< Server: nginx/1.4.7
< Date: Mon, 02 Mar 2015 20:38:52 GMT
< Content-Type: text/html
< Content-Length: 172
< Connection: keep-alive
<

502 Bad Gateway

502 Bad Gateway
nginx/1.4.7

* Connection #0 to host api.flukso.net left intact

Thank for help

Ciarly's picture
Ciarly |

sorry
I have just solved the problem
thank