Viewing 15 replies - 1 through 15 (of 17 total)
  • Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    If that plugin is blocking access to the API, find another.

    Thread Starter Woozy Face

    (@shaady4)

    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?

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    Does your code/access to the API work if that plugin is disabled?

    Thread Starter Woozy Face

    (@shaady4)

    Which plugin are u talking about? If Cerber, no it doesn’t work if disabled.

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    OK< then never mind.

    Rather than referring to another post, please restate the original problem. (This is why we ask that folks not create duplicate topics.)

    Thread Starter Woozy Face

    (@shaady4)

    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)

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    Firewall, perhaps?

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    @shaady4, DO NOT EVER call me again. That is a violation of forum rules. We are done. You have abused your privileges here with me.

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    Please don’t offer to send or post logon credentials on these forums:

    https://make.wordpress.org/support/handbook/forum-welcome/#the-bad-stuff

    Hi Shaady4, how are you?

    First of all I recommend to read the Forum Welcome page.
    So we can find a answer to your problem without another problems.

    About your problem: let’s try to find what is blocking your requests.

    Attempt to disable all plugins, and use one of the default (Twenty*) themes. If the problem goes away, enable them one by one to identify the source of your troubles. If the problem persist something else is blocking you: please contact your host support.

    You can use the Health Check plugin for that: just install and go to troubleshooting tab. There you can click the button to disable all plugins and change the theme for you, while you’re still logged in, without affecting normal visitors to your site.

    Thread Starter Woozy Face

    (@shaady4)

    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.

    https://easyvoicetelecom.nl/site/wc-api/mollie_wc_gateway_ideal/?order_id=2995&key=wc_order_5b1fdffc1bfa8

    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 5 years, 10 months ago by Woozy Face.

    Well… If it’s happening with only Woo and Mollie activated, maybe it’s a Mollie issue (or some setting from Mollie/Woo).

    First of all: did you tested with WooCommerce standard theme?
    If not, try it before.

    If yes, continue:

    Can you try another payment gateway?
    This error happens in any other endpoint?

    FYI: this URL give me 400 (Bad Request) not 401.

    I’m figuring a new point now: maybe the request is not considering troubleshoot method. So, please, can you retest deactivating all the plugins and activating the standard theme without using the Health Checker?

    Do not forget to do a backup before anytest and to refresh permalinks and server caches after do this.

    Thanks

    Thread Starter Woozy Face

    (@shaady4)

    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

    Thread Starter Woozy Face

    (@shaady4)

    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

Viewing 15 replies - 1 through 15 (of 17 total)
  • The topic ‘Use full API blocked?!’ is closed to new replies.