Setting UrlRoot gives ERR_EMPTY_RESPONSE

[derekantrican]

I've been searching through https://github.com/cockpit-project/cockpit/issues?q=is%3Aissue%20UrlRoot and asking ChatGPT, but unfortunately haven't found a good solution.

I've got cockpit installed on an ubuntu server and I was able to access it fine via http://192.168.88.250:9090. However, now that I want to specify UrlRoot, I'm having all kinds of problems.

I've got the following in /etc/cockpit/cockpit.conf:

[WebService]
UrlRoot = /abc
AllowUnencrypted = true

But when I go to http://192.168.88.250:9090/abc I get the error: "192.168.88.250 didn’t send any data. ERR_EMPTY_RESPONSE" (http://192.168.88.250:9090 gives me a proper cockpit 404 page)

What am I missing?

[jelly]

The UrlRoot option is there for reverse proxying, which you don't seem to be doing? Is there any reason why you want cockpit-ws to work with /abc?

[derekantrican]

Hi @jelly - I'm using cloudflare tunnels, so I'd like to be able to host my cockpit instance at like 'server.mydomain.com/abc'