iitbritesh
Forum Replies Created
-
Hi Gijo
Just saw this has already been highlighted, but I have same issue when using the plugin with any page cache i.e. WP Fastest cache, etc.When we enable server side cache, the Flying scripts plugin stops working.
Is there a hook already that fixes this issue?
Thank you for the fast response. I shared login details via email.
Sorry, this got posted twice.
- This reply was modified 5 years, 10 months ago by iitbritesh.
No, Exact same error on sandbox.
The credentials were working for 20 days or so. We had ongoing successful transactions.
Credentials are 100% correct.Suddenly blocked 2 days back.
Clueless now ??
Hi team, Nope our website shows that the connection to the API could not be established. I have double checked the API keys etc.
Hi, thanks for the response – I understand that the IP is possible to extract from the domain. However, the following hostname/subdomain: > api.mangopay.com is pointed to CloudFlare and the “real” IP address is masked by CloudFlare.
It is also possible that Cloudflare blocks certain IP addresses due to Cloudflare security.
Do you agree? Is it possible to check this with Cloudflare?
Hi, after few days of working well – the API is again blocked from our server. It works again when tried from a new server. Could there be some firewall which is blocking requests from our server? I see you use Cloudflare – can Cloudflare be blocking us?
This is the message from my host –
We have investigated the matter carefully. Unfortunately, we were not able to locate any output that may give us a lead for further investigation. The only error message that we face is the one that you have provided in this ticket. With this in mind, it is possible that the API in question is blocked by the server firewall. Having this said could you please contact the API provider and ask them to provide you with the IP addresses associated with the server on which the mentioned API resider in order for us to whitelist the IP address and test once again.
Thank you for your patience and responses. I created a fresh VPS instance and setup the website again and it worked. So, you were right – the issue was with my server.
Although the PHP-Curl was installed, but it was probably something else which we could not figure out.
Thanks again – our website is working well with a wonderful escrow system – thanks to Mangopay and WP&Co.
Update: Tried https://api.mangopay.com as well as https://api.mangopay.com/v2.01 and both CURL requests worked.
https://prntscr.com/ltv10aThank you for the response. I logged in to the server through SSH and made a CURL request to the production API using instructions as provided in the documentation.
As you can see from this snapshot – https://prntscr.com/ltuwp9 – I was able to get an access token and a successful connection to the API.
So the server is definitely being able to connect to the API.
Hello there, thank you very much for the response. My hosting provider believes that the IP address to where the CURL requests are being sent is blocked by my hosting provider. Can you provide the IP address and the CURL endpoint URL so they can unblock it.
This is their message
Hello,
Thank you for the patience.
I was able to recreate the issue by using the provided steps. Please note that cURL is installed on the server:
root@node1376 [~]# curl -V
curl 7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.27.1 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
Protocols: tftp ftp telnet dict ldap ldaps http file https ftps scp sftp
Features: GSS-Negotiate IDN IPv6 Largefile NTLM SSL libzAlso the PHP extension is installed for all PHP versions on the server. You can also confirm the curl support on the following info file:
> https://staging.urbanartspace.co.uk/info.php
Based on the current error here:
> https://i.prntscr.com/XAk2eUSQQ0KAkG2goPht_A.png
I believe that the IP address to which this cURL request should be established is blocked on the server. Having this in mind, please contact this vendor and ask them for IP addresses used for their API connection. Also, if it is possible please provide the exact cURL request which is performing this extension, so we can test it manually on the server.
We are waiting for your update.
Kind Regards,
Oliver W.
Technical Support Team
FastComet Inc.Just a follow up, Mangopay support said there’s no restriction on the number of domains a production clientID and key can be linked in.
Forum: Plugins
In reply to: [MANGOPAY for WooCommerce] Mangopay WC Vendors – Fatal ErrorOh thank you so much for this! – Changed to d/m/Y and works!!
Forum: Plugins
In reply to: [MANGOPAY for WooCommerce] Mangopay WC Vendors – Fatal ErrorHi, sorry for the late reply – I have been in touch with the guys at Mangopay and have found a more detailed analysis of the cause.
So to answer your question, the problem I faced was in two places
1) On the vendor settings page – I saw the error that I have described above in (1) – This is the WC Vendors settings page from the shortcode – [wcv_shop_settings] – this is a snapshot of the page – https://prntscr.com/lkb2jn
It’s a frontend page2) Second error I got was when registering a new user either from the frontend /my-account endpoint OR the backend wp-admin/user-new.php
This is what Mangopay support told me –
I have had a look and the issue is not with the set up but the data being provided.
The initial issue is arising at the point of user creation.
You need a user to be created in order to link the bank account to.However at the moment the user creation is failing and so no ID for the user is being created.
Looking at what is causing the failure is the birthday.
The UNIX time stamp in one birthday request is -59330793600
This is not a valid timestamp.
So how the birthday choice is being handled on your platform is causing the error when a user is created.They asked me to do this and I tried and it worked!
Can you make a test and set the birthday to 12/12/1992.
Let me know once done so I can see if the user is successfully created.I believe that there is an issue with the way the birthday field is inserted by Mangopay plugin on the registration form – See this is the output of the date picker when I select 30th November – https://prntscr.com/lkb477
Forum: Plugins
In reply to: [WooCommerce] Restrict Woocommerce coupons by Custom TaxonomyThomas, thanks for your response. Can you suggest who could help me with the custom code – ready to take it up as a paid project.