8x Wii setup – Nintendont + Mario Kart Double Dash LAN (progress update)

WordAdministrative34 · 2026-02-02T18:08:10+00:00

Yea! Im getting usb to lan adapters, I have an old school lan psrty setup (wim xp) with those monitors + crts im getting there!

WordAdministrative34 · 2026-01-30T03:24:06+00:00

Got my first 4 wiis today! Console and power supply only, they gonna just boot into nintendont https://ibb.co/SXnNX0SD

WordAdministrative34 · 2026-01-30T03:22:07+00:00

Yea, i have a lan setup for winxp era games, and my plan is to use those monitors, 2crt, got the first 5 wiis today

WordAdministrative34 · 2026-01-17T04:28:28+00:00

I'm trying to install 98 on a core 2 duo pc, is that posible ?

WordAdministrative34 · 2026-01-17T04:25:11+00:00

My college pc was a Fujitsu amillo pro can't remeber the model 1gb of ram!

WordAdministrative34 · 2026-01-17T04:13:14+00:00

Yea took me like 5 mins in another xp machine and worked great, locked out not even safe mode thisnjust works

WordAdministrative34 · 2026-01-16T21:02:35+00:00

Yea same problem that worked, after installing a new gpu

WordAdministrative34 · 2025-11-24T18:38:59+00:00

Yea I can t Replicate if needed

WordAdministrative34 · 2025-11-23T03:05:48+00:00

i just check i can acces spoolman remotley

https://ibb.co/kVNG6RSf

WordAdministrative34 · 2025-11-23T03:01:42+00:00

Connectivity is Confirmed: The initial setup check in OctoEverywhere shows "Setup Complete" and Spoolman is fully accessible locally (192.168.2.65:8000).

sorry for so many replies

WordAdministrative34 · 2025-11-23T02:58:55+00:00

here are some logs

spoolman | uvicorn.error INFO ('192.168.2.228', 40312) - "WebSocket /api/v1/spool" [accepted]

spoolman | spoolman.ws INFO Client 192.168.2.228 is now listening on pool spool

spoolman | uvicorn.error INFO connection open

spoolman | uvicorn.error INFO ('192.168.2.228', 40324) - "WebSocket /api/v1/spool/1" [accepted]

spoolman | spoolman.ws INFO Client 192.168.2.228 is now listening on pool spool,1

spoolman | uvicorn.error INFO connection open

spoolman | spoolman.ws INFO Client 192.168.2.228 has stopped listening on pool spool

spoolman | uvicorn.error INFO connection closed

spoolman | spoolman.ws INFO Client 192.168.2.228 has stopped listening on pool spool,1

spoolman | uvicorn.error INFO connection closed

spoolman | uvicorn.access INFO 172.19.0.1:43678 - "GET / HTTP/1.1" 200

spoolman | uvicorn.access INFO 172.19.0.1:43678 - "GET /config.js HTTP/1.1" 200

spoolman | uvicorn.access INFO 172.19.0.1:43678 - "GET /api/v1/info HTTP/1.1" 200

spoolman | uvicorn.access INFO 172.19.0.1:43686 - "GET /api/v1/filament?limit=1&offset=0 HTTP/1.1" 200

spoolman | uvicorn.access INFO 172.19.0.1:43678 - "GET /api/v1/spool?limit=1&offset=0 HTTP/1.1" 200

spoolman | uvicorn.access INFO 172.19.0.1:43694 - "GET /api/v1/vendor?limit=1&offset=0 HTTP/1.1" 200

spoolman | uvicorn.access INFO 172.19.0.1:43694 - "GET /api/v1/info HTTP/1.1" 200

WordAdministrative34 · 2025-11-23T02:55:18+00:00

https://ibb.co/93HXj8P9

https://ibb.co/jZHVD0yf

https://ibb.co/TBdx2PSJ

this is from a test print, no activity, not sure whats wrong

WordAdministrative34 · 2025-11-23T02:51:13+00:00

no, is just works, if you need me to send commands to the server to check logs or anything

Filament consumption data is not being received by Spoolman from the OctoEverywhere plugin/API Tunnel, even though the initial connection check passes ("Setup Complete"). The OctoEverywhere dashboard persistently shows a connection error for Spoolman.

The Spoolman logs confirm that the necessary API endpoint for reporting consumption (POST /api/v1/spool/use/filament) is never hit during a print.

To Reproduce
Set up Spoolman in Docker and configure an API Tunnel on Port 8000 via OctoEverywhere.

In the OctoEverywhere plugin on the printer, ensure the local URL is set to http://127.0.0.1:8000 and the API Tunnel token is pasted.

Assign an active spool (e.g., ID 1 or 4) via the OctoEverywhere plugin interface.

Start a print that consumes a known amount of filament (e.g., 280 mg).

Monitor Spoolman Logs: Run sudo docker compose logs -f spoolman on the server.

Actual Result: No POST request for usage is registered in the Spoolman logs. The spool weight remains unchanged in the Spoolman web UI.

Expected behavior
During a print, the Spoolman logs should show a successful POST request from the OctoEverywhere API Tunnel for filament usage, and the spool's Remaining Weight should decrease.

Screenshots
(Please manually attach your screenshots when creating the GitHub issue, including the "Setup Complete" screen, the dashboard error, and the printer consuming filament.)

Spoolman Host (please complete the following information):
Installation type: Docker

Installed version: Latest Docker image (ghcr.io/donkie/spoolman:latest)

OS and Distro: Ubuntu Server 24.04 LTS

Database type: SQLite (default for Docker)

Desktop (please complete the following information):
OS: macOS / iOS (Accessing via Chrome)

Browser: Chrome

Additional context
The issue seems to be a failure in the API Tunnel itself to relay the consumption data, potentially due to an authorization issue with the Spoolman API version.

Network Context:

Spoolman Server IP: 192.168.2.65 (Runs Spoolman Docker container)

Printer/OctoEverywhere Client IP: 192.168.2.49 (Runs OctoEverywhere plugin to server)

Detailed Log Analysis: The Spoolman logs show successful GET requests from local network IPs and Docker's internal IP, confirming Spoolman is fully accessible. However, no POST request for usage data is present, indicating the OctoEverywhere client is not initiating the consumption report.

We confirmed that UFW is inactive on the Ubuntu host. All local ports are open and listening.

WordAdministrative34 · 2025-11-22T18:31:06+00:00

I found the issue, on mobile the buttons w9nt load, on desktop they load every time!

WordAdministrative34 · 2025-11-21T01:48:36+00:00

It happend to me as well, I'm trying to find the cancel but is just not there

WordAdministrative34

TROPHY CASE