# CSS failing to load on subpath configuration

**URL:** <https://community.taiga.io/t/css-failing-to-load-on-subpath-configuration/6891>\
**Category:** Self hosted Taiga\
**Tags:** docker\
**Created:** [March 29, 2025, 10:15am UTC](https://community.taiga.io/t/css-failing-to-load-on-subpath-configuration/6891 "2025-03-29T10:15:13Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sean](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/sean/32/4257_2.png) [@Sean](https://community.taiga.io/u/Sean)\
**Post date:** [March 29, 2025, 10:15am UTC](https://community.taiga.io/t/css-failing-to-load-on-subpath-configuration/6891/1 "2025-03-29T10:15:13Z")

</div>

I installed Taiga on my ubuntu server following the steps outlined in the README file on github. I wanted to configure it to be a subpath on a site I host on the same server using NGINX as a webserver.

After following the steps I get the following on the taiga subpath

 ![image](https://europe1.discourse-cdn.com/flex017/uploads/taiga/original/2X/9/90f008ddd28c9d82c26011df4fff4385e8f7ae93.png)

Based on the network tab in the browser inspection I can see there are 404 errors being returned for theme-taiga.css and app-loader.js files

My .env file is configured as follows

```auto
# Taiga's URLs - Variables to define where Taiga should be served
TAIGA_SCHEME=https # serve Taiga using "http" or "https" (secured) connection
TAIGA_DOMAIN=[my-site].com # Taiga's base URL
SUBPATH="/taiga" # it'll be appended to the TAIGA_DOMAIN (use either "" or a "/subpath")
WEBSOCKETS_SCHEME=wss # events connection protocol (use either "ws" or "wss")

```

My nginx config is

```auto
server {
    server_name [my-site].com;
    client_max_body_size 100M;

    root /var/www/my-site;
    index index.php index.html index.htm;

    location / {
        client_max_body_size 100M;
        limit_req zone=one burst=40;
        try_files $uri $uri/ /index.php?$args;
    }

    location /taiga/ {
        proxy_set_header Host $http_host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Scheme $scheme;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_redirect off;
        proxy_pass http://localhost:9000/;
    }

    # Events
    location /taiga/events {
        proxy_pass http://localhost:9000/events;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_set_header Host $host;
        proxy_connect_timeout 7d;
        proxy_send_timeout 7d;
        proxy_read_timeout 7d;
    }

    listen [::]:443 ssl ipv6only=on;
    listen 443 ssl http2;
    ssl_certificate /etc/letsencrypt/live/[my-site].com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/[my-site].com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf;
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem;

    error_log /var/log/nginx/site_error.log;
    access_log /var/log/nginx/site_access.log;
} 

```

Does anyone have any idea why the CSS and JS file may not be located?