Your browser was unable to load all of the resources. They may have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.

agent can not access the server #4149

CaoFangyuan ·

Hi Robin,

We plan to add one agent into the quick build server, after finish the install process, the connection shows the below error. We have checked out firewall setting, there is no firewall blocking. We are gating the process by this error for now, do you have any idea?

Error connecting server: Failed to send access token from server to agent . Please make sure the agent is reporting the correct IP address and there is no firewall blocking connection from server to this agent.

  • solved #9
  • replies 8
  • views 993
  • stars 0
robinshen ADMIN ·

Does the error message prints ip address of the agent? If so, please run below from server to make sure it works:
telnet 8811

CaoFangyuan ·

Hi Robin,

We tried, but failed.
Capture.PNG

robinshen ADMIN ·

Looks like the port 8811 on 10.239.94.98 is not open to QB server. Please check firewall setting on the agent.

CaoFangyuan ·

Hi Robin,

We contacted our lab firewall owner and he said this port has been opened. Does there have any other reason that may cause this error? Thanks.

robinshen ADMIN ·

It is a clear issue of the network or firewall if you can not telnet to the agent from server. Or is "10.239.94.98" intended ip address of the build agent?

CaoFangyuan ·

yes, "10.239.94.98" is the ip address of the build agent. I will check the firewall rule again. Thanks

CaoFangyuan ·

Hi Robin,

I have checked with IT, they said that the port 8811 is opened in the firewall. and they let me to check is the port is lessening or not in destination server end. Do you know how can I check that? Thanks.

robinshen ADMIN ·

Please check /conf/node.properties to see if you've specified bindAddress property. Without this setting, the port will listen on all addresses; otherwise it will only listen on specified address. If you have that property, just comment it out and restart QB agent.

To verify, run below on agent to see if it works:
telnet 10.239.94.98 8811