VR shortcode shows an error after it quits trying to load.

[csabarakasz]

Impacted plugin

Jetpack

Quick summary

The user reported that the VR block stopped working on their site, which I was able to replicate. As matter a fact, it gives me an error on our own Embedding 360° Photos and Virtual Reality (VR) Content page:

The image is there: https://en-support.files.wordpress.com/2016/12/vr-shortcode-360.jpg but the VR code fails to load: https://vr.me.sh/view/?view=360&url=https://en-support.files.wordpress.com/2016/12/vr-shortcode-360.jpg

Console return this error:

with We cannot complete this request, remote server returned an unexpected status code (400)

User report: 6663821-zd-a8c

From what I was able to understand, Jetpack CDN gives up the loading process.

Steps to reproduce

Upload a VR image, include the shortcode and visit the live site.

Or visit: https://wordpress.com/support/embedding-360-photos-and-virtual-reality-vr-content/

In some cases, uploading a smaller version of the image helped. But it used to work before with the larger image as well (User feedback.)

A clear and concise description of what you expected to happen.

No response

What actually happened

No response

Impact

One

Available workarounds?

No and the platform is unusable

Platform (Simple and/or Atomic)

Simple

Logs or notes

Chrome: Version 116.0.5845.110 (Official Build) (arm64) Replicated in Firefox 117.0 (64-bit) and Safari (Version 16.5) as well

[github-actions[bot]]

Support References

This comment is automatically generated. Please do not edit it.

• [ ] 6663821-zen

[cuemarie]

Quick note on

Or visit: https://wordpress.com/support/embedding-360-photos-and-virtual-reality-vr-content/

This support doc shows the 360 images without issue for me, in Firefox 117.0 (64-bit) (latest version).

Will test further across browsers, but lowering priority for the moment.

[cuemarie]

📌 REPRODUCTION RESULTS

• Tested on https://wordpress.com/support/embedding-360-photos-and-virtual-reality-vr-content/ – Could Not Replicate
• Tested on Customer's Site – Could Not Replicate

📌 FINDINGS/SCREENSHOTS/VIDEO I'm unable to replicate this issue so far; wondering if this hasn't been resolved already.

Screenshot of guide doc behavior is in previous comment; shared a recording of what I'm seeing on the customer's site here: p1693521870436529/1692694623.999249-slack-CBG1CP4EN

📌 ACTIONS

• Requested author feedback

📌 Message to Author @csabarakasz can you retest and let me know if you're still able to replicate this as you were before?

[csabarakasz]

@cuemarie Interestingly, the error seems to be country-connected. When I tested again from my end, I could replicate all the issues mentioned before on the user's site or the Support doc.

Then I tried with VPN, using USA servers, and the issue went away. Unusual.

Since I can replicate this issue on multiple sites, I wonder if this is somehow Jetpack/country-specific.

Here is my recording: p1693748465463109/1692694623.999249-slack-CBG1CP4EN

[jeherve]

This is most likely happening because the original image is quite big (17.2Mb): https://en-support.files.wordpress.com/2016/12/vr-shortcode-360.jpg

Our CDN most likely failed to download the image at some point, and some of us see a broken image as a result, depending on which node of the CDN we're hitting.

I have now nuked the cache for that image, allowing the CDN to try to download a new copy for all its nodes. Hopefully it will help!

[github-actions[bot]]

This issue has been marked as stale. This happened because:

• It has been inactive for the past 6 months.
• It hasn’t been labeled `[Pri] BLOCKER`, `[Pri] High`, `[Type] Feature Request`, `[Type] Enhancement`, `[Type] Janitorial`, `Good For Community`, `[Type] Good First Bug`, etc.

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.

[davemart-in]

This seems edge case and there has been no movement in over a year, so I'm closing the issue.