Jump to content
  • 0

I keep getting error saying "the content is blocked"


RaptorlJesus
 Share

Question

12 answers to this question

Recommended Posts

  • 0
  • Members
3 minutes ago, Vevrok said:

Hello,

are you using any adblock? if you're using then disable it.

also you can clear cache of browser if you are not using any adblock.

 

let us know if the issue has been resolved.

I don't use adblock- this literally happened out of nowhere, one day was working, the other, I start getting this

Edited by RaptorlJesus
Link to comment
Share on other sites

  • 0
  • Game Makers

Which browser are you using ?

 

Can you open the console (f12 or inspect element and then "console" tab) and take a screenshot (make sure no sensitive info are on it)

 

Did you try in incognito mode if you have the same?

 

Thanks.

Link to comment
Share on other sites

  • 0
  • Members
1 hour ago, SLOom said:

Which browser are you using ?

 

Can you open the console (f12 or inspect element and then "console" tab) and take a screenshot (make sure no sensitive info are on it)

 

Did you try in incognito mode if you have the same?

 

Thanks.

The same on : Chrome, Edge, IE, and Firefox

 

Inspecting elements as normal, they're just not finalising the loading.

 

Incognito mode doesn't change anything, additionally, in chrome, it doesn't even load the backgrounds https://imgur.com/62GAXPY

 

Additionally, chrome/firefox was like that from the start (from fresh windows install and all) and Edge became like it out of nowhere)

Edited by RaptorlJesus
Link to comment
Share on other sites

  • 0
  • Members
10 minutes ago, LaFleur said:

Hello @RaptorlJesus.

 

Please provide us a screenshot from the console as Sloom mentioned.

 

Also, do you run any program that may affect websites i.e. an antivirus with web safety?

https://imgur.com/9CIMsvM

 

Also, this is all the errors: 

 

Quote

[Intervention] Images loaded lazily and replaced with placeholders. Load events are deferred. See https://go.microsoft.com/fwlink/?linkid=2048113
/img/android-chrome-192x192.png:1 Failed to load resource: the server responded with a status of 404 ()
xat.com/:1 Error while trying to use the following icon from the Manifest: https://xat.com/img/android-chrome-192x192.png (Download error or resource isn't a valid image)
activity.js:1 !printErr=wasm streaming compile failed: TypeError: Failed to execute 'compile' on 'WebAssembly': Incorrect response MIME type. Expected 'application/wasm'.
printErr @ activity.js:1
activity.js:1 !printErr=falling back to ArrayBuffer instantiation
printErr @ activity.js:1
firebase.js:1 FBM:An error occurred while retrieving token.  FirebaseError: Messaging: The notification permission was not granted and blocked instead. (messaging/permission-blocked).
    at ot.<anonymous> (https://www.gstatic.com/firebasejs/8.0.1/firebase-messaging.js:1:35588)
    at https://www.gstatic.com/firebasejs/8.0.1/firebase-messaging.js:1:1982
    at Object.next (https://www.gstatic.com/firebasejs/8.0.1/firebase-messaging.js:1:2087)
    at https://www.gstatic.com/firebasejs/8.0.1/firebase-messaging.js:1:1028
    at new Promise (<anonymous>)
    at d (https://www.gstatic.com/firebasejs/8.0.1/firebase-messaging.js:1:779)
    at ot.getToken (https://www.gstatic.com/firebasejs/8.0.1/firebase-messaging.js:1:35341)
    at o (https://xat.com/content/web/R00030/box/www/firebase.js:1:663)
    at https://xat.com/content/web/R00030/box/www/firebase.js:1:1302
(anonymous) @ firebase.js:1
xat.com/:1 Notifications permission has been blocked as the user has ignored the permission prompt several times. This can be reset in Page Info which can be accessed by clicking the lock icon next to the URL. See https://permanently-removed.invalid/features/6443143280984064 for more information.
classic.html:10 Unrecognized Content-Security-Policy directive ''self''.

classic.html:10 Ignoring duplicate Content-Security-Policy directive 'style-src'.

classic.html:10 Ignoring duplicate Content-Security-Policy directive 'connect-src'.

classic.html:10 Ignoring duplicate Content-Security-Policy directive 'img-src'.

classic.html:10 Ignoring duplicate Content-Security-Policy directive 'script-src'.

classic.html:10 Ignoring duplicate Content-Security-Policy directive 'frame-src'.

6Refused to load the stylesheet '<URL>' because it violates the following Content Security Policy directive: "style-src <URL> <URL>". Note that 'style-src-elem' was not explicitly set, so 'style-src' is used as a fallback.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-Eujz25THcf/RDLzFD55VVJia2KtApz0Ff5n4DuFOAFQ='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-KpSV7LuPYEu58+3u9LJr9v5Drm0uIKEv0h3u/+NVNm8='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-KpSV7LuPYEu58+3u9LJr9v5Drm0uIKEv0h3u/+NVNm8='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-zEZIqeiEK8hyAhnB1wXUYVIUSe03t1gRFRGzhq90AnY='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-yPFwn47Bx8ehboIS6M/rAW3s8+mqlYEzkLggqEn84Qk='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-KMrRAXwXArl2uwbBNY20i3rbk4MbNo4A/w9sHSZg4i0='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-pIRjjCc/q6zgeBJY8UB5ZYVYVO6cNAMq+1BK54NP2Lo='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-1OjyRYLAOH1vhXLUN4bBHal0rWxuwBDBP220NNc0CNU='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-utOyE4A+ZtFA2MXLW/PpthQUCJ7EBfQyHyFHGysHyEs='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-ZIPXeud+Qvo8MVQVMUi4WP/gbNtP0/nrZ31uCJ5LtEs='), or a nonce ('nonce-...') is required to enable inline execution.

9Refused to apply inline style because it violates the following Content Security Policy directive: "style-src <URL> <URL>". Either the 'unsafe-inline' keyword, a hash ('sha256-oV3jdqk8GO/BUZSwos543OlGzhzxD3uMNE23EaxYMEQ='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-+VEOHwdF1AlCcC5CkDaldBfmUAas6ftCDlxe/bN5Fuw='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-kWo/6WnACRdZpKK99mW29rKRinT5wjUc/yhGOQzIvrc='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-MxPVpk9zaE74MzjM/1BT2qxcXp7WM4RJtHU2o1M1uZI='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-v7t3g4lVpmxaHAXSzy92dAKRAkpvZqtgBPY8lOjt8wg='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-i3m9j/c7qTmia2iS2xUKT2MPv95j66bg+3dkp02ZxHk='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-sJ3PDdl12BPZlSZNpRG6dkQxv91Q4SKRS26YdntGOfE='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-18gneVX8VHctlEL0BlOwLwL/PV4msRBgULFDccf1bf4='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-m3qGdr2uPckQWF6MMjHFOJqNjqYUzjFSBHAHllBHAXc='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-E0YVSR7rhfpxSkA+G8p7DcBkRrExMT+9M/cs63YdLeQ='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-1eK6brwxmES9qShZeGyexigvU4wgqkPtKHWSfTZwVA4='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-xMtQCr/7G9hvc1sk5HmAbiXFyfBoLPZKqDMKZBYZLM0='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-MJEjax+zVa9TGbwR+90bvPUkSfBNHxsqOVmsxMysAt8='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-5JZI7vfOBbIovdf7LhOUmMji/4h454d8+azD2MDI0bM='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-oAKat72gQh0xEY8QPGPzPQ+ieDKl82FmtTZ5dUZrwpQ='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-S2EjtHQnYzTRgKGpNt9lsO4O0ebMecBOx9/+Kw6G0fo='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-7b2FBG0UXfH13zY6oOKkXK0wm3JtgrF70hCn4Fye11c='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-jmTgAabwNSn6l3k2Pz7G8+VE9s5oWmm2YAQ0Yp75rQU='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-lQggU6rljXafMrtGr8nK3J+uniImlffypjN4ey2bdCc='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-+VEOHwdF1AlCcC5CkDaldBfmUAas6ftCDlxe/bN5Fuw='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-pIjw7Fj546gD/VGuzQaekqcMa+fVUFXywStJ2IN3sHo='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-2uVmxWMLyxmeGDb9V1oSi8RtugX1wcsG2j7cmJOpd70='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-FdZtU7hjhEwbjyWYQAPAOfwIMAFv4tvVnb6qcQhdgiI='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-B5RI203SvjAraw6/vTGfknYoqtyYQ1i4UsmGgzvz6d0='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-B5RI203SvjAraw6/vTGfknYoqtyYQ1i4UsmGgzvz6d0='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-i3m9j/c7qTmia2iS2xUKT2MPv95j66bg+3dkp02ZxHk='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-XRmGDeU3id5w1Xpp9bQMEc2T34x9fZk6fx929MqSJqA='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-EUDSCEAoSYfLbM7Ac4y6phD29gTYODlI16rcY1j88cw='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-Furkk4Lhm2ysKZWCcoDnwgIeDS1aUhVSK8N6qwuMeu8='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-Y9vEHLICLHy1TwLigXGDQAVlfTlmDUKdj+EUvPMUTj8='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-xMtQCr/7G9hvc1sk5HmAbiXFyfBoLPZKqDMKZBYZLM0='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-l/W8d8RFaJ7Ln0EQ5eQC47QwbVjJdFyZB5Ik5e45orA='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-htLbKgVXE8JncPoIQoZ0zXavxlj34boUQgS7hdLlezY='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-l/W8d8RFaJ7Ln0EQ5eQC47QwbVjJdFyZB5Ik5e45orA='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-WiyPcGA+DDDW4NXIiiotgwAhYJ67ouMvhdph73ChM74='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-eVSASXsrr+mQFC0DhraXBfCU/EFMSp22BzjuW2vuNRA='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-tskYP1u3QMMTnkt1sKP5qakiB2jR6hQq3sNqWFDtUXY='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-eVSASXsrr+mQFC0DhraXBfCU/EFMSp22BzjuW2vuNRA='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-F8OEy5/pXX4NJ6oQG75gvuJLtWrA9VwDPazBNnqeqjI='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-VXHnzW/xQLru+uTTXJudsi7lO0uRheeA0Zyfz/Gnpgo='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-SkXmi9K9w88T7cz2Un0jdN1+0q8eZsdBDTT+N5w9miA='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-SJ4yTfghWW4sLBv5fZnWYr1dcKEQGvAGGt9+YjqXjpA='), or a nonce ('nonce-...') is required to enable inline execution.

classic.html:10 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Either the 'unsafe-inline' keyword, a hash ('sha256-68t8GdqcvIIBWHbcG8ZlsUUhN/8isFuMo7CI53+xcSM='), or a nonce ('nonce-...') is required to enable inline execution.

about:blank:1 Unrecognized Content-Security-Policy directive ''self''.

about:blank:1 Ignoring duplicate Content-Security-Policy directive 'style-src'.

about:blank:1 Ignoring duplicate Content-Security-Policy directive 'connect-src'.

about:blank:1 Ignoring duplicate Content-Security-Policy directive 'img-src'.

about:blank:1 Ignoring duplicate Content-Security-Policy directive 'script-src'.

about:blank:1 Ignoring duplicate Content-Security-Policy directive 'frame-src'.

about:blank:1 Unrecognized Content-Security-Policy directive ''self''.

about:blank:1 Ignoring duplicate Content-Security-Policy directive 'style-src'.

about:blank:1 Ignoring duplicate Content-Security-Policy directive 'connect-src'.

about:blank:1 Ignoring duplicate Content-Security-Policy directive 'img-src'.

about:blank:1 Ignoring duplicate Content-Security-Policy directive 'script-src'.

about:blank:1 Ignoring duplicate Content-Security-Policy directive 'frame-src'.

about:blank:1 Unrecognized Content-Security-Policy directive ''self''.

about:blank:1 Ignoring duplicate Content-Security-Policy directive 'style-src'.

about:blank:1 Ignoring duplicate Content-Security-Policy directive 'connect-src'.

about:blank:1 Ignoring duplicate Content-Security-Policy directive 'img-src'.

about:blank:1 Ignoring duplicate Content-Security-Policy directive 'script-src'.

about:blank:1 Ignoring duplicate Content-Security-Policy directive 'frame-src'.

10Refused to load the image '<URL>' because it violates the following Content Security Policy directive: "img-src <URL> <URL>".

7Refused to load the script '<URL>' because it violates the following Content Security Policy directive: "script-src <URL> <URL>". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.

classic.html:1 Refused to frame 'https://xat.com/content/web/R00030/box/www/settings.html' because it violates the following Content Security Policy directive: "frame-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com".

classic.html:1 Refused to frame 'https://xat.com/content/web/R00030/box/www/actions.html' because it violates the following Content Security Policy directive: "frame-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com".

DevTools failed to load SourceMap: Could not load content for https://xat.com/sw.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load SourceMap: Could not load content for https://xat.com/content/web/R00030/workbox-283cc2fc.js.map: HTTP error: status code 403, net::ERR_HTTP_RESPONSE_CODE_FAILURE

 

Also there's 180 issues throughout different categories such as accessibility, compatibility, performance, pwa, and security 

Edited by RaptorlJesus
Link to comment
Share on other sites

  • 0
  • Members
10 minutes ago, LaFleur said:

I see something related to Kaspersky in the errors.

 

Are you able to set an exception for xat.com on Kaspersky? For reference, please see: https://support.kaspersky.com/common/error/other/15335

 

That should likely resolve it.

Slowly getting there! now i see this instead https://imgur.com/phcE9BC

 

Quote

xat.com/:14 Refused to load the image 'data:image/svg+xml;charset=utf8,%3Csvg viewBox='0 0 30 30' xmlns='http://www.w3.org/2000/svg'%3E%3Cpath stroke='rgba(255, 255, 255, 0.5)' stroke-width='2' stroke-linecap='round' stroke-miterlimit='10' d='M4 7h22M4 15h22M4 23h22'/%3E%3C/svg%3E' because it violates the following Content Security Policy directive: "img-src 'self' https://*.xat.com/ https://images.weserv.nl/ http://*.tinypic.com/ https://i.imgur.com/ https://ssl.google-analytics.com/".

android-chrome-192x192.png:1 GET https://xat.com/img/android-chrome-192x192.png 404
xat.com/:1 Error while trying to use the following icon from the Manifest: https://xat.com/img/android-chrome-192x192.png (Download error or resource isn't a valid image)
jquery.min.js:2 [Intervention] Images loaded lazily and replaced with placeholders. Load events are deferred. See https://go.microsoft.com/fwlink/?linkid=2048113
activity.js:1 !printErr=wasm streaming compile failed: TypeError: Failed to execute 'compile' on 'WebAssembly': Incorrect response MIME type. Expected 'application/wasm'.
printErr @ activity.js:1
(anonymous) @ xatcorewasm.php:1
Promise.then (async)
createWasm @ xatcorewasm.php:1
(anonymous) @ xatcorewasm.php:1
(anonymous) @ xatcorewasm.php:1
activity.js:1 !printErr=falling back to ArrayBuffer instantiation
printErr @ activity.js:1
(anonymous) @ xatcorewasm.php:1
Promise.then (async)
createWasm @ xatcorewasm.php:1
(anonymous) @ xatcorewasm.php:1
(anonymous) @ xatcorewasm.php:1
firebase.js:1 FBM:An error occurred while retrieving token.  FirebaseError: Messaging: The notification permission was not granted and blocked instead. (messaging/permission-blocked).
    at ot.<anonymous> (https://www.gstatic.com/firebasejs/8.0.1/firebase-messaging.js:1:35588)
    at https://www.gstatic.com/firebasejs/8.0.1/firebase-messaging.js:1:1982
    at Object.next (https://www.gstatic.com/firebasejs/8.0.1/firebase-messaging.js:1:2087)
    at https://www.gstatic.com/firebasejs/8.0.1/firebase-messaging.js:1:1028
    at new Promise (<anonymous>)
    at d (https://www.gstatic.com/firebasejs/8.0.1/firebase-messaging.js:1:779)
    at ot.getToken (https://www.gstatic.com/firebasejs/8.0.1/firebase-messaging.js:1:35341)
    at o (https://xat.com/content/web/R00030/box/www/firebase.js:1:663)
    at https://xat.com/content/web/R00030/box/www/firebase.js:1:1302
(anonymous) @ firebase.js:1
Promise.catch (async)
o @ firebase.js:1
(anonymous) @ firebase.js:1
Promise.then (async)
(anonymous) @ firebase.js:1
xat.com/:1 Notifications permission has been blocked as the user has ignored the permission prompt several times. This can be reset in Page Info which can be accessed by clicking the lock icon next to the URL. See https://permanently-removed.invalid/features/6443143280984064 for more information.
classic.html:10 Unrecognized Content-Security-Policy directive ''self''.

classic.html:10 Ignoring duplicate Content-Security-Policy directive 'style-src'.

classic.html:10 Ignoring duplicate Content-Security-Policy directive 'connect-src'.

classic.html:10 Ignoring duplicate Content-Security-Policy directive 'img-src'.

classic.html:10 Ignoring duplicate Content-Security-Policy directive 'script-src'.

classic.html:10 Ignoring duplicate Content-Security-Policy directive 'frame-src'.

classic.html:10 Refused to load the stylesheet 'https://xat.com/content/web/R00030/box/www/normalize.css' because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Note that 'style-src-elem' was not explicitly set, so 'style-src' is used as a fallback.

classic.html:10 Refused to load the stylesheet 'https://xat.com/content/web/R00030/box/www/platform.css' because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Note that 'style-src-elem' was not explicitly set, so 'style-src' is used as a fallback.

classic.html:10 Refused to load the stylesheet 'https://xat.com/content/web/R00030/box/www/xat.css' because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Note that 'style-src-elem' was not explicitly set, so 'style-src' is used as a fallback.
 

following the steps reduced it to 17 errors

Quote

jquery.min.js:2 [Intervention] Images loaded lazily and replaced with placeholders. Load events are deferred. See https://go.microsoft.com/fwlink/?linkid=2048113
activity.js:1 !printErr=wasm streaming compile failed: TypeError: Failed to execute 'compile' on 'WebAssembly': Incorrect response MIME type. Expected 'application/wasm'.
printErr @ activity.js:1
(anonymous) @ xatcorewasm.php:1
Promise.then (async)
createWasm @ xatcorewasm.php:1
(anonymous) @ xatcorewasm.php:1
(anonymous) @ xatcorewasm.php:1
activity.js:1 !printErr=falling back to ArrayBuffer instantiation
printErr @ activity.js:1
(anonymous) @ xatcorewasm.php:1
Promise.then (async)
createWasm @ xatcorewasm.php:1
(anonymous) @ xatcorewasm.php:1
(anonymous) @ xatcorewasm.php:1
firebase.js:1 FBM:An error occurred while retrieving token.  FirebaseError: Messaging: The notification permission was not granted and blocked instead. (messaging/permission-blocked).
    at ot.<anonymous> (https://www.gstatic.com/firebasejs/8.0.1/firebase-messaging.js:1:35588)
    at https://www.gstatic.com/firebasejs/8.0.1/firebase-messaging.js:1:1982
    at Object.next (https://www.gstatic.com/firebasejs/8.0.1/firebase-messaging.js:1:2087)
    at https://www.gstatic.com/firebasejs/8.0.1/firebase-messaging.js:1:1028
    at new Promise (<anonymous>)
    at d (https://www.gstatic.com/firebasejs/8.0.1/firebase-messaging.js:1:779)
    at ot.getToken (https://www.gstatic.com/firebasejs/8.0.1/firebase-messaging.js:1:35341)
    at o (https://xat.com/content/web/R00030/box/www/firebase.js:1:663)
    at https://xat.com/content/web/R00030/box/www/firebase.js:1:1302
(anonymous) @ firebase.js:1
Promise.catch (async)
o @ firebase.js:1
(anonymous) @ firebase.js:1
Promise.then (async)
(anonymous) @ firebase.js:1
xat.com/:1 Notifications permission has been blocked as the user has ignored the permission prompt several times. This can be reset in Page Info which can be accessed by clicking the lock icon next to the URL. See https://permanently-removed.invalid/features/6443143280984064 for more information.
android-chrome-192x192.png:1 GET https://xat.com/img/android-chrome-192x192.png 404
xat.com/:1 Error while trying to use the following icon from the Manifest: https://xat.com/img/android-chrome-192x192.png (Download error or resource isn't a valid image)
classic.html:10 Unrecognized Content-Security-Policy directive ''self''.

classic.html:10 Ignoring duplicate Content-Security-Policy directive 'style-src'.

classic.html:10 Ignoring duplicate Content-Security-Policy directive 'connect-src'.

classic.html:10 Ignoring duplicate Content-Security-Policy directive 'img-src'.

classic.html:10 Ignoring duplicate Content-Security-Policy directive 'script-src'.

classic.html:10 Ignoring duplicate Content-Security-Policy directive 'frame-src'.

classic.html:10 Refused to load the stylesheet 'https://xat.com/content/web/R00030/box/www/normalize.css' because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Note that 'style-src-elem' was not explicitly set, so 'style-src' is used as a fallback.

classic.html:10 Refused to load the stylesheet 'https://xat.com/content/web/R00030/box/www/platform.css' because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Note that 'style-src-elem' was not explicitly set, so 'style-src' is used as a fallback.

classic.html:10 Refused to load the stylesheet 'https://xat.com/content/web/R00030/box/www/xat.css' because it violates the following Content Security Policy directive: "style-src https://me.kis.v2.scr.kaspersky-labs.com wss://me.kis.v2.scr.kaspersky-labs.com". Note that 'style-src-elem' was not explicitly set, so 'style-src' is used as a fallback.
 

adding to exclusion list reduced it to 14, tried disabling "block connections over ssl 2.0" and "decrypt ssl connections that use EV certification" but that changed nothing

Link to comment
Share on other sites

  • 0
  • Members
15 minutes ago, RaptorlJesus said:

Slowly getting there! now i see this instead https://imgur.com/phcE9BC

 

following the steps reduced it to 17 errors

adding to exclusion list reduced it to 14, tried disabling "block connections over ssl 2.0" and "decrypt ssl connections that use EV certification" but that changed nothing

Quote

activity.js:1 !printErr=wasm streaming compile failed: TypeError: Failed to execute 'compile' on 'WebAssembly': Incorrect response MIME type. Expected 'application/wasm'.
printErr @ activity.js:1
activity.js:1 !printErr=falling back to ArrayBuffer instantiation
printErr @ activity.js:1
firebase.js:1 FBM:An error occurred while retrieving token.  FirebaseError: Messaging: The notification permission was not granted and blocked instead. (messaging/permission-blocked).
    at ot.<anonymous> (https://www.gstatic.com/firebasejs/8.0.1/firebase-messaging.js:1:35588)
    at https://www.gstatic.com/firebasejs/8.0.1/firebase-messaging.js:1:1982
    at Object.next (https://www.gstatic.com/firebasejs/8.0.1/firebase-messaging.js:1:2087)
    at https://www.gstatic.com/firebasejs/8.0.1/firebase-messaging.js:1:1028
    at new Promise (<anonymous>)
    at d (https://www.gstatic.com/firebasejs/8.0.1/firebase-messaging.js:1:779)
    at ot.getToken (https://www.gstatic.com/firebasejs/8.0.1/firebase-messaging.js:1:35341)
    at o (https://xat.com/content/web/R00030/box/www/firebase.js:1:663)
    at https://xat.com/content/web/R00030/box/www/firebase.js:1:1302
(anonymous) @ firebase.js:1
xat.com/:1 Notifications permission has been blocked as the user has ignored the permission prompt several times. This can be reset in Page Info which can be accessed by clicking the lock icon next to the URL. See https://permanently-removed.invalid/features/6443143280984064 for more information.
classic.html:10 Unrecognized Content-Security-Policy directive ''self''.

classic.html:10 Ignoring duplicate Content-Security-Policy directive 'style-src'.

classic.html:10 Ignoring duplicate Content-Security-Policy directive 'connect-src'.

classic.html:10 Ignoring duplicate Content-Security-Policy directive 'img-src'.

classic.html:10 Ignoring duplicate Content-Security-Policy directive 'script-src'.

classic.html:10 Ignoring duplicate Content-Security-Policy directive 'frame-src'.

6Refused to load the stylesheet '<URL>' because it violates the following Content Security Policy directive: "style-src <URL> <URL>". Note that 'style-src-elem' was not explicitly set, so 'style-src' is used as a fallback.

xat.com/:1 [Intervention] Images loaded lazily and replaced with placeholders. Load events are deferred. See https://go.microsoft.com/fwlink/?linkid=2048113
DevTools failed to load SourceMap: Could not load content for https://xat.com/sw.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load SourceMap: Could not load content for https://xat.com/content/web/R00030/workbox-283cc2fc.js.map: HTTP error: status code 403, net::ERR_HTTP_RESPONSE_CODE_FAILURE

YES I AM JUST DOWN TO THIS ERROR

Link to comment
Share on other sites

  • 0
  • Volunteers

The question or questions in this topic have been answered and an answer has been marked. This topic is now closed.

 

If you have any other questions, please open a new topic.

 

@RaptorlJesus Can you please private message @SLOom answering his question?

 

Thank you.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.