Loading...

This issue is archived. You can view it, but you can't modify it. Learn more

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: Blocker
Component/s: core
Labels:
Environment:
1.498+, Windows Server 2008 R2

All of my windows salve cannot connect to Jenkins master after upgrading to 1.498. Following messages showed up in slaves' jenkins-slave.err:

java.io.IOException: Failed to load http://192.168.30.95/jenkins/computer/Fortify%201/slave-agent.jnlp: 403 Forbidden
at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:238)
at hudson.remoting.Launcher.run(Launcher.java:200)
at hudson.remoting.Launcher.main(Launcher.java:173)

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List
  - Download All

jenkins-slave-error.jpg
37 kB
2013-01-08 02:31

depends on

JENKINS-9679 NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option

Closed

JENKINS-4071 jnlp slaves doesn't support HTTP Auth

Closed

is duplicated by

JENKINS-16346 Upgrade to Jenkins ver. 1.499 breaks master/slave connection

Resolved

JENKINS-16272 LTS 1.480.2 breaks launching slaves via jnlp

Closed

is related to

JENKINS-14610 Full Admin rights needed to run slave WebStart

Resolved

Assignee:: Unassigned
Reporter:: Pei-Tang Huang

Created:: 2013-01-08 01:59
Updated:: 2025-11-25 10:21
Resolved:: 2013-01-21 22:18
Archived:: 2025-11-25 10:21

Details

Description

Attachments

Attachments

Issue Links

Activity

People

Dates