Appearance Customize problem

Hi there,

On the customizer page, can you check it's Google Dev tool's console log? Can you share the errors your site is getting?

If you're not sure how to do it, can you provide use temporary backend access to check it for you?

You can use the private information text field to provide the site details. Let us know. :D

Here is console log:
https://ibb.co/5r5dPjb

I've deactivated Autoptimize and WP Fastest Cache plugins. Problem exist.

Here is Conslole log from FIREFOX"

JQMIGRATE: Migrate is installed, version 3.3.2 load-scripts.php:5:709
Content Security Policy: Ignoring ‘x-frame-options’ because of ‘frame-ancestors’ directive.
An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can remove its sandboxing. customize.php
JQMIGRATE: Migrate is installed, version 3.3.2 jquery-migrate.min.js:2:709
Loading failed for the <script> with source “https://www.googletagmanager.com/gtag/js?id=UA-177449233-1”. www.aantdesign.net:78:1
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified

Can you try disabling ALL plugins except GP Premium and see if the issue still occurs?

If you have a child theme, can you temporarily disable it as well?

And then check if the issue still occurs. Let us know.

I've deactivated all plugins except GP Premium and Really simple SSL and I get this:

JQMIGRATE: Migrate is installed, version 3.3.2 load-scripts.php:5:709
Content Security Policy: Ignoring ‘x-frame-options’ because of ‘frame-ancestors’ directive.
An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can remove its sandboxing. customize.php
JQMIGRATE: Migrate is installed, version 3.3.2 jquery-migrate.min.js:2:709

I also try with Twenty-Twenty One theme and I get same Appearance -> Customizepage.

I’ve deactivated all plugins except GP Premium and Really simple SSL and I get this:

This kind of error is usually from security plugin settings.

Really simple SSL is a security plugin setting. You may have to tweak its setting to fix the issue.

You can actually see this but completely disabling Really Simply SSL. Once you do, the customizer will likely work as intended and when you re-enable, it will likely break again. It's because the plugin prevents the assets from loading properly.

You will have to make changes on its security setting to allow things to load. The settings is CSP related. :D

Note: Really Simple SSL is a third-party plugin outside of our control. You may have to consult them on which is the best approach.

Ok, I'll try disable that plugin and see what happened.

Problem stays.

Hi there,

can you confirm that error occurs when using the Twenty-Twenty One theme ?