got rid of some crap in unixsocket.jinja2, and fixed a but in ssl_socket that ceated a Error: duplicate listen options for [::]:443
sss
This commit is contained in:
parent
6a5e97c4c5
commit
a3189d2cd1
2 changed files with 5 additions and 8 deletions
|
|
@ -1,6 +1,6 @@
|
||||||
|
|
||||||
upstream app_server_{{ extended_name }} {
|
upstream app_server_{{ extended_name }} {
|
||||||
# fail_timeout=0 means we always retry an upstream even if it failed
|
# fail_timeout=0 means we always retry an upstream even if it failed
|
||||||
# to return a good HTTP response
|
# to return a good HTTP response
|
||||||
|
|
||||||
# for UNIX domain socket setups
|
# for UNIX domain socket setups
|
||||||
|
|
@ -49,7 +49,10 @@ server {
|
||||||
root html;
|
root html;
|
||||||
}
|
}
|
||||||
|
|
||||||
listen [::]:443 ssl ipv6only=on; # managed by Certbot
|
# this breaks down with multiple domains using ssl
|
||||||
|
# so I'm commenting it out
|
||||||
|
# listen [::]:443 ssl ipv6only=on; # managed by Certbot
|
||||||
|
|
||||||
listen 443 ssl; # managed by Certbot
|
listen 443 ssl; # managed by Certbot
|
||||||
ssl_certificate /etc/letsencrypt/live/{{server_name}}/fullchain.pem; # managed by Certbot
|
ssl_certificate /etc/letsencrypt/live/{{server_name}}/fullchain.pem; # managed by Certbot
|
||||||
ssl_certificate_key /etc/letsencrypt/live/{{server_name}}/privkey.pem; # managed by Certbot
|
ssl_certificate_key /etc/letsencrypt/live/{{server_name}}/privkey.pem; # managed by Certbot
|
||||||
|
|
|
||||||
|
|
@ -1,9 +1,3 @@
|
||||||
# upstream django_bastardo {
|
|
||||||
# # server unix:///path/to/your/mysite/mysite.sock; # for a file socket
|
|
||||||
# #server unix:///tmp/uwsgi_replyall.sock; # for a file socket
|
|
||||||
# server 127.0.0.1:8002; # for a web port socket (we'll use this first)
|
|
||||||
# }
|
|
||||||
|
|
||||||
upstream app_server_{{ extended_name }} {
|
upstream app_server_{{ extended_name }} {
|
||||||
# fail_timeout=0 means we always retry an upstream even if it failed
|
# fail_timeout=0 means we always retry an upstream even if it failed
|
||||||
# to return a good HTTP response
|
# to return a good HTTP response
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue