Cryptonator service unavailable V1.1.1

[pinthenet]

I've not received any updates since around 18:30 CET on 24th Jan. Found the following in the HA log: Request returned a bad error code 503 11:26:31 – (ERROR) cryptostate (custom integration) - message first occurred at 24 January 2022, 20:31:57 and shows up 1790 times 503 Server Error: Service Temporarily Unavailable for url: https://api.cryptonator.com/api/ticker/eth-eur 11:26:31 – (ERROR) cryptostate (custom integration) - message first occurred at 24 January 2022, 20:31:57 and shows up 1790 times I can access the URL from a browser without error. I have restarted HA (twice). Any one else?

[Revival67]

Same problem here, also since yesterday no data.

[BigNocciolino]

Hi, thanks for reporting, today I found this issue, but now I can not investigate. This afternoon I will try.

[pinthenet]

Good that you found it so quickly Alfonso.

No rush at the moment, everything’s going down anyway :-P

From: Alfonso Sorrentino @.> Sent: Tuesday, 25 January 2022 11:48 To: BigNocciolino/CryptoTracker @.> Cc: Author @.>; pinthenet @.> Subject: Re: [BigNocciolino/CryptoTracker] Cryptonator service unavailableV1.1.1 (Issue #15)

Hi, thanks for reporting, today I found this issue, but now I can not investigate. This afternoon I will try.

— Reply to this email directly, view it on GitHub https://github.com/BigNocciolino/CryptoTracker/issues/15#issuecomment-1021053061 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AA2OBP6BUXESKOSTHETJDODUXZ5WNANCNFSM5MX3JGLQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub . You are receiving this because you authored the thread.Message ID: @.***>

[ { @.": "http://schema.org", @.": "EmailMessage", "potentialAction": { @.": "ViewAction", "target": "https://github.com/BigNocciolino/CryptoTracker/issues/15#issuecomment-1021053061", "url": "https://github.com/BigNocciolino/CryptoTracker/issues/15#issuecomment-1021053061", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { @.": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[t34wrj]

Same here.

[ruigaspar]

The problem is with the cryptonator API. Now they added a browser checking before access to the website, but unfortunately also added it to the API. I think they will fix this, I hope...

[BigNocciolino]

Yes, they seem to have restricted the API access to the web page only, in fact the API is unreachable with curl, wget and postman

I hope they will fix this...

This is the postman output:

[ruigaspar]

Yes, they seem to have restricted the API access to the web page only, in fact the API is unreachable with curl, wget and postman

I hope they will fix this...

This is the postman output:

Exactly, We need to wait or explore another data source API....

[ruigaspar]

API fixed. @BigNocciolino you can close the issue...

[t34wrj]

Back for me too!

[pinthenet]

+1On 25 Jan 2022 21:37, t34wrj @.***> wrote: Back for me too!

—Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you authored the thread.Message ID: @.***>

[kevincaradant]

Hi @BigNocciolino

Indeed it working again since 3 days. However, I got always so many failed on logs

13000 failed occurrences :/. Is it possible to contact less often the api?

Thank you

Regards

Some crypto doesn't load also :(

NB: @BigNocciolino , If needed I open a new issu but I thought it was maybe the same ;)

[BigNocciolino]

Hi, thanks for reporting, I have increased the scan interval of the component. If that doesn't solve the problem, please open a new issue

[kevincaradant]

OK thank you I will update when it will be release on hacs and I will tell you

[pinthenet]

I'm seeing 503 again since yesterday afternoon.

[BigNocciolino]

Hi, really weird things have been going on since about yesterday afternoon, it seems that their sites have gone completely down, even the website.

This happens when I try to reach their site:

The API remains online, but can only be accessed from a browser, as these are the outputs of:

• Browser:

  

• Wget:

  
  [alfonso@Fisso ~]$ wget https://api.cryptonator.com/api/ticker/btc-usd
  --2022-02-05 13:28:28--  https://api.cryptonator.com/api/ticker/btc-usd
  SSL_INIT
  Caricato certificato CA "/etc/ssl/certs/ca-certificates.crt"

Risoluzione di api.cryptonator.com (api.cryptonator.com)... 104.22.62.82, 104.22.63.82, 172.67.10.138, ... Connessione a api.cryptonator.com (api.cryptonator.com)|104.22.62.82|:443... connesso. Richiesta HTTP inviata, in attesa di risposta... 503 Service Temporarily Unavailable 2022-02-05 13:28:28 ERRORE 503: Service Temporarily Unavailable.

EDIT: I hope they solve it as soon as possible, otherwise I could also consider using a different api, which does not require authentication / account creation.

[pinthenet]

In the last hour I think I’ve started to get responses again but always the same value (right side of graph). There was also a strange spike (actually 2) around yesterday lunchtime

Correction: I was too quick, I think it's working again

[BigNocciolino]

Now the API seems to be working, but there is a waiting time of about one minute:

This causes other problems, and therefore a delay for each sensor of about 10 seconds before failing at startup, also causing the problem of @kevincaradant in #19 ( This is a solvable problem, I'll commit for the fix later)

[pinthenet]

Any news?On 5 Feb 2022 16:58, Alfonso Sorrentino @.***> wrote: Now the API seems to be working, but there is a waiting time of about one minute:

This causes other problems, and therefore a delay for each sensor of about 10 seconds before failing at startup, also causing the problem of @kevincaradant in #19 ( This is a solvable problem, I'll commit for the fix later)

—Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you authored the thread.Message ID: @.***>

[BigNocciolino]

Hi, since this big problems with the Cryptonator API, i'm moving this project to a new API, provided by @fawazahmed0 (currency-api).

Development is taking place in the new branch new_api, also check the #20 PR

[pinthenet]

Thanks for the update Alfonso, good luck

From: Alfonso Sorrentino @.> Sent: Wednesday, 9 February 2022 00:17 To: BigNocciolino/CryptoTracker @.> Cc: Author @.>; pinthenet @.> Subject: Re: [BigNocciolino/CryptoTracker] Cryptonator service unavailableV1.1.1 (Issue #15)

Hi, since this big problems with the Cryptonator API, i'm moving this project to a new API, provided by @fawazahmed0 https://github.com/fawazahmed0 (currency-api https://github.com/fawazahmed0/currency-api ).

Development is taking place in the new branch new_api https://github.com/BigNocciolino/CryptoTracker/tree/new_api , also check the #20 https://github.com/BigNocciolino/CryptoTracker/pull/20 PR

— Reply to this email directly, view it on GitHub https://github.com/BigNocciolino/CryptoTracker/issues/15#issuecomment-1033157090 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AA2OBP7ACUOCNOCLQTWONYDU2GP6XANCNFSM5MX3JGLQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub . You are receiving this because you authored the thread.Message ID: @.***>

[ { @.": "http://schema.org", @.": "EmailMessage", "potentialAction": { @.": "ViewAction", "target": "https://github.com/BigNocciolino/CryptoTracker/issues/15#issuecomment-1033157090", "url": "https://github.com/BigNocciolino/CryptoTracker/issues/15#issuecomment-1033157090", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { @.": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[BigNocciolino]

Hi I'm closing all the old issues, if there are problems with the new version, please open a new issue