New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Importing Currency Rates via Webservicex Fails #8006

Closed
tsmith1985 opened this Issue Dec 31, 2016 · 4 comments

Comments

Projects
None yet
5 participants
@tsmith1985

tsmith1985 commented Dec 31, 2016

Trying to import exchange rates via Webservicex fails for most rates and results in error messages saying that the service was unable to retrieve the rates.

Preconditions

  • Magento CE v2.1.3
  • PHP v7.0.14
  • MySQL v14.14 Distrib 5.7.16, for osx 10.12

Steps to reproduce

  1. Log into Admin
  2. Navigate to Stores > Settings > Configuration > General > Currency Setup
  3. Select Use system value for Base Currency #8003
  4. Select Yes for Enabled in the Scheduled Import Settings section
  5. Click Save Config if necessary and flush the cache
  6. Navigate to Stores > Currency > Currency Rates
  7. Try to import rates via Webservicex

Expected result

  1. The rates should imported successfully

Actual result

webservicex_errors

@veloraven

This comment has been minimized.

Contributor

veloraven commented Jan 4, 2017

@tsmith1985 thank you for your report.

I was not able to reproduce this issue. I either get the result from #8003 when values are not imported at all, or I get all the values imported.
Can you please check this case once more, if it still reproduces? As it possible that there was some issue on Webservicex side.

If it does, please provide additional Information:

  • Was it clear Magento install or upgrade from some previous version?
  • What settings did you use for Scheduled Import Settings?
  • Could you provide full description of your currency settings? As I can see from the screenshot there was some trouble with all currencies except Euro and Pounds.
@hostep

This comment has been minimized.

Collaborator

hostep commented Jan 4, 2017

@tsmith1985 & @veloraven: it probably is just the external service Webservicex which was down at that time.
I've seen it happen from time to time over the last few years in Magento 1 (where Webservicex is the only service) in Magento 2, luckily there are some alternatives which you can use, I don't really trust Webservicex any longer based on my past experience with it.

So this doesn't look like a Magento issue, but just an issue over at the external Webservicex project.

@paales

This comment has been minimized.

Contributor

paales commented Jan 6, 2017

Internal advise to customers is to move away from Webservicex and move to Yahoo finance/fixer.io.

@magento-engcom-team

This comment has been minimized.

Contributor

magento-engcom-team commented Sep 13, 2017

Thank you @hostep and @paales for suggestions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment