zitiLogin.. connection refused

Back to the login now... where I am getting a different error message.

$ zitiLogin

The connection to the server instance-20220317-1005:1280 was refused - did you specify the right host or port?

One thing that I needed to do that may have caused this was to upgrade the golang server
Apparently it did not want to run on V1.16.. so I upgraded it to 1.18.. which too me a while to work out..

Let me know if you have any tips

Hmm… I am thinking I may need to remove the .ziti folder and try again… I thought I deleted the identity… but maybe there was something still hanging around

[ 14.716] ERROR edge/controller/model.(*IdentityHandler).CreateWithEnrollments.func1: {error=[duplicate value ‘reflectClient’ in unique index on identities store]} could not create identity in bolt storage
[41611.420] INFO : http: TLS handshake error from 10.0.0.41:58238: remote error: tls: bad certificate
[50117.938] INFO : http: TLS handshake error from 10.0.0.41:58854: remote error: tls: bad certificate
[50630.822] INFO : http: TLS handshake error from 10.0.0.41:58908: remote error: tls: bad certificat

These are the types of reasons why I don’t remove the entire folder and delete services, config etc. The second error looks to me like a connected tunneling app is trying to connect but cannot because the pki was replaced, thus the controller won’t permit the tunneler to attach.

1 Like

As for golang 18, that’s a new one for me. I’ve not had that particular issue yet. Are you building the code yourself? I wouldn’t have expected you to even need go to run things…

Thanks… now that I reread the error… it makes sense… I have reinstalled it so many times… its time to just restart from the top…

In relation to golang… I thought I had everything in place for the reflect server client example… then… as I run the main.go file… it said that a module was not compatible with v.1.6… this was the default version Oracle provides with its yum service…

That triggered a whole bunch of things as I needed to install git and then work out how to migrate the golang server into the right folder… all done now though… the first time is always the hardest

What I preparing for a situation where I zitify an application server like Apache… and then use it to host applications on the dark side of the net… this is probably a month away at this stage

Oooh. It wasn’t clear to me you were running the reflect example. That would need go 1.17+ so yes, now that makes total sense.

1 Like

Quick update.. I deleted the .ziti folder and rerun everything.

Success :slight_smile:

go run main.go server -i reflectServer.json -s reflect
INFO ready to accept connections
INFO connection to edge router using api session token .......

1 Like