I experienced the same issue on Ubuntu 12.04.3 after upgrading to 1.533 from the official repository. I do not know what my previous version was, but it had been updated at some point since mid-August so it was a relatively recent version.
Commenting out the PROXY__HEADER line allowed Jenkins to launch as expected and everything seems to work normally at this point. I am just using the internal authentication, config options selected under Global Security are "Jenkins’s own user database", "Logged-in users can do anything", and "Default Crumb Issuer" with proxy compatibility disabled. Unfortunately this doesn't seem like it'll help Boris, but it might be useful for anyone looking in to why the upgrade leaves the system broken. On Wednesday, September 25, 2013 1:37:33 PM UTC-4, Ullrich Hafner wrote: > Ok, I see. The conflicting part is in Jenkins core. > > Please remove the following block and restart: > > <crumbIssuer class="hudson.security.csrf.DefaultCrumbIssuer"> >> <excludeClientIPFromCrumb>false</excludeClientIPFromCrumb> >> <PROXY__HEADER>X-Forwarded-For</PROXY__HEADER> >> </crumbIssuer> >> > > Did you upgrade Jenkins? Or is this a new installation? Which Jenkins > version? > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
