forex_python.converter.RatesNotAvailableError: Currency Rates Source Not Ready

[aPischel]

Receiving the error with v1.6 installed. Tried a request from the api website, https://theforexapi.com , as well as going there in a browser (Chrome) but received 502: Bad Gateway. Please let me know if there is something else I can try,

Thanks!

[coding-by-sea]

Got the same error. Please give an ETA if possible. Thanks!

[blaaaaaaa]

https://theforexapi.com/ seems down. that is the api that is queried.

[F1x3rG]

Same issue here. Do you have an alternative?

[ate08]

Experiencing the same issue as well

[tim-arney]

Just installed forex v1.6 and experiencing the same issue. Tried putting the rates request in a backoff block and let it run for some time, but still no luck. Using python v3.8.

[SocOrg]

Same issue here. The first request succeeds. Subsequent ones fail. Is it related to having a paid service? I assumed theforexapi.com is free?

[soocer134]

same issue here

[abhijeet-1110]

Hi Guys,Issue Was Fixed.Please Check Now.Still you are facing issue,please let us know

[SocOrg]

Just tried and getting an error. Same error as my earlier screen shot.

[abhijeet-1110]

Pull the latest code from the master branch and try it. PFA

Regards, B.Abhijit Reddy

On Thu, Sep 2, 2021 at 1:11 PM SocOrg @.***> wrote:

Just tried and getting an error. [image: image] https://user-images.githubusercontent.com/35916595/131802999-7f19584b-e8d7-47fa-a31a-772668468f1d.png

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/MicroPyramid/forex-python/issues/100#issuecomment-911326165, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQOYZ3VB6YG2RLFIMDE75T3T74TEFANCNFSM5C5QC5MA . 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.

[abhijit111093]

[SocOrg]

Works great now, thanks!

[vnmabus]

When is the new release containing this fix scheduled?

[alfonsrv]

Can confirm historic data loads with current master branch code.

[abhijeet-1110]

@alfonsrv yes, data is available from 1999-01-04

[aPischel]

Looks to be working! Thanks!!!

[alfonsrv]

What I mean is, we need a new version on pypi as historical data only works with the current master branch.

[vnmabus]

Can anyone publish a new PyPI release, please, @ashwin31?

[dholladay00]

I am seeing this issue presently.

[ashwin31]

@dholladay00 can you check now?

[ashwin31]

@vnmabus new version released in December.

[dholladay00]

It appears to be working again, thanks @ashwin31

[Maria-Fox]

Hey, folks. Looks like this issue is back! Working w/ version 1.6 as the repo instructs. Can we look into this?

[pcbzmani]

Same issue, when i try to convert QAR, TWD to INR.

used forex-python 1.8

[johnathan-booy]

Same issue as well. Every request results in an error RatesNotAvailableError("Currency Rates Source Not Ready")

[egemen1109]

I am facing the same issue, downgraded to 1.6, still persists, 1.8 worked fine couple of weeks ago without problem. The API website is down, that probably is the issue.

#121 This probably relates to the same problem, I think only solution is to wait until the source is fixed.

[GLeonov]

Ping ...

Same error, stopped working on Friday 23rd of September, 2022; any chance this is fixed at some point?

[kabdrau]

when I run following code: from forex_python.converter import CurrencyRates \n c = CurrencyRates() \n c.convert('USD', 'EUR', 100) I get error: forex_python.converter.RatesNotAvailableError: Currency Rates Source Not Ready

[tg295]

Also experiencing the same old error

[jsikst]

from forex_python.converter import CurrencyRates

c = CurrencyRates() USDSEK = c.get_rate('USD', 'SEK')

Gives forex_python.converter.RatesNotAvailableError: Currency Rates Source Not Ready

Does not matter if the day is a weekday or not, tried both. And I'm on version 1.8 so should be no issue with that.