Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

An error occurred while saving any configuration.

aliaksandr_hvozdzeu
Level 3
Level 3

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?

 

image-2020-10-15-15-21-59-319.png

Also, I got this error in the console

Screenshot_1.png

Thank you very much in advance!

 

PS AEM 6.5.6 version

1 Accepted Solution
aliaksandr_hvozdzeu
Correct answer by
Level 3
Level 3

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.

View solution in original post

1 Reply
Vaibhavi
Community Advisor
Community Advisor

Hi @aliaksandr_hvozdzeu , 

 

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

aliaksandr_hvozdzeu
Level 3
Level 3
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
Level 3

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

Umesh_Thakur
Community Advisor
Community Advisor

@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
Correct answer by
Level 3
Level 3

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.

View solution in original post

kautuk_sahni
Community Manager
Community Manager
@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).