Project Page Reporting 404 and Not Loading

[jwa]

Latest install of the server on a single server (non-cluster) environment with default spaces and no tenants. Visiting the projects page results in an empty page. The page drop-down menu reports

• Unhandled error when communicating with the Octopus Deploy server. The server returned a status of: 404

The same error also occurs on the Tasks page when there are no tasks running.

This prevents me from creating new projects.

[jwa]

Console output:

/bff/spaces/Spaces-1/projects/summaries:1 Failed to load resource: the server responded with a status of 404 (Not Found)
/bff/spaces/Spaces-1/projects/summaries:1 Failed to load resource: the server responded with a status of 404 (Not Found)
app-main.e0f7f8b67551a9708ffc.hashedasset.js:1 Uncaught (in promise) Error
at f (app-main.e0f7f8b67551a9708ffc.hashedasset.js:1:3276937)
at t.default.handleError (app-main.e0f7f8b67551a9708ffc.hashedasset.js:1:3274738)
at e.onreadystatechange (app-main.e0f7f8b67551a9708ffc.hashedasset.js:1:3275563)
/ingest:1 Failed to load resource: the server responded with a status of 404 (Not Found)
app-main.e0f7f8b67551a9708ffc.hashedasset.js:2 Unable to ingest messages: Error Object
(anonymous) @ app-main.e0f7f8b67551a9708ffc.hashedasset.js:2
/ingest:1 Failed to load resource: the server responded with a status of 404 (Not Found)
app-main.e0f7f8b67551a9708ffc.hashedasset.js:2 Unable to ingest messages: Error Object
(anonymous) @ app-main.e0f7f8b67551a9708ffc.hashedasset.js:2
/bff/spaces/Spaces-1/projects/summaries:1 Failed to load resource: the server responded with a status of 404 (Not Found)
app-main.e0f7f8b67551a9708ffc.hashedasset.js:1 Uncaught (in promise) Error
at f (app-main.e0f7f8b67551a9708ffc.hashedasset.js:1:3276937)
at t.default.handleError (app-main.e0f7f8b67551a9708ffc.hashedasset.js:1:3274738)
at e.onreadystatechange (app-main.e0f7f8b67551a9708ffc.hashedasset.js:1:3275563)
/api/telemetry/process:1 Failed to load resource: net::ERR_CONNECTION_TIMED_OUT
logo:1 Failed to load resource: the server responded with a status of 500 (Internal Server Error)
logo:1 Failed to load resource: the server responded with a status of 500 (Internal Server Error)
/bff/spaces/Spaces-1/projects/summaries:1 Failed to load resource: the server responded with a status of 404 (Not Found)
app-main.e0f7f8b67551a9708ffc.hashedasset.js:1 Uncaught (in promise) Error
at f (app-main.e0f7f8b67551a9708ffc.hashedasset.js:1:3276937)
at t.default.handleError (app-main.e0f7f8b67551a9708ffc.hashedasset.js:1:3274738)
at e.onreadystatechange (app-main.e0f7f8b67551a9708ffc.hashedasset.js:1:3275563)
/api/telemetry/process:1 Failed to load resource: net::ERR_CONNECTION_TIMED_OUT
/bff/spaces/Spaces-1/projects/summaries:1 Failed to load resource: the server responded with a status of 404 (Not Found)
/api/telemetry/process:1 Failed to load resource: net::ERR_CONNECTION_TIMED_OUT
/api/telemetry/process:1 Failed to load resource: net::ERR_CONNECTION_TIMED_OUT
/api/telemetry/process:1 Failed to load resource: net::ERR_CONNECTION_TIMED_OUT
/api/telemetry/process:1 Failed to load resource: net::ERR_CONNECTION_TIMED_OUT
/api/telemetry/process:1 Failed to load resource: net::ERR_CONNECTION_TIMED_OUT
/api/telemetry/process:1 Failed to load resource: net::ERR_CONNECTION_TIMED_OUT
/bff/spaces/Spaces-1/projects/summaries:1 Failed to load resource: the server responded with a status of 404 (Not Found)

[jwa]

The tasks page console reports

app-main.e0f7f8b67551a9708ffc.hashedasset.js:1 Uncaught (in promise) Error
at f (app-main.e0f7f8b67551a9708ffc.hashedasset.js:1:3276937)
at t.default.handleError (app-main.e0f7f8b67551a9708ffc.hashedasset.js:1:3274738)
at e.onreadystatechange (app-main.e0f7f8b67551a9708ffc.hashedasset.js:1:3275563)

[finnian.dempsey]

Hi @jwa,

Welcome to the Octopus community, thanks for raising this with us!

It looks like a couple of our endpoints are returning 404’s when using virtual directories on our latest version (2022.3.10674). I’ve raised this with our engineers and have created a public Github issue for getting this fixed. To workaround it in the meantime, configure Octopus to use a binding without a virtual directory.

The issue will be updated with a build to install which contains the fix but feel free to reach out if you have any questions at all!

Best Regards,

[jwa]

We don’t use virtual directories in our octopus installation. Octopus owns the server and IIS does not have any web sites under management.

Maybe what you mean is the “/octopus” prefix that we use is the cause?

[jwa]

I responded to your github issue and put in there my workaround using your suggested work around. Adding the “/” root binding (not replacing the existing /octopus binding) appears to be working. The CORS errors went away (expected) and the Projects/Tasks pages both load. Good advice Fin, thanks!