Viewing 15 replies - 1 through 15 (of 23 total)
  • Yes before updating plugin at production site tested development site. Even i am getting this error once in a while.

    Though i am checking at my end if i have done anything to get this error… will get back once i am done updating my custom adopter and all required setups…

    Plugin Author dashed-slug.net

    (@dashedslug)

    Thank you both for reporting.

    I am having trouble reproducing this on my end.

    Can you please tell me if the problem persists when you:

    1. Clear your browser’s cache and reload the page (long shot)

    2. Go to Wallets -> Frontend settings -> and enable the Legacy APIs option?

    let me know please

    thanks

    yes cleared all cache and everything .. thanks for this issue… also i removed so many stored user/password which wanted to do for a long time but did not get time … ??

    Let me first open dashboard … it’s taking ages to open

    Plugin Author dashed-slug.net

    (@dashedslug)

    If you are in a production environment you should be able to downgrade to 2.13.7 until this is resolved, if it is indeed a bug in the plugin. There were no DB schema changes so there should be no problem to downgrade.

    I would like to know the following:

    1. Does the “Legacy APIs” option help?

    2. Which coin adapter(s) are you using?

    3. Can you use your browser to inspect the XHR requests from the frontend to the server? What are the response payloads? If you cannot do this, can you let me login to a site where the problem occurs so I can have a look?

    thanks

    Plugin Author dashed-slug.net

    (@dashedslug)

    4. Does the problem persist if you disable Wordfence or other security plugins/firewalls?

    After disabling rates seems it’s working… let me get back to you on it…

    Plugin Author dashed-slug.net

    (@dashedslug)

    Thanks. Did you try enabling a different provider in the exchange rates settings?

    no i don’t have any … you gave me link to git… but i have no knowledge in php other than copy pasting and tweaking here and there … ??

    i need to create a stable php base rates for BTC and USD

    Plugin Author dashed-slug.net

    (@dashedslug)

    No, I meant, please try to go to your admin interface, then to Wallets and Rates, then you will be able to choose between exchange rates providers, i.e. bittrex, poloniex, etc. No programming knowledge required for this.

    Did you try to change to another option? Does the problem with error 500 persist then? This was my question.

    Thanks. Let me know.

    oh by the way always got following error on enabling poloniex

    Invalid argument supplied for foreach() in /Users/User/Sites/Site/wp-content/plugins/wallets/includes/rates.php on line 654

    Plugin Author dashed-slug.net

    (@dashedslug)

    This is a network issue. It would only occur if your server is unable to retrieve the following URI:

    https://poloniex.com/public?command=returnTicker

    I will make the code a little more robust to cater for that. Does the 500 error persist when you switch to any other provider?

    It shows once “Could not contact server. Status: error Error:” when rate provider switched.. after reloading page it seems to be working fine…

    But as i have so far noticed, as i am also working on UI at the same time… once in a while it does trigger error message.

    Plugin Author dashed-slug.net

    (@dashedslug)

    Thank you.

    After a long discussion with mc_deimon it seems that this is a complex issue that has to do with knockout.js cancelling AJAX requests under certain circumstances.

    Please downgrade to version 2.13.7 until I can roll out a patch for this.

    Sure no worries .. Thank you so much

Viewing 15 replies - 1 through 15 (of 23 total)
  • The topic ‘Could not contact server.’ is closed to new replies.