[PI Zero W] ToyPad is not accessible via web browser

[RealDawTheD]

I installed the ToyPad emulator from scratch because my previous MicroSD card died. I followed all the steps, and when I ran the container, I am unable to connect to the ToyPad using the board's IP address (see screenshots)

System Info:

[RealDawTheD]

When I was building the container, I did select armv6 as the platform. I also tried using arm as the warning said, but that gave me an error on the APK build step. Then I couldn't get docker working as I tried that.

[RealDawTheD]

I even tried downgrading to RPi OS Legacy 32bit-Lite and that didn't fix anything

[RealDawTheD]

I got this installed eventually.

I downgraded to Raspberry Pi OS Lite (Legacy, 32-bit) and used the dev branch to install the emulator; however now I'm left with this issue:

daw@dawid-malinka:~/LD-ToyPad-Emulator $ npm run start

ld-toypad-emulator@1.4.1 start /home/daw/LD-ToyPad-Emulator
node index.js

Initialized toytags.JSON
Server running on port 80
/home/daw/LD-ToyPad-Emulator/node_modules/engine.io/build/server.js:486
req._query = Object.fromEntries(url.searchParams.entries());
^

TypeError: Object.fromEntries is not a function
at Server.prepare (/home/daw/LD-ToyPad-Emulator/node_modules/engine.io/build/server.js:486:33)
at Server.handleRequest (/home/daw/LD-ToyPad-Emulator/node_modules/engine.io/build/server.js:501:14)
at Server.server.on (/home/daw/LD-ToyPad-Emulator/node_modules/engine.io/build/server.js:642:22)
at Server.srv.on (/home/daw/LD-ToyPad-Emulator/node_modules/socket.io/dist/index.js:330:28)
at Server.emit (events.js:193:13)
at parserOnIncoming (_http_server.js:680:12)
at HTTPParser.parserOnHeadersComplete (_http_common.js:113:17)

which occurs as soon as I open the web panel on any device.

The web panel doesn't react to any inputs after this error shows.

Man why couldn't we just keep the previous method before it was changed to podman.

[RealDawTheD]

Okay so after some research, the issue was because the Object.fromEntries was only introduced in node JS v12.

My version was on v11.15.0.

Updating to v18 fixed this (made sure to change my $PATH values).

Yet this still does not solve the fact that I can't get the emulator work with podman properly

[RealDawTheD]

Oh my god, I found out why it didn't work with Podman. So it turns out it was working, but the readme didn't specify I had to connect using http://[board IP]:8080/ instead of http:// or https://[board IP]

Keeping this open so @Berny23 or other contributors can update the readme in the main branch, as well as the script within the dev branch.

main branch - modified README.md

[RealDawTheD]

daw@dawid-malinka:~/LD-ToyPad-Emulator $ podman build
-t ld-toypad-emulator:latest
--platform=linux/arm/v6
.
[6/7] STEP 1/1: FROM --platform=linux/arm/v6 node:18-alpine AS base-armv6
--> 4d5c295714d8
[7/7] STEP 1/11: FROM 4d5c295714d88dac7c5860f358fa2c39734a8a2729dcc1bc18d91daa69791c9e AS final
[7/7] STEP 2/11: ENV CXXFLAGS="-std=c++17"
--> Using cache 5b8bc7eec9927fab65fcc59a59df8426df2ea6833c9d4f2aa329c864b8ed0357
--> 5b8bc7eec992
[7/7] STEP 3/11: RUN apk update && apk add --no-cache build-base python3 libusb-dev linux-headers eudev-dev g++ make py3-pip py3-setuptools
--> Using cache d33d959aa49c9507899ddfea2f0a343f86bff99308fc948b45de3d4a9b292c43
--> d33d959aa49c
[7/7] STEP 4/11: WORKDIR /app
--> Using cache 9e49dfb060c7814c7764bc9fafdd61aff7b739c39d15c9ad1291de2e3bf90f4f
--> 9e49dfb060c7
[7/7] STEP 5/11: COPY package*.json ./
--> Using cache 16a16c0018c18b3d4da6e8e6f6b17fc43f3b8d55188ecf1382cc6e75c86a3a81
--> 16a16c0018c1
[7/7] STEP 6/11: RUN npm install
npm warn deprecated npmlog@4.1.2: This package is no longer supported.
npm error code ECONNRESETe-there-yet@1.1.7: This package is no longer supported.
npm error network Client network socket disconnected before secure TLS connection was established
npm error network This is a problem related to network connectivity.
npm error network In most cases you are behind a proxy or have bad network settings.
npm error network
npm error network If you are behind a proxy, please make sure that the
npm error network 'proxy' config is set properly. See: 'npm help config'
npm notice
npm notice New major version of npm available! 10.8.2 -> 11.10.1
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.10.1
npm notice To update run: npm install -g npm@11.10.1
npm notice
npm error A complete log of this run can be found in: /root/.npm/_logs/2026-02-25T17_03_15_527Z-debug-0.log
Error: building at STEP "RUN npm install": while running runtime: exit status 1

getting this network related error when building god damn it

(RPi OS 32 bit lite Trixie)

---

This is fixed by changing the NPM registry to a mirror

Add this before RUN npm install in the Dockerfile

RUN npm config set registry https://registry.npmmirror.com

---

I find this weird, as a few days ago when I was originally running this, I had no issue building the container

[RealDawTheD]

@Berny23, I don't know what is going on but this is messed up and I hope this isn't just on my end.

daw@dawid-malinka:~/LD-ToyPad-Emulator $ podman logs ld-toypad-emulator
Initialized toytags.JSON
Server running on port 80
<<Syncing tags, one moment...>>
Initialized toytags.JSON
<<Tags are synced!>>
node:events:495
throw er; // Unhandled 'error' event
^

Error: ESHUTDOWN: cannot send after transport endpoint shutdown, read
Emitted 'error' event on ReadStream instance at:
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -108,
code: 'ESHUTDOWN',
syscall: 'read'
}

Node.js v18.20.8

The error occurs as soon as the game loads and the container is shut down.

I'm testing this on my PS3 as I don't have any other device to test it on (though the same, if not similar, results should occur).

One thing I did notice is this: in my dockerfile, I specified to use the mirror for the npm registry. The step before, however, it reads from any json files which have package in the name. Taking a closer inspection in package-lock.json shows that the files are all taken from the standard registry.npmjs.org

I don't believe that this affects anything as doing htop a second terminal, whilst npm install is doing its thing, shows me that the Pi is compiling.

What I find interesting though is how the main registry does not display any json code on its page unlike its mirror.

[RealDawTheD]

(did not mean to close) I've just seen that I'm having the same issues as in #299 and #301

I'll read over those and update this thread.

I will say Berny I am really sorry for this. I'm just getting super frustrated with trying to get this to work. I had no issues previously when I was an older npm build and now I'm constantly getting problems.

Note to self - maybe its worth reading closed threads (which I was too stupid to see)