[JIRA] (JENKINS-39820) The server rejected the connection: None of the protocols were accepted

216 views
Skip to first unread message

halasson.m.simatupang@gdplabs.id (JIRA)

unread,
Nov 17, 2016, 7:55:02 AM11/17/16
to jenkinsc...@googlegroups.com
halasson simatupang created an issue
 
Jenkins / Bug JENKINS-39820
The server rejected the connection: None of the protocols were accepted
Issue Type: Bug Bug
Assignee: halasson simatupang
Components: swarm-plugin
Created: 2016/Nov/17 12:54 PM
Environment: Jenkins version 2.19.1
Priority: Minor Minor
Reporter: halasson simatupang

hello,

could you tel me why when my slave want connect to master using IP address master is success ?
and when i want connect to by domain provided it is show error.

i'm using swarm plugin.

Nov 17, 2016 7:08:34 PM hudson.remoting.jnlp.Main$CuiListener error
SEVERE: The server rejected the connection: None of the protocols were accepted
java.lang.Exception: The server rejected the connection: None of the protocols were accepted
at hudson.remoting.Engine.onConnectionRejected(Engine.java:366)
at hudson.remoting.Engine.run(Engine.java:338)

for example:
java -jar swarm-client-jar-with-dependencies.jar -master x.x.x.x (other parameter) => success

but
java -jar swarm-client-jar-with-dependencies.jar -master test.jenkins.id (other parameter) => is result error
Nov 17, 2016 7:13:34 PM hudson.remoting.jnlp.Main createEngine
INFO: Setting up slave: PHP-CSF-PROD
Nov 17, 2016 7:13:34 PM hudson.remoting.jnlp.Main$CuiListener <init>
INFO: Jenkins agent is running in headless mode.
Nov 17, 2016 7:13:34 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Locating server among https://******.id/
Nov 17, 2016 7:13:34 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Handshaking
Nov 17, 2016 7:13:34 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to ******.id:50000
Nov 17, 2016 7:13:34 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP3-connect
Nov 17, 2016 7:13:34 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Server didn't accept the handshake: HTTP/1.1 400 Bad Request
Nov 17, 2016 7:13:34 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to *********id:50000
Nov 17, 2016 7:13:34 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP2-connect
Nov 17, 2016 7:13:34 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Server didn't accept the handshake: HTTP/1.1 400 Bad Request
Nov 17, 2016 7:13:34 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to ********.id:50000
Nov 17, 2016 7:13:34 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP-connect
Nov 17, 2016 7:13:34 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Server didn't accept the handshake: HTTP/1.1 400 Bad Request
Nov 17, 2016 7:13:34 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to ********.id:50000
Nov 17, 2016 7:13:34 PM hudson.remoting.jnlp.Main$CuiListener error
SEVERE: The server rejected the connection: None of the protocols were accepted
java.lang.Exception: The server rejected the connection: None of the protocols were accepted
at hudson.remoting.Engine.onConnectionRejected(Engine.java:366)
at hudson.remoting.Engine.run(Engine.java:338)

i had verified the firewall and ok.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

jacob.keller@gmail.com (JIRA)

unread,
Dec 1, 2016, 2:55:05 PM12/1/16
to jenkinsc...@googlegroups.com
Jacob Keller commented on Bug JENKINS-39820
 
Re: The server rejected the connection: None of the protocols were accepted

I am having the same issue. I suspect it is because the remoting API in jenkins and the swarm client don't match.

me@basilcrow.com (JIRA)

unread,
Jun 1, 2019, 2:08:02 PM6/1/19
to jenkinsc...@googlegroups.com
Basil Crow assigned an issue to Unassigned
 
Change By: Basil Crow
Assignee: halasson simatupang
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
Reply all
Reply to author
Forward
0 new messages