How Do I Define My Internal Server As The Primary Galaxy Server URL For Downloading Collections / Roles From requirements.yml After Upgrading To Ansible Tower 3.8 ?

Solution Verified - Updated -


After upgrading to Ansible Tower 3.8, i am no longer able to define my internal/custom galaxy server as PRIMARY GALAXY SERVER URL. Due to this the roles/collections defined in the requirements.yml are trying the access the External Galaxy servers like which are not accessible in our environement and timing out causing delays in Project sync.


  • Ansible Tower 3.8

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In