Kawbet agents sign up,11okada vip apk.Recharge Every day and Get Bonus up-to 50%!

Resolved PhilipPeake
(@philippeake)

3 years, 8 months ago

In order to check that my site is working in remote locations, I have VPNs (using WireGuard) to AWS hosts in the US, UK and France.

When the VPN is active, images don’t load (unless already cached in the browser).
The request to the WP servers receives a 400 response. I am guessing that AWS IPs as clients are “blacklisted” by the WP servers. If so, that really needs to be mentioned.

So, turn off Jetpack image performance enhancement, which as I understand it, is supposed to revert to requesting images directly from my server.

However, when I try to load (via a VPN), I still get:

(index):95 GET https://i1.wp.com/photo.vogon.net/wp-content/uploads/2021/03/1973445_10153038966243889_1101334806930711216_o_10153038966243889.jpg?strip=info&w=1363&ssl=1 400
(index):95 GET https://i0.wp.com/photo.vogon.net/wp-content/uploads/2021/03/10295247_10153038965508889_1788102948936406709_o_10153038965508889.jpg?strip=info&w=1379&ssl=1 400
(index):95 GET https://i1.wp.com/photo.vogon.net/wp-content/uploads/2021/03/10498440_10153038965048889_6739463768070129495_o_10153038965048889.jpg?strip=info&w=1340&ssl=1 400
(index):95 GET https://i1.wp.com/photo.vogon.net/wp-content/uploads/2021/03/11016104_10153038965488889_7960815999632756797_o_10153038965488889.jpg?strip=info&w=1367&ssl=1 400
(index):95 GET https://i0.wp.com/photo.vogon.net/wp-content/uploads/2021/03/11049488_10153038965498889_2868305847034317328_o_10153038965498889.jpg?strip=info&w=1355&ssl=1 400
(index):95 GET https://i1.wp.com/photo.vogon.net/wp-content/uploads/2021/03/10865810_10153038966438889_4077546770117943104_o_10153038966438889.jpg?strip=info&w=1500&ssl=1 400
(index):95 GET https://i2.wp.com/photo.vogon.net/wp-content/uploads/2021/03/10857198_10153038966588889_2652310119031967696_o_10153038966588889.jpg?strip=info&w=1367&ssl=1 400
(index):95 GET https://i0.wp.com/photo.vogon.net/wp-content/uploads/2021/03/10498570_10153038966778889_1835265228853923933_o_10153038966778889.jpg?strip=info&w=1367&ssl=1 400
(index):95 GET https://i1.wp.com/photo.vogon.net/wp-content/uploads/2021/03/10911403_10153038965923889_3540558918754229952_o_10153038965923889.jpg?strip=info&w=1370&ssl=1 400
(index):95 GET https://i2.wp.com/photo.vogon.net/wp-content/uploads/2021/03/10991624_10153038965078889_2252711911010035238_o_10153038965078889.jpg?strip=info&w=1366&ssl=1 400
(index):95 GET https://i2.wp.com/photo.vogon.net/wp-content/uploads/2021/03/11002670_10153038966813889_6427634991625579892_o_10153038966813889.jpg?strip=info&w=1375&ssl=1 400
(index):95 GET https://i1.wp.com/photo.vogon.net/wp-content/uploads/2021/03/10633592_10153038966363889_3310403143097497532_o_10153038966363889.jpg?strip=info&w=1384&ssl=1 400
(index):95 GET https://i1.wp.com/photo.vogon.net/wp-content/uploads/2021/03/11073053_10153038965273889_7884924090862283475_o_10153038965273889.jpg?strip=info&w=1372&ssl=1 400
(index):95 GET https://i0.wp.com/photo.vogon.net/wp-content/uploads/2021/03/11061257_10153038966623889_8282242656434731141_o_10153038966623889.jpg?strip=info&w=1372&ssl=1 400
(index):95 GET https://i1.wp.com/photo.vogon.net/wp-content/uploads/2021/03/11080498_10153038966803889_68381482583551829_o_10153038966803889.jpg?strip=info&w=1375&ssl=1 400
(index):95 GET https://i0.wp.com/photo.vogon.net/wp-content/uploads/2021/03/11082237_10153038965228889_2334588689614285971_o_10153038965228889.jpg?strip=info&w=1358&ssl=1 400
(index):95 GET https://i1.wp.com/photo.vogon.net/wp-content/uploads/2021/03/11103134_10153038965918889_3453436209254631531_o_10153038965918889.jpg?strip=info&w=1391&ssl=1 400
(index):95 GET https://i0.wp.com/photo.vogon.net/wp-content/uploads/2021/03/11083992_10153038966143889_11580292692362264_o_10153038966143889.jpg?strip=info&w=1367&ssl=1 400

Any ideas why I am still hitting WP servers?
And more importantly, how to stop this happening?

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

jakehhcls
(@jakehhcls)

3 years, 8 months ago

I have the same issue. Looking forward to fixing this

Thread Starter PhilipPeake
(@philippeake)

3 years, 8 months ago

Site URL: https://photo.vogon.net

Plugin Contributor Karen Attfield
(@wpkaren)

3 years, 8 months ago

Hi @philippeake ,

If you are using the Tiled Gallery Block to add a gallery, by default the images will be served via the Jetpack Image CDN. However it is possible to avoid this by adding a Tiled Gallery using the Classic Block (or using the Classic Editor plugin).

To do this you would use the ‘Add Media’ button from the Classic Editor and add a gallery and select Tiled Gallery following the steps here:

https://jetpack.com/support/tiled-galleries/

You can also double check that Tiled Galleries are active and the Image CDN deactivated following the link on this page:

https://jetpack.com/support/control-jetpack-features-on-one-page/

This should then work. It is a bit of a workaround and our support documentation isn’t particularly clear about this so we’ll make sure to clarify the steps as soon as possible. Could you let us know if this works for your gallery?

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

The topic ‘Jetpack image caching still working after turning off’ is closed to new replies.