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

Specifing port with hostname causes socket error #24921

Open
sidey79 opened this issue Nov 25, 2024 · 0 comments
Open

Specifing port with hostname causes socket error #24921

sidey79 opened this issue Nov 25, 2024 · 0 comments
Labels
problem Something isn't working

Comments

@sidey79
Copy link

sidey79 commented Nov 25, 2024

What happened?

I get a socket error (getaddrinfo EAI_AGAIN) if i specify the env var "ZIGBEE2MQTT_CONFIG_SERIAL_PORT" with a hostname like this: tcp://:45108

If i add the ip address, then i get a connection
10.2.11.90:45108

Hostname resolution works from other containers in the same stack__

What did you expect to happen?

Network connection can be established via hostname

How to reproduce it (minimal and precise)

Specify a network connection SERIAL_PORT with a hostname and not an ip address

Zigbee2MQTT version

1.41.0

Adapter firmware version

Adapter

conbee-3

Setup

containerized

Debug log

no debug log available

@sidey79 sidey79 added the problem Something isn't working label Nov 25, 2024
@sidey79 sidey79 changed the title Specifing Port with hostname causes Socket error Specifing port with hostname causes socket error Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
problem Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant