How can agent connect to go server over port 8154.

[toper halo]

I've got go server that listens to port 8154. Port 8153 is blocked. 

There was a topic here: https://groups.google.com/forum/#!searchin/go-cd/ssl/go-cd/tImlyLCYbVQ/a0lCen1m4_gJ

And the guy had the same problem as mine. I red several times and couldn't find the clear understanding, how my agent config should look like.


Now it looks like this
root@x:/etc/default# cat go-agent
GO_SERVER=x.x.x.x
export GO_SERVER
GO_SERVER_SSL_PORT=8154
export GO_SERVER_SSL_PORT
AGENT_WORK_DIR=/var/lib/go-agent
export AGENT_WORK_DIR
DAEMON=Y
VNC=N
JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64/jre
export JAVA_HOME


I tried:
cat /etc/default/go-agent.backup
GO_SERVER=x.x.x.x
export GO_SERVER
GO_SERVER_PORT=8153
export GO_SERVER_PORT
GO_SERVER_SSL_PORT=8154
export GO_SERVER_SSL_PORT
AGENT_WORK_DIR=/var/lib/go-agent
export AGENT_WORK_DIR
DAEMON=Y
VNC=N
JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64/jre
export JAVA_HOME


I tried restarting agent, but still it tries to connect to 8153 port. I've got the same error output as in the topic on a link.

[toper halo]

Basically in my config I should say, bro use port 8154 and run over https but I don't know how.

[srinivas upadhya]

This should help: https://groups.google.com/d/msg/go-cd/ChPXb4oVwq0/Wv0w4BR0RmEJ

[Aravind SV]

Hmm, maybe I'm understanding this wrong. But, I don't think this is going to work. The Go Agent does need both ports (well, two configured ports). 8153 is used only once at the beginning, and then 8154 is used from then on.

On Thu, Jan 8, 2015 at 11:55 PM, srinivas upadhya <srinivas...@gmail.com> wrote:

This should help: https://groups.google.com/d/msg/go-cd/ChPXb4oVwq0/Wv0w4BR0RmEJ

--
You received this message because you are subscribed to the Google Groups "go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jyoti Singh]

I will just try and elaborate what others have been trying to tell.

As Aravind pointed out, agent needs to connect to server on two different ports, 8153 by default for http calls and 8154 by default for https ones. The port numbers for the above calls can be changed to anything you like, but the calls cannot be skipped. Meaning, the first few calls that agent makes to the server will be through http not https, and the later ones using https. This cannot be configured in any way to behave differently. So, if you have been meaning to do the above, it cannot be done.

The post that you originally linked is about being able to configure/change the port numbers for the above mentioned communications from 8153/8154 to 80/443, and that is very much possible.

Basically it requires changes at two places - one on the server machine and another on the agent. Exact steps have been mentioned in the link that Srinivas posted.