getting rid of rancher from nginx network as could be impacting cluster creation

This commit is contained in:
talksik
2023-08-14 18:06:05 -07:00
parent 6a0adf5bf7
commit 78fef17a6b
2 changed files with 3 additions and 31 deletions
+3 -2
View File
@@ -34,6 +34,7 @@ services:
image: rancher/rancher:latest
restart: unless-stopped
container_name: rancher
ports:
- 2000:80
- 2001:443
privileged: true
networks:
- nginx
-29
View File
@@ -68,35 +68,6 @@ http {
}
}
server {
listen 80;
server_name rancher.flowy.live;
location / {
proxy_pass http://rancher:80;
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;
}
}
server {
listen 443 ssl;
server_name rancher.flowy.live;
# RSA certificate
ssl_certificate /etc/letsencrypt/live/flowy.live/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/flowy.live/privkey.pem; # managed by Certbot
location / {
proxy_pass https://rancher;
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;
}
}
# k8s api: passthrough grpc/tcp
# server {
# listen 80 http2;