Grafana not running behind nginx

I am referring to the grafana docs to try to run it behind Nginx.

Here is my config,

[server]
domain = vogo-alpha.cloudapp.net
root_url = %(protocol)s://%(domain)s:/grafana

Here is nginx config,

upstream vogo_grafana {
    server 127.0.0.1:3000;
}

server {
    listen 80;
    server_name vogo-alpha.cloudapp.net;


location ~ ^/grafana {

            proxy_pass http://vogo_grafana;

            access_log /var/log/nginx/grafana_access.log;
            error_log /var/log/nginx/grafana_error.log;
    }

But it says, message: Basic auth failed

What can be the issue ?

http://docs.grafana.org/installation/behind_proxy/#nginx-configuration

 location /grafana/ {
  proxy_pass http://localhost:3000/;
}

The trailing slashes are important

@torkel

I got it running behind nginx, it was working fine yesterday.

What about this now ? This is what I got when I forward the port 3000 of my server to my machine. The same I am getting when I access it via Nginx.

@torkel This is error in the log fiiles,

t=2017-04-29T13:30:58+0530 lvl=eror msg="Request error" logger=context userId=0 orgId=0 uname= error="session(release): write /var/lib/grafana/sessions/c/4/c4042a76b8689a7f: no space left on device" stack="/usr/local/go/src/runtime/panic.go:489 (0x42f00f)\n/go/src/github.com/grafana/grafana/pkg/middleware/session.go:82 (0xa92d96)\n/usr/local/go/src/runtime/asm_amd64.s:514 (0x459438)\n/usr/local/go/src/reflect/value.go:434 (0x4aa01f)\n/usr/local/go/src/reflect/value.go:302 (0x4a95e4)\n/go/src/github.com/grafana/grafana/vendor/github.com/go-macaron/inject/inject.go:117 (0x759104)\n/go/src/github.com/grafana/grafana/vendor/gopkg.in/macaron.v1/context.go:113 (0x776692)\n/go/src/github.com/grafana/grafana/vendor/gopkg.in/macaron.v1/context.go:104 (0x7765b6)\n/go/

Hi @luvpreet,

I am exactly getting the same error which you had been got. How did can you fix the error?

Actually the space on my server was full. And the process was not getting any space, so it couldn’t run. I cleared some space and it was running again.

Are there any errors in the Grafana server logs?

I am facing the same issue when its accessed via nginx. Any resolution?