Ansible Automation Platform 2.5 Containerized Deployment

PAH stands for personal automation hub, right? I assume that’s their downstream version of Galaxy. Looking at your other thread, AAP 2.5 Collection Issues I noticed this

“https://localhost:8443/pulp_ansible/galaxy/published/. Got an unexpected error”,
“when getting available versions of collection test_collection.titan: Unknown”,

I have no idea how all this is meant to work with AAP since I don’t utilize it, but are you really meant to be using localhost when referencing your uh galaxy server? I only ask because later you referenced

that collection is configured with the following URL:

https://REMOVED:8443/pulp_ansible/galaxy/published/

You seem to know enough about technology enough for me to suspect you aren’t concerned about obfuscating localhost from us online strangers.

If you’re totally out of luck and/or just desperate to get things working, may be worth a shot to download the collections you care about from RedHat’s private registry and host them on your private/corporate Gitlab/Github server and reference them that way. Not a great long-term solution, but maybe something to get you going while waiting for RedHat to offer better help.

Sorry if this info isn’t helpful, I’ll stop replying so someone who has more experience can chime in.