# Proxy Setup - Well Known config urls

**URL:** <https://forum.keycloak.org/t/proxy-setup-well-known-config-urls/8353>\
**Category:** Getting advice\
**Tags:** admin-console, oidc\
**Created:** [April 7, 2021, 10:35am UTC](https://forum.keycloak.org/t/proxy-setup-well-known-config-urls/8353 "2021-04-07T10:35:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kcuser](https://avatars.discourse-cdn.com/v4/letter/k/71c47a/32.png) [@kcuser](https://forum.keycloak.org/u/kcuser)\
**Post date:** [April 7, 2021, 10:35am UTC](https://forum.keycloak.org/t/proxy-setup-well-known-config-urls/8353/1 "2021-04-07T10:35:11Z")

</div>

Hi, I’ve been attempting to setup a proxy in front of my dev version of keycloak that runs in a docker container on Windows, I set the env var on setup of the container in preparation:

`-e PROXY_ADDRESS_FORWARDING=true`

And I’ve been into the admin area to set the front end url for the specific realm, eg:

`KEYCLOAK_FRONTEND_URL = http://auth.example.com`

And cleared all the cache for the realm but when I check the well-known config file, some of the URLs still include the localhost:8080 domain:

```
{
  "issuer": "http://auth.example.com/auth/realms/testing",
  "authorization_endpoint": "http://auth.example.com/auth/realms/testing/protocol/openid-connect/auth",
  "token_endpoint": "http://localhost:8080/auth/realms/testing/protocol/openid-connect/token",
  "introspection_endpoint": "http://localhost:8080/auth/realms/testing/protocol/openid-connect/token/introspect",
  "userinfo_endpoint": "http://localhost:8080/auth/realms/testing/protocol/openid-connect/userinfo",
  "end_session_endpoint": "http://auth.example.com/auth/realms/testing/protocol/openid-connect/logout",
  "jwks_uri": "http://localhost:8080/auth/realms/testing/protocol/openid-connect/certs",
  "check_session_iframe": "http://auth.example.com/auth/realms/testing/protocol/openid-connect/login-status-iframe.html",
  "grant_types_supported": [....

```

Am I missing something, I would have thought my changes would have been used for all urls above (and the other 2 further down in the well-known config).

Thanks,  
Steve

---

<div class="post-metadata">

**Author:** ![kcuser](https://avatars.discourse-cdn.com/v4/letter/k/71c47a/32.png) [@kcuser](https://forum.keycloak.org/u/kcuser)\
**Post date:** [April 7, 2021, 11:13am UTC](https://forum.keycloak.org/t/proxy-setup-well-known-config-urls/8353/2 "2021-04-07T11:13:00Z")

</div>

Ok I’ve figured it out, I had to edit the standalone-ha.xml file on the container to set the value for `forceBackendUrlToFrontendUrl` to be true, I saw this bit in the docs which led to some searching and then finding that the docker container uses the standalone-ha.xml by default:

 ![backend](https://global.discourse-cdn.com/free1/uploads/keycloak/original/2X/8/83872b49de6d945744eff18e4017f1590f5995b4.png)

My next task is to figure out how I can run the proxy from something like [auth.example.com](http://auth.example.com) which internally points directly to the realm in question, a bit like is described here:  
[https://github.com/keycloak/keycloak-community/blob/master/design/hostname-default-provider.md](https://github.com/keycloak/keycloak-community/blob/master/design/hostname-default-provider.md)

I’m finding the docs exhaustive but a little tough to penetrate solving particular issues but nevertheless things are impressive so far on the whole.