Yes, see this:
https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+IIS
That procedure works for us.
Terry
On Tuesday, January 22, 2019 at 10:29:39 AM UTC-7, Chad Ruppert wrote:
>
> Terry, did you ever get this resolved?
>
>>
--
You received this message because you are subscribed
Terry, did you ever get this resolved?
On Friday, June 2, 2017 at 10:17:28 AM UTC-4, Terry Lacy wrote:
>
> Thanks, Stephen.
>
> Yes, I would certainly like to fix it. I'm sure it will break something
> down the road. But I can't find a working configuration anywhere.
>
> Any. Where.
>
> Terry
>
Thanks, Stephen.
Yes, I would certainly like to fix it. I'm sure it will break something
down the road. But I can't find a working configuration anywhere.
Any. Where.
Terry
On Thursday, June 1, 2017 at 5:10:46 PM UTC-6, Stephen Connolly wrote:
>
> I do not have easy access to a windows machin
I do not have easy access to a windows machine, so I cannot help with
configuration of that
I should be possible to configure it correctly, if the warning is showing
then you will find some features don't work, so I recommend trying to fix it
On Thu 1 Jun 2017 at 17:22, Terry Lacy wrote:
>
> Aft
After pursuing this in this forum for over a month, posting a bug and
having it promptly closed as "not a defect", and no working solution, I'm
left to conclude that it is not possible to get rid of the "your reverse
proxy set up is broken" with recent versions of Jenkins and IIS.
Or, nobody h
Thanks for your reply, Stephen.
Here's the IIS web.config file. Does anyone know how the rewrite rule
should be configured for Jenkins?
http://localhost:8080/{R:1}";
/>
https://our.server.name/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/testForReverseProxySetup/https%3A%2F%2Four.server.name%2Fmanage/
Looks like the URL rewrite rule is setup wrong and is double prefix with
https://...
On Thu 25 May 2017 at 20:45, Terry Lacy wrote:
> Here's so
Here's some extra information I haven't posted before.
The wiki page linked from the "More Info" button (
https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+says+my+reverse+proxy+setup+is+broken)
says this curl command will provide more info:
curl -iL -e http://your.reverse.proxy/jenkins/manag
I posted a bug (https://issues.jenkins-ci.org/browse/JENKINS-44239), and it
was resolved as "not a defect", so I'm back here, still looking for a
solution.
Does anyone here run Jenkins behind IIS? Are you using a recent version?
Are you able to get rid of the "It appears that your reverse proxy
Since there doesn't seem to be a solution to this, would y'all advise that
I post a bug report?
Terry
On Wednesday, May 3, 2017 at 12:45:40 PM UTC-6, Terry Lacy wrote:
>
> Okay, we verified that ipv6 was disabled on the network interface. We also
> changed the IIS reverse proxy to point to "127
Okay, we verified that ipv6 was disabled on the network interface. We also
changed the IIS reverse proxy to point to "127.0.0.1:8080" instead of
"localhost:8080". That didn't make any difference.
On Wednesday, May 3, 2017 at 11:28:34 AM UTC-6, Terry Lacy wrote:
>
> For whatever it's worth, addin
By all appearances, the reverse proxy is working. However, we haven't done
really extensive testing yet. I've just done a couple of builds and tested
with one slave.
So, yeah, so far, it's just the message on the Jenkins Manage Jenkins page.
However, I'm assuming the message is there for a rea
I wondered about that too. I'll get with our SA and see. I wonder whether
it'd be better to use "127.0.0.1" in the configuration instead of
"localhost"
On Wednesday, May 3, 2017 at 11:28:34 AM UTC-6, ok999 wrote:
>
> Is there an ip v6 enabled as well?
>
>
> On Mon, May 1, 2017 at 1:16 PM Terry
Does this means that your reverse proxy is not working?
And not just the error on the jenkins page
On Wed, May 3, 2017 at 12:28 PM Terry Lacy wrote:
> For whatever it's worth, adding another "/" to that URL still results in a
> 404.
>
> Terry
>
> On Wednesday, May 3, 2017 at 10:39:04 AM UTC-6, S
Is there an ip v6 enabled as well?
On Mon, May 1, 2017 at 1:16 PM Terry Lacy wrote:
> I'm not sure if this is useful information, but we see this in the
> jenkins-stderr logs when browsing to the Manage Jenkins page:
>
> 01-May-2017 12:10:39.038 WARNING [Handling GET
> /administrativeMonitor/hu
For whatever it's worth, adding another "/" to that URL still results in a
404.
Terry
On Wednesday, May 3, 2017 at 10:39:04 AM UTC-6, Stephen Connolly wrote:
>
>
> On 3 May 2017 at 16:30, Terry Lacy >
> wrote:
>
>>
>> /administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/testForRever
Hi, Stephen,
Thanks for your reply. I don't have any ideas on why it would be converting
the URL that way. Could be an URL encoding issue, but I have no idea how
to fix it.
Terry
On Wednesday, May 3, 2017 at 10:39:04 AM UTC-6, Stephen Connolly wrote:
>
>
> On 3 May 2017 at 16:30, Terry Lacy >
On 3 May 2017 at 16:30, Terry Lacy wrote:
> /administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/
> testForReverseProxySetup/https:/our.server.name/manage/
>
That looks to be the malformed url. you should want to see why it is
converting the URL to "https:/our.server.name" and not "
Summarizing this and adding a little information. We still don't have a
solution.
We're still getting "It appears that your reverse proxy set up is broken."
on the Manage Jenkins page.
Jenkins 2.46.2 .war file
Tomcat 8.5.14.
Windows Server 2012 R2 Datacenter 64-bit
IIS 8.5
Java 1.8.0_131 6
Here's our current web.config file for IIS:
http://localhost:8080/{R:1}"; />
I'm not sure if this is useful information, but we see this in the
jenkins-stderr logs when browsing to the Manage Jenkins page:
01-May-2017 12:10:39.038 WARNING [Handling GET
/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/testForReverseProxySetup/https:/
our.server.name/manage/
Hi, Stephen. Thanks for your reply.
I'm not sure about X-Forwarded-Host. I think we tried that, but I'll have
to check with our SA, and he's not here right now. I'll get back here as
soon as I find out.
We did try a couple of iterations where we tried to redirect
https://our.server.name/ to ht
On Mon 1 May 2017 at 16:13, Terry Lacy wrote:
> Is there other information I could supply that would help?
>
> Alternatively, has anyone successfully set up Jenkins behind IIS with a
> setup similar to that described below *without* getting the bad proxy
> message? Would you be willing to share y
Is there other information I could supply that would help?
Alternatively, has anyone successfully set up Jenkins behind IIS with a
setup similar to that described below *without* getting the bad proxy
message? Would you be willing to share your setup?
So far, things seem to work fine despite th
Hi,
Sorry if this has been answered before.
We're having a very difficult time trying to get an IIS reverse proxy
working with Jenkins. No matter what we try, we still get the "It appears
that your reverse proxy set up is broken" message on the Manage Jenkins
page.
We've seen a few links des
25 matches
Mail list logo
