An error occurred while saving any configuration. | Community
Skip to main content
aliaksandr_hvozdzeu
Level 3
February 23, 2021
Solved

An error occurred while saving any configuration.

  • February 23, 2021
  • 6 replies
  • 3380 views

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

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by aliaksandr_hvozdzeu

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.

6 replies

Vaibhavi_J
Level 7
February 23, 2021

Hi @aliaksandr_hvozdzeu , 

 

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

aliaksandr_hvozdzeu
Level 3
February 23, 2021
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
aliaksandr_hvozdzeu
Level 3
February 23, 2021
Any ideas?
aliaksandr_hvozdzeu
Level 3
February 23, 2021

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

Bhuwan_B
Community Advisor
Community Advisor
February 24, 2021

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-login-fail-aem-6-3-sp1/qaq-p/239472

 

Umesh_Thakur
Community Advisor
Community Advisor
February 25, 2021

@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  

aliaksandr_hvozdzeu
aliaksandr_hvozdzeuAuthorAccepted solution
Level 3
March 2, 2021

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
Community Manager
Community Manager
March 11, 2021
@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).
Kautuk Sahni