Gamedig widget no longer shower minecraft bedrock edition (be) status properly

[mgrimace]

Description

The Gamedig widget was working previously, but is now showing that the Minecraft server is offline. It is online. It was previously working with serverType: minecraftbe and I also tried mbe and minecraft

homepage version

nightly 40b0f95, Aug 15, 2024

Installation method

Docker

Configuration

    - Creative (port 19132):
        icon: minecraft.png
        href: https://crafty.{{HOMEPAGE_VAR_DOMAIN}}:8443
#        description: Ubuntu server on Oracle
        widget:
            type: gamedig
            serverType: minecraftbe
            url: udp://{{HOMEPAGE_VAR_ORACLE_IP}}:19132
            fields: ["name", "players", "status"]
    - Survival (port 19134):
        icon: minecraft.png
        href: https://crafty.{{HOMEPAGE_VAR_DOMAIN}}:8443
#        description: Ubuntu server on Oracle
        widget:
            type: gamedig
            serverType: minecraftbe
            url: udp://{{HOMEPAGE_VAR_ORACLE_IP}}:19134
            fields: ["name", "players", "status"]

Container Logs

[2024-08-15T23:51:18.035Z] error: <httpProxy> Error calling [http://redacted/...](http://redacted:7396/...%3C/span%3E%3C/span%3E)
[2024-08-15T23:51:18.035Z] error: <httpProxy> [
  500,
  Error: socket hang up
      at connResetException (node:internal/errors:720:14)
      at Socket.socketOnEnd (node:_http_client:525:23)
      at Socket.emit (node:events:529:35)
      at endReadableNT (node:internal/streams/readable:1400:12)
      at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
    code: 'ECONNRESET'
  }
]
[2024-08-15T23:51:20.787Z] error: <httpProxy> Error calling [http://redacted:7396/...](http://redacted:7396/...%3C/span%3E%3C/span%3E)
[2024-08-15T23:51:20.787Z] error: <httpProxy> [
  500,
  Error: socket hang up
      at connResetException (node:internal/errors:720:14)
      at Socket.socketOnEnd (node:_http_client:525:23)
      at Socket.emit (node:events:529:35)
      at endReadableNT (node:internal/streams/readable:1400:12)
      at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
    code: 'ECONNRESET'
  }
]
[2024-08-15T23:51:28.864Z] error: <gamedigProxyHandler> Error: Failed all 1 attempts
    at QueryRunner.run (file:///app/node_modules/.pnpm/[email protected]/node_modules/gamedig/lib/QueryRunner.js:106:17)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at listOnTimeout (node:internal/timers:538:9)
    at process.processTimers (node:internal/timers:512:7)
    at async GameDig.query (file:///app/node_modules/.pnpm/[email protected]/node_modules/gamedig/lib/gamedig.js:11:12)
    at async GameDig.query (file:///app/node_modules/.pnpm/[email protected]/node_modules/gamedig/lib/gamedig.js:21:12)
    at async gamedigProxyHandler (/app/.next/server/pages/api/services/proxy.js:2949:24)
    at async Object.apiResolver (/app/node_modules/.pnpm/[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/api-utils/node.js:366:9)
    at async NextNodeServer.runApi (/app/node_modules/.pnpm/[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:481:9)
    at async Object.fn (/app/node_modules/.pnpm/[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:741:37)
Attempt #1 - Port=19132 Retry=0:
Error: Attempt - Timed out after 10000ms
    at Timeout.<anonymous> (file:///app/node_modules/.pnpm/[email protected]/node_modules/gamedig/lib/Promises.js:7:18)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7)
[2024-08-15T23:51:29.888Z] error: <gamedigProxyHandler> Error: Failed all 1 attempts
    at QueryRunner.run (file:///app/node_modules/.pnpm/[email protected]/node_modules/gamedig/lib/QueryRunner.js:106:17)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at listOnTimeout (node:internal/timers:538:9)
    at process.processTimers (node:internal/timers:512:7)
    at async GameDig.query (file:///app/node_modules/.pnpm/[email protected]/node_modules/gamedig/lib/gamedig.js:11:12)
    at async GameDig.query (file:///app/node_modules/.pnpm/[email protected]/node_modules/gamedig/lib/gamedig.js:21:12)
    at async gamedigProxyHandler (/app/.next/server/pages/api/services/proxy.js:2949:24)
    at async Object.apiResolver (/app/node_modules/.pnpm/[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/api-utils/node.js:366:9)
    at async NextNodeServer.runApi (/app/node_modules/.pnpm/[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:481:9)
    at async Object.fn (/app/node_modules/.pnpm/[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:741:37)
Attempt #1 - Port=19134 Retry=0:
Error: Attempt - Timed out after 10000ms
    at Timeout.<anonymous> (file:///app/node_modules/.pnpm/[email protected]/node_modules/gamedig/lib/Promises.js:7:18)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7)
[2024-08-15T23:51:30.562Z] error: <gamedigProxyHandler> Error: Failed all 1 attempts
    at QueryRunner.run (file:///app/node_modules/.pnpm/[email protected]/node_modules/gamedig/lib/QueryRunner.js:106:17)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at listOnTimeout (node:internal/timers:538:9)
    at process.processTimers (node:internal/timers:512:7)
    at async GameDig.query (file:///app/node_modules/.pnpm/[email protected]/node_modules/gamedig/lib/gamedig.js:11:12)
    at async GameDig.query (file:///app/node_modules/.pnpm/[email protected]/node_modules/gamedig/lib/gamedig.js:21:12)
    at async gamedigProxyHandler (/app/.next/server/pages/api/services/proxy.js:2949:24)
    at async Object.apiResolver (/app/node_modules/.pnpm/[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/api-utils/node.js:366:9)
    at async NextNodeServer.runApi (/app/node_modules/.pnpm/[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:481:9)
    at async Object.fn (/app/node_modules/.pnpm/[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:741:37)
Attempt #1 - Port=19132 Retry=0:
Error: Attempt - Timed out after 10000ms
    at Timeout.<anonymous> (file:///app/node_modules/.pnpm/[email protected]/node_modules/gamedig/lib/Promises.js:7:18)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7)
[2024-08-15T23:51:30.576Z] error: <gamedigProxyHandler> Error: Failed all 1 attempts
    at QueryRunner.run (file:///app/node_modules/.pnpm/[email protected]/node_modules/gamedig/lib/QueryRunner.js:106:17)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at listOnTimeout (node:internal/timers:538:9)
    at process.processTimers (node:internal/timers:512:7)
    at async GameDig.query (file:///app/node_modules/.pnpm/[email protected]/node_modules/gamedig/lib/gamedig.js:11:12)
    at async GameDig.query (file:///app/node_modules/.pnpm/[email protected]/node_modules/gamedig/lib/gamedig.js:21:12)
    at async gamedigProxyHandler (/app/.next/server/pages/api/services/proxy.js:2949:24)
    at async Object.apiResolver (/app/node_modules/.pnpm/[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/api-utils/node.js:366:9)
    at async NextNodeServer.runApi (/app/node_modules/.pnpm/[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:481:9)
    at async Object.fn (/app/node_modules/.pnpm/[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:741:37)
Attempt #1 - Port=19134 Retry=0:
Error: Attempt - Timed out after 10000ms
    at Timeout.<anonymous> (file:///app/node_modules/.pnpm/[email protected]/node_modules/gamedig/lib/Promises.js:7:18)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7)

Browser Logs

No response

Troubleshooting

docker exec homepage ping [redactedIP]
PING redactedIP (readactedIP): 56 data bytes

[shamoon]

Sigh. We can assume this is #3841 which might make it more trouble than its worth.

I don't really have much to do to check this out, it does seem like mbe should work and otherwise nothing about gamedig changed.

Perhaps other gamedig users can chime in, TBH I'm inclined to just revert the PR if it is breaking things.

[shamoon]

@mgrimace would you mind asking over at gamedig? Maybe their discord? The homepage code is very simple:

homepage/src/widgets/gamedig/proxy.js

Lines 15 to 21 in 0d25f57

	const serverData = await GameDig.query({
	type: serviceWidget.serverType,
	host: url.hostname,
	port: url.port,
	givenPortOnly: true,
	checkOldIDs: true,
	});

Also have you tried the basic stuff like re-creating (removing and recreating, not just restart) the container?

[mgrimace]

No problem, I'll ask over there. I saw that gamedig was updated in the logs, and checked out the new game codes and figured mbe (the new minecraft:be code) would work, but its not connecting properly on my end at least. Yep, tried the basics (remove/recreate) after setting it as mbe, no change. I'll report back if I can find anything.

[shamoon]

Alright, so I forgot how easy gamedig is to test with public servers. These two work fine:

     - GameDig csgo:
          widget:
               type: gamedig
               serverType: csgo # see https://github.com/gamedig/node-gamedig#games-list
               url: udp://135.148.151.222:16261
               fields: ["status", "maxPlayers"]
     - GameDig mbe:
          widget:
               type: gamedig
               serverType: mbe # see https://github.com/gamedig/node-gamedig#games-list
               url: udp://play.spacecraftsmp.com:25565
               fields: ["status", "maxPlayers"]

(also worked fine with serverType: minecraftbe)

[shamoon]

So maybe this has more to do with your specific server?

[mgrimace]

Interesting ok, similar response in their discord that it's working on public. We're doing some testing on the gamedig end via their discord

[mgrimace]

I'll mention that my own java server using the widget type: minecraft on the same server as bedrock is working fine in homepage, which is why I was thinking it must be something to do with the gamedig widget. All three are on oracle, same IP just different ports:

[shamoon]

Did you see if it still works when you downgrade homepage? If so that really suggests a gamedig issue (ie it shouldn’t have broken compatibility but did)

[mgrimace]

Did you see if it still works when you downgrade homepage? If so that really suggests a gamedig issue (ie it shouldn’t have broken compatibility but did)

We think we found a potential issue in Gamedig, it's not homepage, I'll report back

[mgrimace]

Quick update - working on debugging the issue, and it’s not a homepage thing, see here: gamedig/node-gamedig#610

[shamoon]

Sweet thanks for all the investigating. Will follow that and merge in the update when they release it

[CosminPerRam]

Hey, took longer than expected due to some irl stuff, 5.1.2 containing the fix is released!

[shamoon]

Thanks, #3876 merges 5.1.2 into homepage so mgrimace you can test out the main docker image if / when you have a chance (and it will be in our next release of course)

[mgrimace]

Thanks, #3876 merges 5.1.2 into homepage so mgrimace you can test out the main docker image if / when you have a chance (and it will be in our next release of course)

Confirmed working on main (tested as soon as it finished building). Tested using both the minecraft and mbe serverTypes and the widget now shows 'online' as expected. Thanks much @CosminPerRam and @shamoon, incredible detective work and collaboration here!

[github-actions[bot]]

This discussion has been automatically closed because it was marked as answered. See our contributing guidelines for more details.

[github-actions[bot]]

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.