How do I set up Redash server behind an nginx with path?

[eladitzhakian]

Hey everyone

I want to set up a Redash server behind an nginx reverse-proxy, but I want it to sit behind a path, meaning:

location /redash {
   proxy_pass http://redash/;
}

Is there documentation regarding how to do this? There's usually an environment variable like BASE_PATH to help get around the path issues.

[aejazm]

I used Caddy just to do this as I felt that things are more complex to configure in nginx. You just need the following configuration file for caddy to access redash using the URL https://yourhost.yourdomain.com

yourhost.yourdomain.com {
        log
        log {
           output file /var/log/caddy/access.log
        }
        reverse_proxy localhost:5000
        tls [email protected]
}

Assuming that redash is already setup to run on yourhost.yourdomain.com

Hope it helps.

[justinclift]

Note that I just reformatted that config section to be easier to read. 😄

[eladitzhakian]

Thank you, however I need to use nginx with a path like /redash

[aejazm]

Thanks. My first post....

…

On Mon, Jul 31, 2023 at 9:19 PM Justin Clift ***@***.***> wrote: Note that I just reformatted that config section to be easier to read. 😄 — Reply to this email directly, view it on GitHub <#6319 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHQOXKT7WRM2PAGRYBTEUUDXTB7UXANCNFSM6AAAAAA25CFKQI> . You are receiving this because you commented.Message ID: ***@***.***>

[aejazm]

With nginx you could try the following. Note that I haven't tried this myself, so it could take some tweaking.

https{
...
server {
        listen       5000 default_server;
        listen       [::]:5000 default_server;
        server_name  _;
        
        location / {
             proxy_pass             http://localhost:5000;
             proxy_set_header       Host $host;
        }
  }
}

[eladitzhakian]

Thanks but let me reiterate that the path shouldnt be /, it should be /redash and thats why I believe further configuration is required

[justinclift]

As a rough guess there, making that location line say this might work:

location /redash {

[eladitzhakian]

@justinclift appreciate your suggestion but that won't work. you see redash's app has to be configured to use paths prefixed by /redash

[justinclift]

@eladitzhakian Yeah, now that you mention it this is sounding familiar. Might be an environment variable or similar setting, to set the "slug".

The old online redash.io service used to have things named by "slug". From rough memory:

• https://app.redash.io/customer1/
• https://app.redash.io/customer2/
• https://app.redash.io/customer3/

So, the "slug" thing would be the customer1, customer2, customer3 in the examples above. I'm saying "slug" because that's the term I remembering being used for that.

---

Maybe it's just the standard REDASH_HOST environment variable which needs changing?

https://redash.io/help/open-source/admin-guide/env-vars-settings

So, instead of foo.example.com it would be something like foo.example.com/something.

No clear idea (I'm very, very overdue for sleep), but it might be worth trying out. 😄

[aejazm]

I didn't want /redash in the path, hence the need for tweaking...

…

On Mon, Jul 31, 2023, 10:09 PM Justin Clift ***@***.***> wrote: As a rough guess there, making that location line say this *might* work: location /redash { — Reply to this email directly, view it on GitHub <#6319 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHQOXKVDOUWX6FXZHXFGUMDXTCFP3ANCNFSM6AAAAAA25CFKQI> . You are receiving this because you commented.Message ID: ***@***.***>

[armando-fandango]

any solutions for this ?

[anemology]

Hope this can help, should work with SAML/LDAP login too. We are using SAML login and it's running for a while, no Redash code change needed.

Frontend use NGINX's sub_filter to replace / to /redash.
Backend use SCRIPT_NAME header let WSGI to prepend /redash when processing requests.

Redash version: v10.1.0, Docker Tag: redash/redash:10.1.0.b50633
NGINX version: nginx:1.23.2-alpine

upstream redash_server {
    server 127.0.0.1:5000;
}

server {
    listen      443           ssl http2 default_server;
    listen [::]:443           ssl http2 default_server;

    access_log                /dev/stdout;
    error_log                 /dev/stderr info;

    include /etc/nginx/ssl.conf;

    location /redash/ {
        sub_filter ="/" ="/redash/";
        sub_filter ="/static/ ="/redash/static/;
        sub_filter ="/ldap/ ="/redash/ldap/;
        sub_filter ="/saml/login ="/redash/saml/login;
        sub_filter url(/static url(/redash/static;
        sub_filter_once off;
        sub_filter_types application/javascript text/css text/xml text/javascript application/json text/plain;

        proxy_set_header Host $http_host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header SCRIPT_NAME /redash;

        proxy_pass       http://redash_server;
    }
}

Reference:

• Hosting redash not under root
• https://wsgi.readthedocs.io/en/latest/definitions.html#envvar-SCRIPT_NAME

[rajnathsah]

It works but while refreshing in url i can see location getting appended like this

redash/redash/redash/redash/redash/redash/redash/redash/redash

With each refresh, it is getting increased. Am i missing anything here?

[anemology]

@rajnathsah did you missing one of double quotes? Or you can post your nginx config and the URL encounter issue here.

[rajnathsah]

Here is my nginx conf

location /redash/ {
    sub_filter ="/" ="/redash/";
    sub_filter ="/static/ ="/redash/static/;
    sub_filter ="/ldap/ ="/redash/ldap/;
    sub_filter ="/saml/login ="/redash/saml/login;
    sub_filter url(/static url(/redash/static;
    sub_filter_once off;
    sub_filter_types application/javascript text/css text/xml text/javascript application/json text/plain;

    proxy_set_header Host $http_host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header SCRIPT_NAME /redash;

    proxy_pass  http://127.0.0.1:5000;
}

Let me know if you see anything wrong here?