No, still not workinig :-(, same error as before. I verified the logs on
the firewall and there is no more traffic blocked from puppet master and
from the proxy. Additionally, I can telnet my F5 on port 443 without any
problem from both servers.
Any other idea what could be the causing this pro
Hi Gavin!
ok, yes that make sense. We do have a firewall in-between and I had only
enable access to the BIG-IP from the proxy not from the pupept master. I
will give it a try. Thanks a lot for the hint!
Cheers,
Cesar
On Wednesday, January 9, 2013 5:39:44 PM UTC+1, Gavin Williams wrote:
>
> Hi
Hi there,
I've done some work with the F5 network device support in our env, and
haven't had any issues with self-signed certs...
Sounds more likely that it's a network/firewall issue...
Can you telnet from the puppet server to F5 on port 443?
Cheers
Gavin
On Wednesday, 9 January 2013 16:2
