Support

You only see this message when CloudFlare's Rocket Loader JavaScript and local storage data is detected on the page. Seeing that on a site which doesn't use CloudFlare is strange and makes me think that something is wrong with the JavaScript on your site.

I am also very confused because in the same message you say that Joomla (the CMS which powers your site) doesn't work anymore but also that your site (powered by Joomla) does work. These two statements are mutually exclusive. You obviously mean something else, but what? What doesn't work? Try to be more detailed so I can understand what you mean. I can't help you unless I can at the very least understand what is the problem you are facing.

First, delete your .htaccess file. It defines a Content-Security-Policy which prevents inline scripts and inline styles from being applied. This is incompatible with Joomla 3. Joomla 3 (and Kickstart itself) use inline scripts and inline event attributes in HTML elements. Since these are disallowed the JavaScript on the page breaks. Akeeba Backup does NOT use inline scripts or inline event attributes BUT if the JavaScript on the page has already stopped working because of this kind of an error then our JavaScript never gets the chance to run which is why the JavaScript-reliant detection of RocketLoader seems to not be working. Basically, the Content-Security-Policy you added in your .htaccess broke your site. It's not something related to our software.

Note that the Content-Security-Policy which disallows inline scripts will only work on Joomla 4 and ONLY if you set up the relevant feature in Joomla itself AND your 3PD extensions support it. Our software does support it since early 2020 — it was part of the large scale JavaScript refactoring you saw in our release notes back then.

Since I didn't have enough information before I assumed that you are using Apache whose behaviour is controlled by a .htaccess file. Instead, it looks like you are using NginX. Unlike Apache, NginX' configuration is NOT controlled by a file in your site's root. You need to edit the actual site definition and restart or reload the NginX server for any changes to be applied.

Ask your host how to remove any custom NginX configuration you have set up which generates the HTTP header Content-Security-Policy: default-src 'self'; which is causing the problem you came here with.

Also note that your custom NginX configuration seems to block access to the phpinfo.php file, using it to reply with a 404 error. The 404 is then caught by Joomla which is why you see Joomla's 404 page when trying to access that file.