Publishing PowerShell: Error 400

[Guest]

Background:
I'm running the latest ProGet docker container, which might make a difference.

Problem:
When I try to publish a PowerShell module (this happens with all modules, but in this example I'm publishing Plaster) to our feed, I get a 400 error. If I specify an incorrect apikey, I get a 403 as expected.

Register-PSRepository -Name proget-psgallery`
                      -SourceLocation http://192.168.1.230/nuget/proget-psgallery `
                      -PublishLocation http://192.168.1.230/nuget/proget-psgallery `
                      -InstallationPolicy Trusted `
                      -Verbose
Publish-Module -Name Plaster `
               -Repository proget-psgallery `
               -NuGetApiKey 'Admin:Admin' `
               -Verbose

I get the following error message and haven't been successful at hunting it down for why:

VERBOSE: Performing the operation "Publish-Module" on target "Version '1.0.1' of module 'Plaster'".
Publish-PSArtifactUtility : Failed to publish module 'Plaster': 'Response status code does not indicate success: 400 (Bad Request).
'.
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.1.3.1\PSModule.psm1:1260 char:17
+ ...             Publish-PSArtifactUtility @PublishPSArtifactUtility_Param ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : FailedToPublishTheModule,Publish-PSArtifactUtility

Product: ProGet
Version: 4.7.13

[Guest]

Were you ever able to work-around this?

Its hard to say what was causing the error, because everything looks correct from a quick scan of the commands ...

[Guest]

Unfortunately, no, I was not. I'm in the process of taking a look at ProGet running in containers again, I will test in the near future and let you know. I don't expect it to be working unless something changed with the containers in the last several months.