It's odd because I haven't updated ProGet (or Ansible) since installing it, and it did work back 5 months ago.

You're right, I'll likely need to modify the bootstrap_script if ProGet is not pulling the install.ps1 from the Chocolatey source upon request.

I set up a Chocolatey feed back last fall and tested it without issue. Let's say the url is http://1.1.1.1/nuget/Chocolatey.

We're using Ansible to install software in our environment. So when I originally set up the feed, I used the feed URL above to perform installs with the Ansible module - https://docs.ansible.com/ansible/latest/collections/chocolatey/chocolatey/win_chocolatey_module.html

Recently, one of our engineers was trying to install software with the same feed. When passing that Chocolatey feed into Ansible, Ansible is unable to find the install.ps1 file to install Chocolatey to be able to perform software installs. No one has touched the system since, so I'm not sure why the installer can't be found. We're on version ProGet 2022.9 Build 2 (Docker/ Linux)

From the Ansible docs linked here, this is how Ansible tries to find that file.

This value may also be used when Chocolatey is not installed as the location of the install.ps1 script if bootstrap_script is not set, and only supports URLs for this case. In this case, if the URL ends in “.ps1”, it is used as-is. Otherwise, if the URL appears to contain a “/repository/” fragment, the module will attempt to append “/install.ps1” to find an install script. If neither of these checks pass, the module will strip off the URL path and try to find an “/install.ps1” from the root of the server.