# Rancher agent cannot connect with self-signed server cert **URL:** \ **Category:** Rancher 1.x\ **Created:** [May 10, 2016, 7:37am UTC](https://forums.suse.com/t/rancher-agent-cannot-connect-with-self-signed-server-cert/2728 "2016-05-10T07:37:32Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Jose\_Gato\_Luis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/jose_gato_luis/32/6587_2.png) [@Jose\_Gato\_Luis](https://forums.suse.com/u/Jose_Gato_Luis)\ **Post date:** [May 10, 2016, 7:37am UTC](https://forums.suse.com/t/rancher-agent-cannot-connect-with-self-signed-server-cert/2728/1 "2016-05-10T07:37:32Z")
I have been checking similar topics but I still not find the answer. I have rancher server running with SSL following instructions [here](http://docs.rancher.com/rancher/latest/en/installing-rancher/installing-server/basic-ssl-config/). The self-signed certificate following this [ones](http://www.akadia.com/services/ssh_test_certificate.html). Rancher server seems to be working ok. I can access using https. To run the agent I have copied my ca.cert in /var/lib/rancher/etc/ssl and then executed rancher agent with custom host command. But the result is: ```auto Updating certificates in /etc/ssl/certs... 1 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d....done. ... .... INFO: Attempting to connect to: https://95.211.12.16:8080/v1 ERROR: https://95.211.12.16:8080/v1 is not accessible ERROR: https://95.211.12.16:8080/v1 is not accessible ERROR: https://95.211.12.16:8080/v1 is not accessible ``` Please, any suggestion about what could be my problem? many thanks ---
**Author:** ![Tommy\_Walker](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/tommy_walker/32/2259_2.png) [@Tommy\_Walker](https://forums.suse.com/u/Tommy_Walker)\ **Post date:** [March 3, 2017, 1:04am UTC](https://forums.suse.com/t/rancher-agent-cannot-connect-with-self-signed-server-cert/2728/2 "2017-03-03T01:04:56Z")
Jose, I see no one got back to you here, but I think we might have the same issue you are describing in your post - Did you have resolution? Many Thanks, Tommy