Thanks for the pointer,

for those using apache the setting is

ProxyPreserveHost On

This seems to fix the issue


On 24 Jun 2014, at 09:21, Juraci Paixão Kröhling <> wrote:

Hash: SHA512

Are you sending the proper host/protocol/... headers to Wildfly? In
nginx, it would be something like this:

proxy_pass http://localhost:8080;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto https;
proxy_set_header Host $http_host;

- - Juca.

On 06/24/2014 08:39 AM, Conrad Winchester wrote:
Hi all,

I made some progress. This was apparently occurring because I had 
lingering Wildly Processes. I killed them all, cleaned up,
restarted and was able to see my keycloak welcome screen at


through my reverse proxy - nice!

Unfortunately, when I click to go through to the administration
console I end up at


I am having difficulty changing the (localhost:8080). Can anybody
please advise



On 23 Jun 2014, at 20:10, Conrad Winchester < 
<>> wrote:

Hi all,

I have been using keycloak in development for a couple of weeks
now and it has been running fine.

I now need to deploy it into a UAT environment, but after
installing wildly and integrating keycloak I get an issue when
starting up.

Basically everything starts fine, but auth-server is immediately 

2014-06-23 19:49:36,038 INFO  [] (Controller Boot
Thread) JBAS015961: Http management interface listening on 2014-06-23 19:49:36,038 INFO
[] (Controller Boot Thread) JBAS015951: Admin console
listening on <> 
2014-06-23 19:49:36,038 INFO  [] (Controller Boot
Thread) JBAS015874: WildFly 8.1.0.Final "Kenny" started in 8047ms
- Started 303 of 356 services (91 services are lazy, passive or
on-demand) 2014-06-23 19:49:41,051 INFO
[org.wildfly.extension.undertow] (MSC service thread 1-3)
JBAS017535: Unregistered web context: /auth 2014-06-23
19:49:41,104 INFO  [] (ServerService Thread Pool
-- 21) JBAS011410: Stopping Persistence Unit (phase 2 of 2) 
Service 'auth-server.war#jpa-keycloak-identity-store' 2014-06-23
19:49:41,104 INFO  [] (ServerService Thread Pool
-- 22) JBAS011410: Stopping Persistence Unit (phase 2 of 2) 
Service 'auth-server.war#jpa-keycloak-audit-store' 2014-06-23
19:49:41,106 INFO  [org.jboss.weld.deployer] (MSC service thread
1-4) JBAS016009: Stopping weld service for deployment 
auth-server.war 2014-06-23 19:49:41,128 INFO  []
(ServerService Thread Pool -- 22) JBAS011410: Stopping
Persistence Unit (phase 1 of 2) Service
'auth-server.war#jpa-keycloak-identity-store' 2014-06-23
19:49:41,129 INFO  [] (ServerService Thread Pool
-- 21) JBAS011410: Stopping Persistence Unit (phase 1 of 2) 
Service 'auth-server.war#jpa-keycloak-audit-store' 2014-06-23
19:49:41,141 INFO  [] (MSC service
thread 1-1) JBAS015877: Stopped deployment auth-server.war 
(runtime-name: auth-server.war) in 96ms 2014-06-23 19:49:41,175
INFO  [] (DeploymentScanner-threads - 2)
JBAS018558: Undeployed "auth-server.war" (runtime-name:
"auth-server.war") 2014-06-23 19:49:46,178 INFO
(DeploymentScanner-threads - 1) JBAS015003: Found auth-server.war
in deployment directory. To trigger deployment create a file
called auth-server.war.dodeploy

The main difference between this and dev is that in UAT keycloak
has to be behind an apache proxy

ProxyPass /auth/ http://localhost:8080/auth/ ProxyPassReverse
/auth/ http://localhost:8080/auth/

Can anybody help? I am completely stumped - Is it something to do
with apache already running on port 80?


Conrad _______________________________________________ 
keycloak-user mailing list

_______________________________________________ keycloak-user
mailing list

Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird -

keycloak-user mailing list