So just to be clear this is the page I am not able...
# kolide
e
So just to be clear this is the page I am not able to download the server certificate from. Tried changing URL to server ip address, public ip address and what I think is my fqdn but still no luck.
@zwass Thank you for answering me earlier questions.
z
Just use the certificate file that you are providing to the server
e
@zwass any idea if this is bc of my URL or tls?
z
This looks like you provided an incorrect URL in the osqueryd configuration. Connection refused usually means there is no server listening at that address/port.
👍 1
e
Ok. Will troubleshoot. Thank you.
@zwass So I checked my fqnd and did a ping -a from another server and its getting recognized. This is how i have my URL set My fqdn is me.mylabserver.com so I have my URL as https://me.mylabserver.com
Not sure if this warning has to do with my clients not connecting to server.
@groob Appreciate you guys help. Thank you.
g
it says connection refused. is your server up?
e
yes, its running.
g
your server is running on port 8080 but you’re connecting to port 443
e
Thats true. Let me change that.
g
now it’s timing out but that looks like an issue on your end again. i’m not sure why that would be
e
The server seem to recognize it.
g
all the logs are showing me are from the frontend requests
e
Ok I see.
I m not sure why kolide isn't working for me. Not sure what I am doing wrong. We were planning on using it on about 6000 units.
g
is it always timing out?
or are you getting other error messages?
can you show me the output of
curl -v <https://your-fleet-server:8080/healthz>
?
e
g
so osquery is not the problem
firewall issue? something else?
try restarting fleet
e
ok. copy.
glad we can rule out osquery as problem.
g
the issue is 100% your environment. not osquery and not fleet
e
Was afraid that would be the case.
g
are you still able to connect through the browser?
e
I am just able to get here in browser. Add new host just give the enroll secret and certificate and link to using launcher or osquery by itself.
g
you’re connecting to
localhost
in the browser
whatever you’re doing your’re not exposing fleet to be reachable outside of that VM
do you have someone on your networking team or someone with web service experience who can help you troubleshoot?
e
yes I ll check with my team to help me with that part.
but glad to know I am following the directions the way they were meant. I ll check with team and hopefully we are able to resolve environment issues. Thank you for all your help.
@groob You were 100% correct. It was firewall. Issue resolved. Thank you once again.
👍 1