Walter T.

Hi everybody,

The problem is now solved, it was a firewall issue. I talked with the support and they solve the issue ASAP. Everything is now working fine.

Thanks to all of you that helped me to find the culprit.

Best regards

Hi,

thanks for the feedback.
I’m waiting for the support response, They acknowledged the question but no answer so far.

I installed the WP-Staging, just add /woocommercedebug after the domain to enter the staging site with the request configurations.
Spoiler alert, 403 is still there https://prnt.sc/0BZY-ztE79xM

Thank you for the help, hope we can manage to fix this problem.

Greats

Hi Shameem,

Thank you for your answer.

1&2. I’ve seen this solution in another thread and tested it before and tested it now again. 403 is still there.

3. I’ll email the support asking for some help. The ?get_refreshed_fragments request works fine. so it doesn’t look like a problem here, anyway, I’ll take a look with them.

4. I tested the cart with only WooCommerce and a basic theme without any positive results. I’m unsure about any FW or IP blocking software, but I’ll also check support.

Another appointment that I was told to check, is to try to access the URL out of context, so I tested with postman, GET and POST methods, the results were the same, -1 in the body with a 403 code.

Thank you for the help.

• This reply was modified 1 year ago by Walter T..

Hi ckadenge,

thank you for your help.

Here’s the gist: https://gist.github.com/walter-tavares/6dd769aea7d0a62b46bc6ab1a2fe36c5

Hi ckadenge,

Thank you for the response.

Yes, I indeed tested with the themes Twenty Twenty-Four, Storefront, and Unero – the current theme.
At the time I only had the WooCommerce plugin active and the 403 was and still happens.

Great, thanks a lot.

Hi,

Thanks for your help and feedback, it’s seems ok now. I had a log every 5 minutes and none since 08:56 (server time):

[21/Aug/2015:08:31:51 +0000] "HEAD / HTTP/1.1" 200 - "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)
[21/Aug/2015:08:36:39 +0000] "HEAD / HTTP/1.1" 200 - "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)
[21/Aug/2015:08:41:45 +0000] "HEAD / HTTP/1.1" 200 - "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)
[21/Aug/2015:08:46:47 +0000] "HEAD / HTTP/1.1" 200 - "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)
[21/Aug/2015:08:51:39 +0000] "HEAD / HTTP/1.1" 200 - "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)
[21/Aug/2015:08:56:40 +0000] "HEAD / HTTP/1.1" 200 - "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)

Can I use the Jetpack plugin without the monitor feature now? Can I now activate/deactivate the monitor feature?

Greats,
thanks a lot

Hi,

Have you anything new to me? I still have downtime cause the dynos can’t rest.

Greats

No matter what Jeremy, is it possible to manually stop the monitoring for my sites?
I still have accesses and it’s killing me.

Greats

Hi Jeremy,

I already done that. I did each of this actions but I still receiving logs from the Jetpack Site Uptime Monitor. Right now I don’t have the plugin installed, and the site aren’t linked to my wordpress account, but they still be monitored by the plugin. Can you remove manually my site from the monitoring task?
The url are:
https://www.comeebebe.com
https://www.waltertavares.pt

Greats,
/wt