Oops, not logged in, on most pages [resolved]

Community Help
1

On newest Chrome on Windows, I now get the ‘Oops, an unexpected error occurred.’ on most pages, including sometimes the home page. I think I am not logged in, at least this is what the page says. I found a reproducible pattern:

Visit ‘Community’ at the top bar
Always get the error, after flashing the actual page.
Visit observablehq.com home page
Get the error.
Visit ‘Product’
Get the actual page
Visit observablehq.com home page
Get the actual page
Visit ‘Community’ at the top bar
Always get the error, after flashing the actual page.

This does not happen on Firefox or Incognito, so perhaps some cookie, local/session storage issue. It persists between tabs.

Using Firefox now, hoping that the issue resolves itself.

2

Oh man! Sorry that’s happening. I can’t reproduce… hm. If something works Incognito but not in regular Chrome, it’s often due to a Chrome extension. Do you have anything that might be interfering with API requests, like a CORS blocker? You could try disabling extensions one by one (I know that could be a pain if you have a lot) and see if that resolves it.

1 Like
3

I do get CORS errors in the console, such as:

Access to XMLHttpRequest at 'https://www.google-analytics.com/j/collect?v=1&_v=j93&aip=1&a=2101744665&t=pageview&_s=1&dl=https%3A%2F%2Fobservablehq.com%2Fcommunity&dp=%2Fcommunity&ul=en-us&de=UTF-8&dt=Observable&sd=24-bit&sr=1920x1200&vp=1525x192&je=0&_u=SACAAEABEAAAAC~&jid=454186114&gjid=11708366&cid=1327001174.1629846746&tid=UA-112925870-1&_gid=1480459508.1629846746&_r=1&z=64949970' from origin 'https://observablehq.com' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.

Let me check the extensions although I do not have a CORS blocker.

4

Ok, it turns out I had a CORS related extension which I had tried and left enabled. Disabling it I think resolved the issue completely. Thanks for the quick response !

3 Likes
5

Glad that worked! And glad we’ve seen this a few times and now I know what to guess : )