Chronograf: Problems with basepath on 1.5.0.1

[voiprodrigo]

Hello,

I'm having two problems with basepath after upgrading to 1.5.0.1. Previously I was using 1.4.4 without issue in this regard.

Problem 1: basepath "/whatever/chronograf-something" is considered invalid and service does not start.

Problem 2: basepath "/whatever/chronograf" service starts, but can't access it properly, just get "404 page not found".

I'm using CentOS 7 with systemd, basepath set via BASE_PATH in an EnvironmentFile.

Thanks

[russorat]

@voiprodrigo thanks for the issue. Just to clarify, you've set your basepath to be BASE_PATH=/whatever/chronograf-something?

[voiprodrigo]

To be exact: BASE_PATH="/whatever/chronograf-something"

[russorat]

hyphens are not allowed in basepaths. When i try to set that, i get:

ERRO[0000] Invalid basepath, must follow format "/mybasepath"  basepath=invalid component=server
2018/06/15 09:23:50 Invalid basepath, must follow format "/mybasepath"
make: *** [run-dev] Error 1

but setting to BASE_PATH="/whatever/chronografsomething" works fine.

[voiprodrigo]

I reverted to 1.4.4 and both cases work fine again.

Please also see comments in https://github.com/influxdata/chronograf/commit/2ce7d8e3eea9e2319271df34118647bf3826186f#diff-91bbeda7eb98a7adc57b9e47e2cf5c2b

[russorat]

thanks for the link. I connected this issue and your comment so we can review.

[jaredscheib]

This was changed in 1.5.0, but we can revert that aspect to make it so that hyphens or any valid URL path will work.

[voiprodrigo]

(Sorry to comment on closed issue)

Thanks for addressing the hyphen situation, but regarding this:

Problem 2: basepath "/whatever/chronograf" service starts, but can't access it properly, just get "404 page not found".

Any hints? I assume it's a different root-cause, as the behaviour is different.

Thanks.

@jaredscheib @russorat

[voiprodrigo]

I managed to get it working again. But this seems to be an unexpected change in basepath handling.
I have an Apache in front of chronograf. If the ProxyPass is set to http://localhost:8888, it fails with 404 (it worked before). I changed the ProxyPass to forward to http://localhost:8888/basepath, and now it's ok.

[russorat]

@voiprodrigo i'm not sure i understand completely.

The expected behavior is that when basepath is enabled, accessing just the standard localhost:8888 should return a 404. accessing localhost:888/basepath should work. I'm not familair with ProxyPass specificially, but if forwarding to just localhost:8888 was working before, it was unintentional and incorrect. Forwarding to /basepath is the correct solution.