[GH-ISSUE #2099] After installing self hosted no styling using NGINX #602

New issue

Open

opened 2026-02-26 18:47:45 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 18:47:45 +03:00

Owner

Originally created by @ekatzhms on GitHub (Oct 24, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/2099

I installed the system on an Ubuntu using NGINX, the content of the page rendered, but all of the static assets, like css are getting a 404.

Here's my nginx config:

`server {
server_name documenso.cloudpress.host;

root /var/www/documenso;

location / {
    proxy_pass http://localhost:3000;
    proxy_http_version 1.1;
    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_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
}

#    location ^~ /app/ {
#    alias /var/www/documenso/apps/remix/app/;   # note trailing slash
#   try_files $uri =404;
    # If other locations have auth/IP rules, keep this public:
#    auth_basic off;
#}

listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/documenso.cloudpress.host/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/documenso.cloudpress.host/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

}
server {
if ($host = documenso.cloudpress.host) {
return 301 https://$host$request_uri;
} # managed by Certbot

listen 80;
server_name documenso.cloudpress.host;
return 404; # managed by Certbot

}
`

anyone have any suggestions?

Originally created by @ekatzhms on GitHub (Oct 24, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/2099 I installed the system on an Ubuntu using NGINX, the content of the page rendered, but all of the static assets, like css are getting a 404. Here's my nginx config: `server { server_name documenso.cloudpress.host; root /var/www/documenso; location / { proxy_pass http://localhost:3000; proxy_http_version 1.1; 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_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } # location ^~ /app/ { # alias /var/www/documenso/apps/remix/app/; # note trailing slash # try_files $uri =404; # If other locations have auth/IP rules, keep this public: # auth_basic off; #} listen 443 ssl; # managed by Certbot ssl_certificate /etc/letsencrypt/live/documenso.cloudpress.host/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/documenso.cloudpress.host/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot } server { if ($host = documenso.cloudpress.host) { return 301 https://$host$request_uri; } # managed by Certbot listen 80; server_name documenso.cloudpress.host; return 404; # managed by Certbot } ` anyone have any suggestions?

kerem added the

Stale

status: triage

labels

2026-02-26 18:47:45 +03:00

kerem commented

2026-02-26 18:47:45 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Oct 24, 2025):

Thank you for opening your first issue and for being a part of the open signing revolution!

One of our team members will review it and get back to you as soon as it possible 💚

Meanwhile, please feel free to hop into our community in Discord

@github-actions[bot] commented on GitHub (Oct 24, 2025): Thank you for opening your first issue and for being a part of the open signing revolution! <br /> One of our team members will review it and get back to you as soon as it possible 💚 <br /> Meanwhile, please feel free to hop into our community in [Discord](https://documen.so/discord)

kerem referenced this issue

2026-02-26 19:31:43 +03:00

[PR #602] [CLOSED] fix(web): fix stale documents list by forcing refresh after uploading #1072

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/documenso#602

No description provided.

Rows
Columns