Woozy Face
Forum Replies Created
-
Forum: Plugins
In reply to: [WP Fastest Cache - WordPress Cache Plugin] 500 error on first time visitYes it seems highly likely!
Forum: Plugins
In reply to: [WP Fastest Cache - WordPress Cache Plugin] 500 error on first time visitWould that help? Cause I didn’t clear anything but first time visitors are still getting this message.
Thanks!
Forum: Plugins
In reply to: [WP Fastest Cache - WordPress Cache Plugin] 500 error on first time visitWhat do you mean with you should not clear cache day?
Forum: Plugins
In reply to: [Content Visibility for Divi Builder] List of boolean expressionsOh I thought you had a list presented can you redo your title with a Request: at the beginning?! Otherwise it’ll confuse people Like me XD!
Forum: Fixing WordPress
In reply to: Use full API blocked?!Well I had some caching issues which resulted in a 404 for your browser chrome, at least thats what the logs say;
(changed the ip to anonymous *’s )
What you see is 2 different results depending on JP being activated.20 juni 2018, 18:29 https://easyvoicetelecom.nl/site/en/wc-api/_wc_gateway_ideal?order_id=2995&key=wc_order_5b1fdffc1bfa8
GET HTTP 400 Bad Request 2514 ms
177.*.*.*
177.*.*.*.static.host.gvt.net.brChrome on Linux
User agent
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.3620 juni 2018, 18:27
https://easyvoicetelecom.nl/site/en/wc-api/mollie_wc_gateway_ideal?order_id=2995&key=wc_order_5b1fdffc1bfa8
GET HTTP 401 Unauthorized 3761 ms
177.*.*.*
177.*.*.*.static.host.gvt.net.br Chrome on LinuxSo if some jetpack guru is around here please help me a little would u 🙂
Thanks
- This reply was modified 7 years, 12 months ago by Woozy Face.
Forum: Fixing WordPress
In reply to: Use full API blocked?!So im back I disabled all the plugins except WooCommerce and mollie and now it showing me a 404. Next thing I did was starting to activate each plugin one by one started with jetpack, then I tried to navigate to the wc-api page mentioned earlier and guess what. it throws a 401 again.
So to conclude it might be possible that jetpack is the issue, however I don’t use the security features of JP show how can it still affect this? And how can I fix this?
Thanks
Forum: Fixing WordPress
In reply to: Use full API blocked?!Okey but there are no settings for this kind of api in woo or mollie, also we only use them as payment provider. About your FYI line; this is what mollie says; statuscode 401 (Got HTTP/1.1 401 Unauthorized instead of 20x).
Now I’m going to eat some dinner and after that I will try it without the health checker, I’ll update u a.s.a.p.
Thank you
Forum: Fixing WordPress
In reply to: Use full API blocked?!Hi Mário,
Thanks for your response, I tried doing the health check and enabled only WooCommerce and Mollie. But still the same 401 error.
I also checked the webserver (the varnish cache handles the URL fine and doesn’t break it, but keeps it intact).
the webserver itself doesn’t give a 401 error code but the site is. Why the site does this is something I can’t seem to figure out; Could it might be that the key doesn’t exist?Thank you!
- This reply was modified 7 years, 12 months ago by Woozy Face.
Forum: Fixing WordPress
In reply to: Use full API blocked?!Well the issue is, that the api of my payment provider gets blocked so they can’t tell WooCommerce and the subscriptions plugin that a payment has been received if it’s a direct debit. it just throws an 401 back!
statuscode 401 (Got HTTP/1.1 401 Unauthorized instead of 20x)Forum: Fixing WordPress
In reply to: Use full API blocked?!Which plugin are u talking about? If Cerber, no it doesn’t work if disabled.
Forum: Fixing WordPress
In reply to: Use full API blocked?!What do you mean? Please be more specific. the developers of cerber told me that it is not their plugin which is blocking the api’s. So the question now is where does the blocking come from?
strange what can it be?
I’m aware of that page, didn’t had any effect.
with G crawler It just say something like “looking for vulnerable php code” and with our payment provider it throws 401 errors.
The conflict occurred when some one wanted to show their woo subscriptions, auto url completion was redirecting to the mailpoet subscription settings..