clio install-gate fails with 400 Bad Request on Creatio 8.3.2 .NET Framework — cliogate package cannot be uploaded
Hi everyone,
I've set up Clio successfully before on other machines, but on this new Windows 11 setup I'm hitting a wall with cliogate installation and can't find a way through.
I'm currently traveling and don't have access to my other machine to compare, so any help to unblock this would be much appreciated.
Environment:
- Creatio: 8.3.2.4199, .NET Framework, IIS, PostgreSQL
- Clio: 8.0.2.67
- OS: Windows 11, IIS 10
- URL: local IIS instance on port 8020
- IsNetCore: false
What works:
- clio ping -e MyEnv → success
- clio packages -f cliogate -e MyEnv → shows cliogate 2.0.0.31 pre-installed
- Installing my own .zip packages via ApplicationManagement UI → works fine
What fails:
- clio install-gate -e MyEnv → uploads then throws EnsureSuccessStatusCode
- Manual upload of cliogate.gz via ApplicationManagement UI → 400 Bad Request
- Manual upload of cliogate as .zip → 400 Bad Request
- clio generate-pkg-zip + upload → 400 Bad Request
The IIS log shows no entry for the failed upload requests — the 400 happens before IIS logs it. InstallZipPackage.log shows no entries for the cliogate upload attempts either.
Current state: the instance has cliogate pre-installed at version 2.0.0.31. Clio 8.0.2.67 requires 2.0.0.32 or higher, so it reports: "To use this command, you need to install the cliogate package version 2.0.0.32 or higher".
Questions:
- Why does PackageInstallerService return 400 for cliogate specifically, while other packages upload fine?
- Is there a way to upgrade cliogate from 2.0.0.31 to 2.0.0.41 without the upload mechanism?
- Is there an alternative download for the cliogate package compatible with Creatio 8.3.2?
Thank you
Julio Falcon
Like