serloo
Forum Replies Created
-
Thank you
Here is the part of log, hide some infomation with xxx111:
Response Body: {“name”:”INVALID_REQUEST”,”message”:”Request is not well-formed, syntactically incorrect, or violates schema.”,”debug_id”:”0d9918f719d99″,”details”:[{“field”:”/purchase_units/@reference_id==’default’/items/0/name”,”value”:”International Standard Shipping (to xx) of Lxxxxxxxx Pxxxxxx Sxxxxx Axxxx Mxxxxx with Lxx – Pxxxxxx Rxxxx Sxxxxx – Fxxxx Sxxxxx #111111″,”location”:”body”,”issue”:”INVALID_STRING_LENGTH”,”description”:”The value of a field is either too short or too long.”}],”links”:[{“href”:”https://developer.paypal.com/docs/api/orders/v2/#error-INVALID_STRING_LENGTH”,”rel”:”information_link”,”encType”:”application/json”}]}
Thank you for your reply.
No emoji in the fee item
Yeah, 127 is the limit of paypal, but another plugin–Payment Plugins for PayPal WooCommerce we used and there’s no 127 limit, maybe you can check what they did, we are not familar with that.
I guess they cut the fee item with first 127 characters and send it to paypal.
Forum: Plugins
In reply to: [Stock Sync for WooCommerce] RestAPI is not accessibleThe issue has fixed after changing the permalinks to post name in wordpress settings.
It is not related to cloudflare or hosting.
Forum: Plugins
In reply to: [Stock Sync for WooCommerce] RestAPI is not accessibleThis is the server error log:
[error] 1929#1929: *646 FastCGI sent in stderr: “PHP message: PHP Warning: Attempt to read property “order_awaiting_payment” on null in /www/test2r_482/public/wp-content/plugins/woocommerce/includes/wc-cart-functions.php on line 185″ while reading response header from upstream, client: 35.187.247.7, server: turtle.asia, request: “GET /wp-json/wc/v2/?consumer_key=invalid&consumer_secret=invalid HTTP/2.0”, upstream: “fastcgi://unix:/var/run/php8.1-fpm-test2r.sock:”, host: “turtle.asia:55616”
Forum: Plugins
In reply to: [Stock Sync for WooCommerce] RestAPI is not accessibleHere is the reply from hosting provider, could you help to check?
———————
So far, we’ve ruled out the server / LXD or container issue (by getting both 2 sites on the same location/LXD).
And as per the access.log real time review (while you did the action) I didn’t see any blocking requests there (and there’s no CF RAY ID either as per your screenshot).
I would suggest to report this issue to the plugin’s support team.
————————
Forum: Plugins
In reply to: [Stock Sync for WooCommerce] RestAPI is not accessibleDebugging response shows as below:
Response code 200
Headers
date Wed, 10 Jan 2024 01:37:39 GMT
content-type text/html; charset=UTF-8
cf-cache-status DYNAMIC
link <https://serloo.cloud/index.php?rest_route=/>; rel=”https://api.w.org/”
vary Accept-Encoding
ki-cache-type None
ki-cf-cache-status BYPASS
ki-edge v=20.2.5;mv=3.0.1
ki-edge-o2o yes
ki-origin g1p
x-content-type-options nosniff
x-edge-location-klb 1
x-kinsta-cache BYPASS
report-to {“endpoints”:[{“url”:”https:\/\/a.nel.cloudflare.com\/report\/v3?s=2GzmOgfOz6odhUGTopPoomxlYNmA0lgsaxAeJaCAhdWNfxy11EEb4XWbaepBqE8i%2Fsj0ApmuXQ4ZxFLv6O5mcSn6WoNhULq%2FsxHt9UKgZsQufDuQFXnOCTtDybEKaw%3D%3D”}],”group”:”cf-nel”,”max_age”:604800}
nel {“success_fraction”:0.01,”report_to”:”cf-nel”,”max_age”:604800}
server cloudflare
cf-ray 8431322d2fe910aa-HKG
alt-svc h3=”:443″; ma=86400
Response body: too long, how to upload a file?