62506f10b4
Deploy to VPS / deploy (push) Has been cancelled
The site was redirecting / -> https://rf-flux.com:3000/en, where :3000 is the container's internal port (only "expose"d, not published) — so the browser saw ERR_CONNECTION_REFUSED. Root cause: when running behind Nginx in standalone mode, Next.js (via next-intl in this case) can build absolute redirect URLs that leak the container's internal PORT/HOSTNAME env into the Location header. TWO LAYERS OF DEFENCE 1. Nginx (nginx/conf.d/flux.conf) - Adds X-Forwarded-Host + X-Forwarded-Port so the upstream knows the public port (443) and host - proxy_redirect rewrites any Location header that still slips through with :3000 back to the public https://$host 2. Middleware (src/proxy.ts) - sanitizeRedirectLocation() runs after handleI18nRouting and scrubs Location headers that point at internal hostnames (app / localhost / 0.0.0.0) or the container port :3000, replacing them with the public host derived from x-forwarded-host / host header. Either layer alone would fix the immediate symptom; together they also prevent the same class of bug from showing up in any future redirect path.
191 lines
6.6 KiB
Plaintext
191 lines
6.6 KiB
Plaintext
limit_req_zone $binary_remote_addr zone=api:10m rate=10r/s;
|
|
limit_req_zone $binary_remote_addr zone=login:10m rate=5r/s;
|
|
|
|
upstream nextjs {
|
|
server app:3000;
|
|
keepalive 32;
|
|
}
|
|
|
|
server {
|
|
listen 80;
|
|
server_name rf-flux.com www.rf-flux.com;
|
|
|
|
location /.well-known/acme-challenge/ {
|
|
root /var/www/certbot;
|
|
}
|
|
|
|
location / {
|
|
return 301 https://$host$request_uri;
|
|
}
|
|
}
|
|
|
|
server {
|
|
listen 443 ssl;
|
|
http2 on;
|
|
client_max_body_size 500M;
|
|
server_name rf-flux.com www.rf-flux.com;
|
|
|
|
ssl_certificate /etc/letsencrypt/live/rf-flux.com/fullchain.pem;
|
|
ssl_certificate_key /etc/letsencrypt/live/rf-flux.com/privkey.pem;
|
|
ssl_protocols TLSv1.2 TLSv1.3;
|
|
ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384;
|
|
ssl_prefer_server_ciphers off;
|
|
ssl_session_timeout 1d;
|
|
ssl_session_cache shared:SSL:10m;
|
|
ssl_session_tickets off;
|
|
|
|
add_header Strict-Transport-Security "max-age=63072000; includeSubDomains; preload" always;
|
|
|
|
# Next.js bundles use content hashing — safe to cache forever
|
|
location /_next/static/ {
|
|
proxy_pass http://nextjs;
|
|
expires 365d;
|
|
add_header Cache-Control "public, immutable";
|
|
access_log off;
|
|
}
|
|
|
|
# Next.js image optimizer — short cache, browser revalidates
|
|
location /_next/image {
|
|
proxy_pass http://nextjs;
|
|
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_cache_bypass $http_upgrade;
|
|
add_header Cache-Control "public, max-age=300, must-revalidate" always;
|
|
}
|
|
|
|
location /hq-command/login {
|
|
limit_req zone=login burst=10 nodelay;
|
|
proxy_pass http://nextjs;
|
|
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;
|
|
}
|
|
|
|
# Asset uploads (large files, long timeout)
|
|
location /api/assets {
|
|
client_max_body_size 500M;
|
|
proxy_pass http://nextjs;
|
|
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_read_timeout 600s;
|
|
proxy_send_timeout 600s;
|
|
proxy_request_buffering off;
|
|
}
|
|
|
|
location /api/public-upload {
|
|
client_max_body_size 500M;
|
|
proxy_pass http://nextjs;
|
|
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_read_timeout 600s;
|
|
proxy_send_timeout 600s;
|
|
proxy_request_buffering off;
|
|
}
|
|
|
|
location /hq-command/ {
|
|
proxy_pass http://nextjs;
|
|
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;
|
|
}
|
|
|
|
location /api/chat {
|
|
limit_req zone=api burst=20 nodelay;
|
|
proxy_pass http://nextjs;
|
|
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_http_version 1.1;
|
|
proxy_set_header Connection '';
|
|
proxy_buffering off;
|
|
proxy_cache off;
|
|
proxy_read_timeout 120s;
|
|
}
|
|
|
|
location /api/health {
|
|
proxy_pass http://nextjs;
|
|
access_log off;
|
|
}
|
|
|
|
# ─────────────────────────────────────────────────────────────────
|
|
# User-uploaded assets — served directly from disk (bypass Next.js)
|
|
#
|
|
# Cache strategy: short max-age + must-revalidate.
|
|
# Browser caches for 5 minutes, then asks Nginx "did this change?"
|
|
# via If-Modified-Since. Nginx auto-replies 304 (Not Modified) if the
|
|
# file's mtime is unchanged, or serves the new file if it changed.
|
|
# This means new CMS uploads appear within ~5 min without rebuild
|
|
# AND saved bandwidth on unchanged files.
|
|
# ─────────────────────────────────────────────────────────────────
|
|
|
|
location /cases/ {
|
|
alias /srv/cases/;
|
|
add_header Cache-Control "public, max-age=300, must-revalidate" always;
|
|
access_log off;
|
|
}
|
|
|
|
location /applications/ {
|
|
alias /srv/applications/;
|
|
add_header Cache-Control "public, max-age=300, must-revalidate" always;
|
|
access_log off;
|
|
}
|
|
|
|
location /news/ {
|
|
alias /srv/news/;
|
|
add_header Cache-Control "public, max-age=300, must-revalidate" always;
|
|
access_log off;
|
|
}
|
|
|
|
location /parts/ {
|
|
alias /srv/parts/;
|
|
add_header Cache-Control "public, max-age=300, must-revalidate" always;
|
|
access_log off;
|
|
}
|
|
|
|
location /operations-inbox/ {
|
|
alias /srv/operations-inbox/;
|
|
add_header Cache-Control "private, max-age=60, must-revalidate" always;
|
|
access_log off;
|
|
}
|
|
|
|
location /footage/ {
|
|
alias /srv/footage/;
|
|
add_header Cache-Control "public, max-age=300, must-revalidate" always;
|
|
access_log off;
|
|
}
|
|
|
|
location /branding/ {
|
|
alias /srv/branding/;
|
|
add_header Cache-Control "public, max-age=300, must-revalidate" always;
|
|
access_log off;
|
|
}
|
|
|
|
location / {
|
|
proxy_pass http://nextjs;
|
|
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;
|
|
# Public-facing host + port so Next.js builds correct absolute
|
|
# redirect URLs (without leaking the internal container port 3000).
|
|
proxy_set_header X-Forwarded-Host $host;
|
|
proxy_set_header X-Forwarded-Port 443;
|
|
proxy_http_version 1.1;
|
|
proxy_set_header Upgrade $http_upgrade;
|
|
proxy_set_header Connection "upgrade";
|
|
|
|
# Strip any leaked container port from upstream redirects, just in
|
|
# case Next.js still builds Location headers with :3000.
|
|
proxy_redirect ~^https?://[^/:]+:3000(/.*)$ https://$host$1;
|
|
}
|
|
}
|