Closed stephen-dahl closed 6 years ago
You don't have the ELB setup properly. It needs to be TLS->TCP and have proxy protocol enavles. The API returns absolute URLs, which the UI follows, and the server needs to get enough information to reconstruct the original request URL to generate them.
http://rancher.com/docs/rancher/v1.6/en/installing-rancher/installing-server/basic-ssl-config/#elb
I had those set up before, my problem is I had it running on port 80 before and changed to 8080 now, that means my proxy policy is no longer applying since it was set to 80. Closing
o and thanks :)
Rancher versions: rancher/server:stable rancher/agent: NA
Infrastructure Stack versions: healthcheck: NA ipsec: NA network-services: NA scheduler: NA kubernetes (if applicable): no
Docker version: (
docker version
,docker info
preferred)Operating system and kernel: (
cat /etc/os-release
,uname -r
preferred)4.4.0-1047-aws
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO) AWS
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB) single node
Environment Template: (Cattle/Kubernetes/Swarm/Mesos) cattle
Steps to Reproduce:
docker-compose up -d
this server sits behind an aws elb performing ssl terminationResults: ui load but some api calls are not using https and being blocked by the browser.