Files
regress/deploy/nginx-regress-domain.conf
T
ssmithx 927997543d Move to dedicated regress.atobitcoin.io subdomain
DNS now exists for the subdomain, so retired the podsteadr.atobitcoin.io/regress/
path-prefix arrangement in favor of a clean root deployment on its own
domain: real Let's Encrypt cert (certbot certonly --webroot, same method
as podsteadr's own cert), independent nginx server blocks, no more
ROUTE_PREFIX/VITE_BASE needed for the live deploy (though still supported
and tested for future use elsewhere). Removed the now-dead /regress/
location from podsteadr's own nginx config.
2026-08-05 15:07:38 +00:00

41 lines
1.4 KiB
Plaintext

# /etc/nginx/sites-available/regress-domain on 23.182.128.130 (same host as
# podsteadr, but a fully separate nginx site/server_name — not sharing
# podsteadr's config file). Symlinked into sites-enabled as regress-domain.
#
# Cert obtained via: certbot certonly --webroot -w /var/www/html
# -d regress.atobitcoin.io
# (same webroot/method already used for podsteadr's own cert on this host;
# renews automatically via the existing certbot timer).
server {
listen 80;
listen [::]:80;
server_name regress.atobitcoin.io;
location /.well-known/acme-challenge/ {
root /var/www/html;
}
location / {
return 301 https://$host$request_uri;
}
}
server {
listen 443 ssl;
listen [::]:443 ssl;
server_name regress.atobitcoin.io;
ssl_certificate /etc/letsencrypt/live/regress.atobitcoin.io/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/regress.atobitcoin.io/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;
location / {
proxy_pass http://127.0.0.1:8199;
proxy_http_version 1.1;
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;
}
}