Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have Apache 2.2. installed with SSL. It is running as a reverse proxy based on a question I asked and was answered here: Apache SSL reverse proxy for multiple servers What I discovered, however, is that the "sign in" prompt in Liferay no longer will authenticate. In FF I am given a security warning but my userid and password does not work. In other browsers, no security warning is given, but the authentication fails. Yet, if I use the IP address in the ProxyPass directives to go to the web page and then sign in, all is well. I assumed that Apache is passing all traffic back to the server unencrypted.

So, I am guessing that the data is getting mangled (somehow) in the ProxyPass directives so that Liferay cannot read the data. Is there another directive I need to add to the VirtualHost entry so that the data is passed unencrypted (or unmangled) to Liferay?

So, based on the post referenced above, when I go to I am redirected to which is properly hitting the server but the authentication fails. If I go directly to I can authenticate just fine. So somewhere in the https:// to http:// translation, something is getting hammered (I think).

Did I miss something in the VirtualHost directive that is messing up the authentication?


share|improve this question

I know this is old, but I think for this one, I would recommened trying out:


in the

share|improve this answer
I don't know for sure if this took care of the issue but I did add the directive and it is now working. Thanks. – Pete Helgren Apr 24 '13 at 19:58

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.