Card #3392 · Grafana
Difficulty configuring reverse proxies and SSL/TLS for Grafana
Users struggle to correctly set up Grafana behind reverse proxies (Apache, IIS) and manage SSL/TLS certificates. Common issues include incorrect sub-path routing for static files, TLS handshake errors with self-signed certificates, and URL redirection problems.
Pain score
0.20/ 1.00 · weighted product of four components
Reach1.00distinct authors (log-normalized)
Recency1.00freshness decay, half-life months
Engagement0.99upvotes + comments, normalized
Monetization0.25willingness-to-pay cues in evidence
§ Evidence — 5 verified quotes
I hit the same issue with Grafana 11.1.3 on Debian with Apache 2.4.57. This is my working config running Grafana behind Apache reverse proxy on sub-path https://example.com/grafana/
I would like to access grafana using subdomain.domain.report without using port number 3000.
After running grafana, it keeps spamming “ TLS handshake error from 127.0.0.1:48610: tls: first record does not look like a TLS handshake ” on console
Is it expected, that when you providing subpath (i.e. /grafana), static files still serves from the root /public, instead of /grafana/public?
I’m getting the following error when trying to setup a “Personal” cloud-hosted grafana instance. “Unable to load TLS certificate”
Comments are a Pro feature — join the conversation, share what you've shipped, hear what others are building.
Upgrade to Pro