Hosting Octopus on a subpath e.g. http://example.com/myoctopusserver causes steps and deployment targets created from step packages to become unusable. You can't add/edit steps in deployment processes or add/edit targets in Portal. The UI fails with a 404 error (or potentially a 502 behind a proxy) when attempting to show the logo and when configuring step or target settings.
Deployment targets affected:
Amazon ECS Cluster
Steps affected:
Deploy Amazon ECS Service
Update Amazon ECS Service
Create Amazon S3 Bucket
Reproduction
Configure Octopus Server to be hosted on a subpath e.g. http://example.com/myoctopusserver. This could be using a virtual directory in IIS or other similar means in other web servers.
Deployment targets:
In the Octopus Portal go to Infrastructure -> Deployment Targets and attempt to add an Amazon ECS Cluster target.
Steps:
In the Octopus Portal go to the deployment process in a project and attempt to add a Deploy Amazon ECS Server step.
Error and Stacktrace
No response
More Information
If configuring the setting Octopus.WebPortal.ListenPrefixes to listen directly on a subpath as opposed to doing this in a web server then the logo can be shown correctly, however configuring a step or target (either editing or creating new) will still fail with a similar 404 error when loading a .js file.
zentron
commented
1 year ago
Team
Severity
Blocking at least one customer
Version
Earliest reported is 2022.1.2232
Latest Version
I could reproduce the problem in the latest build
What happened?
Hosting Octopus on a subpath e.g.
http://example.com/myoctopusservercauses steps and deployment targets created from step packages to become unusable. You can't add/edit steps in deployment processes or add/edit targets in Portal. The UI fails with a 404 error (or potentially a 502 behind a proxy) when attempting to show the logo and when configuring step or target settings.Deployment targets affected:
Steps affected:
Reproduction
Configure Octopus Server to be hosted on a subpath e.g.
http://example.com/myoctopusserver. This could be using a virtual directory in IIS or other similar means in other web servers.Deployment targets:
Steps:
Error and Stacktrace
No response
More Information
If configuring the setting
Octopus.WebPortal.ListenPrefixesto listen directly on a subpath as opposed to doing this in a web server then the logo can be shown correctly, however configuring a step or target (either editing or creating new) will still fail with a similar 404 error when loading a .js file.Workaround
No known workaround