Does the google page speed tool work for anyone on v5 cloud hosted environment? I think there are major issues with the current cloudflare setup and google access.

At the end of the pagespeed report it says:

Oops! Something went wrong.

extensible_stubs::UNABLE_TO_RETRY: A retriable error could not be retried due to Extensible Stubs memory limits for streams (see go/xs-retries-memory-limit-reached). Original error: RPC::UNREACHABLE: sending stream message: write tcp [2002:a05:6638:46d1:b0:4f2:201e:fd79]:35188->[2002:a05:6902:4682:b0:e63:4eee:f5e3]:14001: write: connection reset by peer

It fails for me for any url, both for mobile and desktop. Previously, I reported that the adsense preview tool, adsense auto ads on mobile devices also do not work with invision 5 cloud hosted environment.

Edited March 12Mar 12 by virap1

Now I did 2 tests on your site - main domain and one article. Test for me no issue.

See tests

1. domain

2. article

I ran a few topic URLs and they processed fine. Is this still an issue for you?

Thank you for checking.

Yes, it fails for me with error message: Core Web Vitals Assessment: Failed

 

Yes, it fails for me with error message: Core Web Vitals Assessment: Failed

Keep in mind that doesn't mean the test failed to run but rather the Core Web Vitals were not to Google's liking.

That is really concerning. Very poor performance of mobile especially. I know this was mentioned by others even before the official release of v5.

and I just got the same error again: Oops! Something went wrong.

extensible_stubs::UNABLE_TO_RETRY: A retriable error could not be retried due to Extensible Stubs memory limits for streams (see go/xs-retries-memory-limit-reached). Original error: RPC::UNREACHABLE: sending stream message: write tcp [2002:a05:6638:46d1:b0:4f2:201e:fd79]:35860->[2002:a05:6902:4682:b0:e63:4eee:f5e3]:14001: write: connection reset by peer

Core Web Vitals are not just the software performance but rather everything that is on the page and getting loaded. From advertisements to custom JavaScript to third party applications to large images, etc... You will want to review the results to see what is impacting your community. You can compare it to here where this very topic passed running the same software and cloud servers: https://pagespeed.web.dev/analysis/https-invisioncommunity-com-forums-topic-482136-google-pagespeed-fails/0uiveq87ln?form_factor=mobile

 

That is really concerning. Very poor performance of mobile especially. I know this was mentioned by others even before the official release of v5.

and I just got the same error again: Oops! Something went wrong.

extensible_stubs::UNABLE_TO_RETRY: A retriable error could not be retried due to Extensible Stubs memory limits for streams (see go/xs-retries-memory-limit-reached). Original error: RPC::UNREACHABLE: sending stream message: write tcp [2002:a05:6638:46d1:b0:4f2:201e:fd79]:35860->[2002:a05:6902:4682:b0:e63:4eee:f5e3]:14001: write: connection reset by peer

There are too many issues in your article pages. See test with dev tool chrome browser

Thanks. I will check.

The issues appearing in the chrom dev tools are all related to manually placed google ads code.

Is the cloudflare rocket loader enabled? if so, can it be disabled for our account?

can we for testing disable the cloudflare for our account altogether?

Is there a way to migrate back to invision 4? if not, is there a way to migrate from cloud hosted to self hosted?

Whatever is the cause v5 does not work for me at all. There was an immediate drop in adsense earning following the upgrade and I am unable to find a solution to this. So willing to do whatever it takes to get this fixed.

 

Is the cloudflare rocket loader enabled? if so, can it be disabled for our account?

can we for testing disable the cloudflare for our account altogether?

We do not allow disabling of items in CloudFlare as it operates as part of our infrastructure. We do not enable RocketLoader.

 

Is there a way to migrate back to invision 4? if not, is there a way to migrate from cloud hosted to self hosted?

No matter if you're on Cloud or self-hosted, the only way to return to version 4 would be to restore a backup from when you were on version 4. We do not recommend doing so as you will lose content/data/etc...

 

There was an immediate drop in adsense earning following the upgrade

You'll want to contact them regarding that to figure out what the issue is here. Without knowing what the issue is, it is hard to say whether or not version 5 is the issue. It could merely be a coincidence and making changes might worsen the decline and/or cause headaches for you and your members for potentially no gain.

If I change my user agent to Mediapartners-Google which is what adsense uses then I immediately get stoped by cloudflare. It repeatedly prompts to verify I am human but would not let me pas that check.

Could we whitelist Mediapartners-Google in cloudflare.

Thanks.

 

If I change my user agent to Mediapartners-Google which is what adsense uses then I immediately get stoped by cloudflare. It repeatedly prompts to verify I am human but would not let me pas that check.

Could we whitelist Mediapartners-Google in cloudflare.

Thanks.

This is likely due to you are not part of the IP range which is a valid Google bot. There are a lot of algorithms which innately go into CloudFlare that we follow to block suspicious or automated traffic that is not good. We do allow good bots, like all variations of Google.

Thank you. Yes, that might be case.

When I inspect a url such as this https://www.enotalone.com/article/relationships/regain-control-in-your-relationship-r24117/

I see that some of the adsense resources like adtrafficquality.google/pagead/sodar are failing with a message err_blocked_by_orb.

Is there anything we can do to fix this on our end?

Could any settings in cloudflare or in admin cp for things like "Content-Security-Policy HTTP header" be causing this?

Thank you.

Unfortunately, I am not seeing this in the browser console. This makes sense though as this error is typically on the browser side of things. Such as privacy restrictions, third party cookie blocks, ad blockers, browser extensions for privacy, etc...

We do not set a CSP header which would stop this.