Issue dashboard SSL per tenant instead of full cert sync.
Per-row Issue SSL now runs ssl-issue-tenant.sh for business/customer hosts only, with nginx cert map support, so one broken tenant cannot block others. Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
co-authored by
Cursor
parent
202ac7d4bd
commit
b7bce38131
@@ -46,8 +46,8 @@ server {
|
||||
server {
|
||||
listen 443 ssl;
|
||||
server_name ~^business\.(?<apex>.+)$;
|
||||
ssl_certificate /etc/letsencrypt/live/meshkee-dashboards/fullchain.pem;
|
||||
ssl_certificate_key /etc/letsencrypt/live/meshkee-dashboards/privkey.pem;
|
||||
ssl_certificate $meshkee_dashboard_ssl_cert;
|
||||
ssl_certificate_key $meshkee_dashboard_ssl_key;
|
||||
ssl_protocols TLSv1.2 TLSv1.3;
|
||||
|
||||
location / {
|
||||
@@ -59,8 +59,8 @@ server {
|
||||
server {
|
||||
listen 443 ssl;
|
||||
server_name ~^customer\.(?<apex>.+)$;
|
||||
ssl_certificate /etc/letsencrypt/live/meshkee-dashboards/fullchain.pem;
|
||||
ssl_certificate_key /etc/letsencrypt/live/meshkee-dashboards/privkey.pem;
|
||||
ssl_certificate $meshkee_dashboard_ssl_cert;
|
||||
ssl_certificate_key $meshkee_dashboard_ssl_key;
|
||||
ssl_protocols TLSv1.2 TLSv1.3;
|
||||
|
||||
location / {
|
||||
|
||||
Reference in New Issue
Block a user