Minecraft Widget using tcp instead of udp? #1435
Replies: 3 comments 3 replies
-
Working fine for me
Perhaps theres something with the IP resolution, but homepage only uses the hostname and port from the url. Perhaps try re-creating things... |
Beta Was this translation helpful? Give feedback.
3 replies
-
This discussion has been automatically closed due to inactivity. |
Beta Was this translation helpful? Give feedback.
0 replies
-
This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description
I added the Minecraft Widget as per the docs and the Status is always Offline for me.
My Service section looks like this:
description: Local Server
icon: minecraft
server: docker
container: minecraft
widget:
type: minecraft
url: udp://192.168.0.12:19132
In the Homepage logs however, I can see this error:
It looks to me like a TCP connection is attempted instead of UDP and because of that the connection to the Minecraft Server fails?
I also entered the Homepage Container and tested the connection with a nc -zvu 192.168.0.12 19132 successfully.
Steps to reproduce
homepage version
v0.6.16 (0ae13d8)
Installation method
Docker
Configuration
Container Logs
homepage | [2023-04-30T13:14:35.428Z] error: Error: connect ECONNREFUSED 192.168.0.12:19132
homepage | at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16)
Browser Logs
No response
Other
No response
Before submitting, I have made sure to
Beta Was this translation helpful? Give feedback.
All reactions