Cannot open my notes

[VasilyB 0]

Greetings, I get oops when I try to open my notes. The button contact support from the screen fails also.
I have a lot of CORS errors in web browser console:
Failed to load resource: the server responded with a status of 500 (Internal Server Error)
IonCe.action:1

Refused to frame 'https://evernote.com/' because it violates the following Content Security Policy directive: "default-src 'self' data: blob: *.evernote.com *.google.com *.googleapis.com *.google-analytics.com *.gstatic.com *.doubleclick.net *.appspot.com *.qualtrics.com *.m-stable.test.enops.net *.m-stable.dev.enops.net www.datadoghq-browser-agent.com browser-http-intake.logs.datadoghq.com api.iterable.com". Note that 'frame-src' was not explicitly set, so 'default-src' is used as a fallback.

DOMException: Blocked a frame with origin "https://www.evernote.com" from accessing a cross-origin frame.
    at https://cdn1.evernote.com/ion/dist/main/6469.3080212e0183277447d7.js:2:1724979
    at Pl (https://cdn1.evernote.com/ion/dist/main/7882.1b91f768e981468d93a4.js:2:4668687)
    at t.unstable_runWithPriority (https://cdn1.evernote.com/ion/dist/main/7882.1b91f768e981468d93a4.js:2:5158520)
    at Gi (https://cdn1.evernote.com/ion/dist/main/7882.1b91f768e981468d93a4.js:2:4609189)
    at Dl (https://cdn1.evernote.com/ion/dist/main/7882.1b91f768e981468d93a4.js:2:4668150)
    at gl (https://cdn1.evernote.com/ion/dist/main/7882.1b91f768e981468d93a4.js:2:4659645)
    at https://cdn1.evernote.com/ion/dist/main/7882.1b91f768e981468d93a4.js:2:4609412
    at t.unstable_runWithPriority (https://cdn1.evernote.com/ion/dist/main/7882.1b91f768e981468d93a4.js:2:5158520)
    at Gi (https://cdn1.evernote.com/ion/dist/main/7882.1b91f768e981468d93a4.js:2:4609189)
    at Yi (https://cdn1.evernote.com/ion/dist/main/7882.1b91f768e981468d93a4.js:2:4609357)
I'm using Google Chrome Version 93.0.4577.82 (Official Build) (64-bit)

How to fix the problem?

[Austin G 527]

Hello @VasilyB. Thanks for this report. We're looking into this now. We've just made some adjustments on our end that may fix this. Please confirm if the issue continues. Thanks.