Open hanselke opened 7 years ago
Have encountered this before, but this is a more common use case.
I'm trying to relaunch my single instance, external DB rancher server behind RAP proxy. Cloudflare DNS is used as well.
sudo docker run -d --name=paas -e ROOT_URL=https://rancher.domain.com -e PORT=8080 -l rap.host=rancher.domain.com-l rap.port=8080 -l rap.proto=https -l rap.le_host=rancher.domain.com -l rap.le_email=infra@domain.com --restart=unless-stopped -p 8080 rancher/server:stable \ --db-host db --db-port 3306 --db-user root --db-pass dbpass --db-name rancherserver
So from what i understand, RAP should be proxing rancher.domain.com port 80 as well as 443 requests via https to port 8080.
RAP has managed to get a letsencrypt cert as i can find it in /etc/nginx/letsencrypt
Now the issue is whenver i hit rancher.domain.com:80, I just get into a redirect loop of GET / HTTP/1.1
Got same error and it came from a .htaccess file
don't mind me just passing through...
missing a space...after .com
Have encountered this before, but this is a more common use case.
I'm trying to relaunch my single instance, external DB rancher server behind RAP proxy. Cloudflare DNS is used as well.
sudo docker run -d --name=paas -e ROOT_URL=https://rancher.domain.com -e PORT=8080 -l rap.host=rancher.domain.com-l rap.port=8080 -l rap.proto=https -l rap.le_host=rancher.domain.com -l rap.le_email=infra@domain.com --restart=unless-stopped -p 8080 rancher/server:stable \ --db-host db --db-port 3306 --db-user root --db-pass dbpass --db-name rancherserver
So from what i understand, RAP should be proxing rancher.domain.com port 80 as well as 443 requests via https to port 8080.
RAP has managed to get a letsencrypt cert as i can find it in /etc/nginx/letsencrypt
Now the issue is whenver i hit rancher.domain.com:80, I just get into a redirect loop of GET / HTTP/1.1