Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ORB not able to connect to diode server #229

Open
willflo opened this issue Jan 14, 2025 · 4 comments
Open

ORB not able to connect to diode server #229

willflo opened this issue Jan 14, 2025 · 4 comments
Labels
status: needs triage This issue is awaiting triage by a maintainer

Comments

@willflo
Copy link

willflo commented Jan 14, 2025

Hey,

ive setup diode as the guide in the readme but when i try running a discovery with orb and orb triest to connect diode it gets a connection refused. Ive checked the api keys alot of times but there is still this issue coming up.
"dial tcp 127.0.0.1:8080: connect: connection refused"

@mfiedorowicz
Copy link
Member

Hi @willflo, few questions to help us understand the issue:

  • are you running orb-agent on same host as diode?
  • how are you running diode? (docker compose, helm chart/k8s)?
  • in your netbox with diode plugin installed and configured, are you able to open ingestion logs view without any errors?

@mfiedorowicz mfiedorowicz added the status: needs triage This issue is awaiting triage by a maintainer label Jan 14, 2025
@willflo
Copy link
Author

willflo commented Jan 14, 2025

Hey

  1. yes
  2. its running on docker compose
  3. no, it show: "UNAVAILABLE: Received http2 header with status: 504"

thanks for the fast response! :)

@mfiedorowicz
Copy link
Member

mfiedorowicz commented Jan 14, 2025

Re: error on netbox diode plugin - it's timing out (504), and might be also related to orb-agent -> diode connection issue, sounds like firewall on your host machine, hard to say exactly without knowing environment running on.

@willflo
Copy link
Author

willflo commented Jan 14, 2025

its running on ubuntu 24.04.1
The only "firewally" thing running on it is iptables for docker communication

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: needs triage This issue is awaiting triage by a maintainer
Projects
None yet
Development

No branches or pull requests

2 participants