Open f616 opened 11 hours ago
Hmmm, you have tried everything I would have tried. It does seem like a firewall issue.
Is it normal to get a curl: (52) Empty reply from server?
Yes, agents use a private SSL cert which rejects all clients.
You can try adding --level debug
to see if any new information is printed. My hunch is no since there is nothing new to log when an agent fails.
example of commands run on 10.220.2.99 to check for connectivity.
For me, nc
shows a different output.
nc -vz test.com 7007
Connection to test.com port 7007 [tcp/afs3-bos] succeeded!
Not sure why? Perhaps bc I am on mac.
I think the best option is to add more log statements. But I don't know what to log since it is the gRPC client that is rejecting the connection.
Let me know if you have any ideas. I'll keep thinking too.
🔍 Check for existing issues
How is Dozzle deployed?
Agents
📦 Dozzle version
v8.6.2
✅ Command used to run Dozzle
dozzle-agent running on machine 10.220.2.100
dozzle running on machine 10.220.2.99
🐛 Describe the bug / provide steps to reproduce it
dozzle-agent running on machine 10.220.2.100
dozzle running on machine 10.220.2.99 is not able to connect to the agent
Both machines are on the same network on my corporative private cloud. The issue might be related to any firewall restriction, however I have connectivity from 10.220.2.99 to 10.220.2.100
example of commands run on 10.220.2.99 to check for connectivity.
Is it normal to get a
curl: (52) Empty reply from server
? Any clues how can I troubleshoot this?Thank you f616
💻 Environment
📸 If applicable, add screenshots to help explain your bug
No response
📜 If applicable, attach your Dozzle logs. You many need to enable debug mode. See https://dozzle.dev/guide/debugging.
No response