UI does not function behind reverse proxy

fsiler commented 8 months ago

Describe the bug

I've toyed with different permutations of api.base-url and server.http_path_prefix. System will not function when prefixed at /pyroscope

To Reproduce

Steps to reproduce the behavior:

Start Pyroscope (SHA or version)

1.4.0

Perform Operations(Read/Write/Others)

Configure as follows:

server:
  http_listen_port: 4040
## FMS: these don't appear to work properly for reverse proxy use in 1.4.0
  http_path_prefix: /pyroscope
api:  
  base-url: /pyroscope

Expected behavior

Port-forward config, try to visit UI at /pyroscope. Does not work. Used both kubectl port-forward and HTTPProxy frontend, all broken.

Notably, I can visit /pyroscope/ready and it functions. Not sure about other API endpoints.

Environment

Infrastructure: Kubernetes configured with config.yaml mapped via ConfigMap
Deployment tool: Helm

Additional Context

n/a

hazra-mms commented 8 months ago

I experience the same behaviour adding the base-url config during configuring from the Helm chart. I tried to use port-forward and the UI comes blank.

sylr commented 1 week ago

Same here, trying to setup pyroscope behind tailscale serve but it does not work:

https://tragicomix.xxxxxxxx.ts.net (tailnet only)
|-- /grafana   proxy http://127.0.0.1:3000
|-- /pyroscope proxy http://127.0.0.1:4000

---
api:
  base-url: /pyroscope
server:
  http_path_prefix: /pyroscope
pyroscopedb:
  data_path: /opt/homebrew/var/lib/pyroscope

grafana / pyroscope