Frequently asked questions

Go to http://pocket.local/admin. That address always reaches the console, whatever homepage is currently set.

Once you set a homepage, / serves your app instead of the console. That’s the whole point of the device — but it does mean the admin page isn’t at the root any more. /admin is the permanent way back in, and it never depends on what you’ve uploaded.

Which address to use

Situation	Address
Default setup, connected to the device	http://pocket.local/admin
You renamed the device	http://<name>.local/admin
.local names don’t resolve on your phone or laptop	http://192.168.4.1/admin

That last address is the device itself while it’s broadcasting its own Wi-Fi, so it works even when nothing on your network can resolve .local. If you pointed the board at your home Wi-Fi instead, use the name — the numeric address will be whatever your router handed out.

First check you’re on its network

The board isn’t on the internet, so no address reaches it unless you’re joined to the same network. By default that’s the one it broadcasts itself: look for pocket-server- followed by four characters in your Wi-Fi list, and join it with the password password123 unless you’ve changed it. Give it a minute after power-on before you go looking.

If it asks for a password

The password is the one you chose when you first claimed the device. If you set a hint, the sign-in screen shows it.

To reset your password, tap the reset button five times, about once a second, letting each restart finish before the next tap. That returns the board to setup mode so you can claim it again with a new password. Your uploaded files are kept — but the Wi-Fi settings, device name and guest permissions are cleared, and it won’t serve your homepage again until it’s claimed. Typing reset into a serial monitor at 115200 baud does the same thing.

The pins are right; the numbers printed beside them are wrong. It’s a silkscreen mistake on that one batch — the GPIO numbers were carried over from an earlier layout that moved, and the copper underneath is correct.

Nothing is broken and there’s nothing to fix on the board — you just have to read the header by position rather than by the printed number. Pin 1 is the square pad; the other seven are round.

The correct layout

Free for your own wiring Already spoken for Power, not a GPIO

Pin	Printed	Actually	Notes
1	3.3v	3.3V	Correct as printed. Square pad.
2	GND	GND	Correct as printed.
3	10	GPIO42	Free. Use this one first.
4	11	GPIO41	Free. Use this one second.
5	12	GPIO2	Shared with the onboard status LED — driving it also blinks the LED.
6	13	GPIO43	UART0 TX. Reserved for future Pocket Server updates.
7	17	GPIO44	UART0 RX. Reserved for future Pocket Server updates.
8	18	5V	Power, not a GPIO — a 3.3V part wired here sees 5V.

What happens if you follow the silkscreen anyway

Usually, mostly nothing. The numbers 10, 11, 12 and 13 happen to name pins the SD card interface owns, so the device answers 400 and refuses to drive them while a card is mounted — and 11, the card-detect line, is off-limits even with an empty slot. 17 and 18 are accepted but aren’t connected to the header at all, so the request succeeds and nothing moves on the wire.

The one case that isn’t harmless is the physical one: a wire on pin 8 expecting 3.3V logic and finding 5V.

Using the free pins

Pins 3 and 4 — GPIO42 and GPIO41 — are the two with nothing else attached, so reach for those. From an app on the device:

The developer guide has the full GPIO reference, and the device validates pin numbers itself — so an app that surfaces the error it returns will keep working on a board whose labels are fixed.