loud-keyboard-84117
03/03/2022, 12:52 PMdamp-sunset-69236
03/03/2022, 2:24 PMloud-keyboard-84117
03/03/2022, 2:29 PMdamp-sunset-69236
03/03/2022, 2:30 PMloud-keyboard-84117
03/03/2022, 2:33 PMdamp-sunset-69236
03/03/2022, 2:35 PMloud-keyboard-84117
03/03/2022, 2:38 PMdamp-sunset-69236
03/03/2022, 2:39 PMloud-keyboard-84117
03/03/2022, 2:41 PMdamp-sunset-69236
03/03/2022, 2:41 PMloud-keyboard-84117
03/03/2022, 2:48 PMerror=map[message:neither remote address nor any x-forwarded-for values match CIDR ranges [127.0.0.1/32]: [172.19.0.1], ranges, check)]
and
error=map[message:can not serve request over insecure http]
To tackle 2nd one, I'm using https connection on 127.0.0.1:8080 but I'm unaware of the 1st one.
My nginx rules are:
location /auth-admin{
proxy_set_header X-Forwarded-Proto $thescheme;
proxy_pass <http://127.0.0.1:9000/>;
}
location /auth-public{
proxy_set_header X-Forwarded-Proto $thescheme;
proxy_pass <http://127.0.0.1:9001/>;
}
location /idp-admin {
proxy_set_header X-Forwarded-Proto $thescheme;
proxy_pass <http://127.0.0.1:4433/>;
}
location /idp-public {
proxy_set_header X-Forwarded-Proto $thescheme;
proxy_pass <http://127.0.0.1:4434/>;
}
damp-sunset-69236
04/08/2022, 6:26 AMallow_termination_from:
- 127.0.0.1/32
and add your internal network range of your load balancersloud-keyboard-84117
04/08/2022, 8:11 AMSERVE_TLS_ALLOW_TERMINATION_FROM_0=127.0.0.1/32
damp-sunset-69236
04/08/2022, 8:37 AM172.19.0.1
It’s an example I found in your logsloud-keyboard-84117
04/08/2022, 11:13 PM/oauth2/auth?response_type=code&redirect_uri=http%
instead of /auth-public/oauth2/auth?response_type=code&redirect_uri=http%
Trying to figure out what config can I override.