NC_PUBLIC_URL not respected in subdirectory reverse proxy format

[alfureu]

Please enter the following details

NocoDB used as docker : true
NocoDB version : 0.84.8
Database used in NC_DB URL : pg
Project was created by clicking : New Project by connecting to external database
Database on which spreadsheet is created : pg
OS on which NocoDB is running : CentOS 7.0
Node.js version if running as node : -
Database version : -

Steps To Reproduce

1. run docker container
2. define under environments NC_PUBLIC_URL=[sub.domain.tld/nocodb] and NC_BACKEND_URL=[http://IP:port]
3. try to define nocodb instance instead of subdomain format (e.g. nocodb.domain.tld) as a subdirectory (e.g. sub.domain.tld/nocodb) in nginx or Nginx Proxy Manager (NPM)
4. Whenever one types sub.domain.tld/nocodb. the NC_PUBLIC_URL is not respected and switches to sub.domain.tld/dashboard; also, the page is clearly available from sub.domain.tld as well, although it is defined in NPM as sub.domain.tld/nocodb

Expected behavior
NC_PUBLIC_URL should be respected and the address should be consequently sub.domain.tld/nocodb/dashboard

Also, please provide detailed documentation for main reverse proxy setups (caddy, nginx, Nginx Proxy Manager, traefik, etc).

[ericparland]

Same issue, seems like issue 428 was re-introduced again.

[bonacci-johannes]

Any update on this issue? Can one provide an instruction how to set enviorment variables when using reverse proxies?

[marcw]

I can confirm there are issues when using reverse proxy and subfolders.

I got a working setup with these environment variables:

NC_DASHBOARD_URL=/nocodb/dashboard
NC_PUBLIC_URL=https://blabla.net/nocodb
NUXT_PUBLIC_NC_BACKEND_URL=https://blabla.net/nocodb

and this Caddy reverse proxy configuration bit:

# Contrary to handle_path, the handle directive does not strip prefix.
# We do not want the prefix to be stripped, so we use the handle directive.
handle /nocodb* {
  # The nocodb API server doesn't handle prefixes correctly
  uri /nocodb/api* strip_prefix /nocodb

  reverse_proxy http://nocodb:8080
}

Also interested in this. Running into the same issue using nginx.

[saurabhnanda]

@pranavxc Even I'm facing this issue. Do we know in which version was this re-introduced? I don't mind downgrading till the latest version contains a fix.

[pranavxc]

@saurabhnanda : Can you share the version which you are using currently and are you defining NC_PUBLIC_URL environment variable?

[saurabhnanda]

@saurabhnanda : Can you share the version which you are using currently and are you defining NC_PUBLIC_URL environment variable?

@pranavxc I'm using the latest docker image nocodb/nocodb:latest which has the checksum d0a41b9f5e5e.

I tried TWO setups and both of them didn't work out:

1. UI & API, both in the same subdir:

   # the docker-compose file for my project (nocodb is being used as part of a larger project)
   
   nocodb:
     image: "nocodb/nocodb:latest"
     networks:
       - internal
     environment:
   
       NC_DB: "REDACTED"
       NC_AUTH_JWT_SECRET: "REDACTED"
       NC_DASHBOARD_URL: /nocodb/dashboard
       NC_PUBLIC_URL: "http://${APP_DOMAIN}/nocodb"
       NUXT_PUBLIC_NC_BACKEND_URL: "http://${APP_DOMAIN}/nocodb"
   

   location /nocodb {
       proxy_set_header Host $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_pass http://nocodb:8080;
   }
   

2. UI in a different subdir and API in a different subdir

   # the docker-compose file for my project (nocodb is being used as part of a larger project)
   
   nocodb:
     image: "nocodb/nocodb:latest"
     networks:
       - internal
     environment:
   
       NC_DB: "REDACTED"
       NC_AUTH_JWT_SECRET: "REDACTED"
       NC_DASHBOARD_URL: /noco-ui
       NC_PUBLIC_URL: "http://${APP_DOMAIN}/noco-api"
       NUXT_PUBLIC_NC_BACKEND_URL: "http://${APP_DOMAIN}/noco-api"
   

   location /noco-ui {
       proxy_set_header Host $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_pass http://nocodb:8080;
   }
   
   location ~ ^/noco-api(/?)(.*) {
       proxy_set_header Host $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_pass http://nocodb:8080/$2;
   }
   

[pranavxc]

@saurabhnanda Use the following and try to access the dashboard path directly, for example: http://your_domain/nocodb/dashboard ( with your old config try http://your_domain/nocodb/nocodb/dashboard). If it works then it's related to redirect path related.

nocodb:
  image: "nocodb/nocodb:latest"
  networks:
    - internal
  environment:

    NC_DB: "REDACTED"
    NC_AUTH_JWT_SECRET: "REDACTED"
    NC_DASHBOARD_URL: /dashboard
    NC_PUBLIC_URL: "http://${APP_DOMAIN}/nocodb"
    NUXT_PUBLIC_NC_BACKEND_URL: "http://${APP_DOMAIN}/nocodb"