Hronak Nahar's Replies

Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)

Forum: Plugins
In reply to: [Google for WooCommerce] 504 Gateway Timeout due to update_products/process_item job
Thread Starter Hronak Nahar
(@hronak)

7 months, 3 weeks ago
It happened again today. We ran PING for api.woocommerce.com the moment our admin panel went down and here are the results:
```
$ ping api.woocommerce.com
PING api.woocommerce.com (192.0.96.246) 56(84) bytes of data.
64 bytes from 192.0.96.246: icmp_seq=1 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=5 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=10 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=12 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=39 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=42 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=43 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=46 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=48 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=49 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=50 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=51 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=52 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=55 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=59 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=61 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=66 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=68 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=70 ttl=48 time=266 ms
64 bytes from 192.0.96.246: icmp_seq=75 ttl=48 time=266 ms
^C
--- api.woocommerce.com ping statistics ---
75 packets transmitted, 20 received, 73.3333% packet loss, time 75554ms
rtt min/avg/max/mdev = 266.100/266.168/266.289/0.050 ms
```
73% packet loss. There’s definitely something going on with api.woocommerce.com. I would love if WooCommerce Site Reliability team can respond here.

Moreover, when wp-cron & action scheduler jobs are run via WP-CLI, IT SHOULDN’T BE TAKING DOWN THE FRONTEND. THAT’S WHAT I’VE BEEN TRYING TO MAKE YOU GUYS UNDERSTAND.

A related issue was posted in Dec, 2023 – https://ww.wp.xz.cn/support/topic/product-feed-in-wordpress-admin-will-not-load/
Forum: Plugins
In reply to: [Google for WooCommerce] 504 Gateway Timeout due to update_products/process_item job

Thread Starter Hronak Nahar
(@hronak)

8 months ago

Hey,

Sorry to say that it’s not related to server resource limit. The error is happening randomly since yesterday as mentioned earlier. It was working perfectly all this long. We’ve tried pinging api.woocommerce.com while this error happened on the same machine, it didn’t respond to ping as well. So clearly the endpoint was down it seems.

Our support request is about the ‘cURL error 28’ on api.woocommerce.com taking down the WordPress admin panel. It shouldn’t be happening because those requests are executed in cron jobs from WP-CLI using system cron. Yesterday, admin panel of all our client’s sites with this plugin (Google for WooCommerce) were down due to this error. By down, I mean it kept on loading and them returned 504 gateway timeout.

Can you replicate it on your end by manually triggering timeout and see if takes down the whole WordPress admin panel?

Forum: Plugins
In reply to: [Google for WooCommerce] 504 Gateway Timeout due to update_products/process_item job

Thread Starter Hronak Nahar
(@hronak)

8 months ago

Hi,

Thank you for taking time to reply. Here’s the WooCommerce System Status Report of one of the affected site: https://pastebin.com/UcgcxL7J (expires in 1 day).

Note: Some identifying information like site URL and database prefixes were replaced with the text “[REDACTED]”.

Forum: Plugins
In reply to: [Shiprocket] Access Token Changed Without Backward Compatibility

Thread Starter Hronak Nahar
(@hronak)

3 years, 4 months ago

Hey Abhinav! If you’re still running old version of Shiprocket plugin, try updating the SHIPROCKET_ACCESS_TOKEN value in your Shiprocket plugin manually to source_wc_app_2022 in the file wp-content/plugins/shiprocket/shiprocket-woocommerce-shipping-calculator.php (line number 77).

The change should look like
From:
define( 'SHIPROCKET_ACCESS_TOKEN', '32e1024fc4e127f4d81a98c8a51cd1f4330b590f490de76380dd872426d564cc' );
To:
define( 'SHIPROCKET_ACCESS_TOKEN', 'source_wc_app_2022' );

If you don’t see this file, you probably updated the plugin to a more recent version.

Disclaimer: I run a modified Shiprocket plugin on my clients’ website for added features. Their recent update completely broke the live rates & shipping feature on our client website, due to which they lost 12 hours of sales.

Shiprocket changed this without even notifying users of this change, neither keeping any backward compatibility on the server side for old access token. Can’t trust Shiprocket anymore. I actually sent an email to Shiprocket trying to offer help when their plugin was under review asking if I could fix the issues and update the plugin’s coding standard. No response even after multiple follow-ups.

Hope this helps you in restoring your website. Let me know if you need any help. Shiprocket won’t come to help but we as a community can help each other.

Viewing 4 replies - 1 through 4 (of 4 total)