An error occurred while saving any configuration.

[aliaksandr_hvozdzeu]

Good day.

Please help me figure out the error. When saving any configuration, I get an error (like in the picture). In this case, the configuration is saved, but the error is still there. What could be the reason?

Also, I got this error in the console

Thank you very much in advance!

PS AEM 6.5.6 version

[aliaksandr_hvozdzeu]

Any ideas?

[aliaksandr_hvozdzeu]

A bit more information. This error appeared after switching to HTTPS and closing the Felix console.  The transition was made according to the instructions: https://helpx.adobe.com/experience-manager/6-3/sites/administering/using/ssl-by-default.html

[kautuk_sahni · Accepted solution]

I found the reason. The configuration was saved under a dedicated path when installing aem.

And when adding a new configuration an error appeared.

Removing the new configuration and adding the org.apache.felix.proxy.load.balancer.connection.enable true property helped to resolve this issue.

Thanks all.

[kautuk_sahni · Accepted solution]

@aliaksandr_hvozdzeu, Thank you for posting the solution with AEM Community. This helps in posterity. Keep the wonderful contribution going (both as learner and contributor).

[#6]

@aliaksandr_hvozdzeu,

This kind of errors normally occurs in Chrome and IE browser due to restriction imposed by security best practices so to fix it you have two options on is use Firefox or implement the security features like uses of HTTPS instead of HTTP.

For more details you can read below article:

https://web.dev/fixing-mixed-content/

Hope this will help.

Umesh Thakur  

[#7]

Can you please check below community Thread and also try replicating issue with latest Service Pack 6.5.7.0 (Software Distribution)

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/mixed-content-https-http-l...

[aliaksandr_hvozdzeu]

Hi @aliaksandr_hvozdzeu , 

Please check if all the bundles are active?? Also please check the logs for error details 

[aliaksandr_hvozdzeu]

There are no errors in the logs and all bundles are active. I cannot understand why it is loaded as HTTP if AEM works throw HTTPS