check if this helps - Re: Sling Exporter with custom selector

access control should work for this

Is maven-scr-plugin:1.7.4 generated by archetype 11 or is it carried over from your 6.1 pom.xml?A best practice - It’s recommended to place Uber jar at the bottom of the dependency list so that Maven will honor any newer versions of dependencies that is explicitly declared inside the project POM.

Couple of questions:1) Does the issue happens with  '-Pauto-install-bundle' or '-Pauto-install-package' or both profiles? -- based on your statement 'We are deploying use maven content plugin with bundle auto install.'? 2) If the issue happens with 'auto-install-bundle'  - can you verify that the '/...

A solution would be to write a custom exporter based on your use caseAdobe Experience Manager Help | Developing Sling Model Exporters in AEM Adobe Experience Manager Help | Understanding Sling Model Exporters in AEM

I can't pinpoint any issue unless I go through the code. I can try if you're willing to share the minimal code package.

Do you mean to say that you have followed Adobe Experience Manager Help | Getting Started with React and AEM SPA Editor  and same is working fine but your own custom component in AEM?Could you share more details about that component(s) and what version/SP of AEM do you use?

Most likely your listener IP is different than your public IP or otherwise its an internal network/firewall issue.logon to that box, check the hosts file for that IPAs mentioned by Jörg​, secure it ASAP

Talk to your CSM for the cutover period constraints in Prod/Non-Prod environments as applicable

Check if Versioned ClientLibs helps for your use case