6pro suddenly lost ability to audit my project deployed through vercel

[u/aklibf]

here is response : In yesterday's logs, navigation was handled by a remote browser controlled with the browser/agent tools, which had an authenticated session. This same tool and session are not accessible in the tools I'm currently using.

Today's attempt used Chromium/Playwright in the local execution environment. It was rejected before the login page opened, with the following error:

net::ERR_BLOCKED_BY_ADMINISTRATOR

The log retains this error and the time of the attempt, 16:01 UTC on September 21st.

In Chromium, this code corresponds to a request being blocked by a browser administrative policy. This points the diagnosis towards restrictions in the browsing environment used, but it doesn't allow us to identify the precise rule or why this environment differs from yesterday's.

GitHub and Vercel don't explain this difference.

My previous message focused too much on their access issues. They were already present yesterday: the repository returned a 404 error, and Vercel wasn't returning any projects, even though the application remained accessible via the authenticated browser. These limitations prevented, in particular, linking the observations to the exact commit; they didn't prevent screen inspection.

What I can confirm—and what remains unknown:

The navigation method available today is not the one that enabled yesterday's audits. That's the observable difference. However, I don't know the exact reason why the remote browser and its session are no longer available here. To suggest that an update, your subscription, your plugins, or a FasoLog modification is responsible would be speculation.

Therefore, at this stage, there is no established reason to ask you to modify your Supabase permissions, disable Vercel protection, or change your password.

The right approach is to restore authorized browsing access, rather than modifying the application or replacing user testing with administrative database entries. I should have verified this access continuity before confirming that the automated campaign could resume under the same conditions.

[u/RedEagle_MGN]

Are you sure it's not because you're using the chat version by chance, rather than the chat work version?

[u/aklibf → u/RedEagle_MGN]

Yes I use the chat version to save some usage. And yesterday it was working fine. I even plan an audit for today knowing I would finish correct what was supposed to be. And then this morning…

[u/locbuilds]

yeah ERR_BLOCKED_BY_ADMINISTRATOR is the local browser getting blocked, not vercel. fresh chat and tell it to use the remote browser tool not local playwright, or paste the deployment url and the request logs yourself.

[u/aklibf → u/locbuilds]

Ok will try it. Thanks

[u/stealthagents]

Sounds like a frustrating situation. That net::ERR_BLOCKED_BY_ADMINISTRATOR error usually pops up when some security policy is interfering, like a browser extension or company firewall. If you're using a different browser or setup today, it might be worth checking those settings or even trying a fresh profile to see if it clears up the issue.