SSH access to the printer

Most things on the G1 are done from the web interface. A few are not — recovering a broken update, reading a log that Mainsail will not show you, or downgrading a component. For those you need a terminal on the printer’s Raspberry Pi.

Login

Address	g1os.local — the same one you use in the browser
Username	pi
Password	raspberry

These are the factory credentials, and everyone knows them

pi / raspberry is the default on every G1 as shipped, and it is published here because you need it. It also means anyone on your network can log into your printer.

On an isolated workshop network that is usually acceptable. If the printer sits on an office network, or anywhere reachable from outside, change the password with passwd after your first login.

Never expose the printer directly to the internet.

Connecting

Windows

Windows 10 and 11 include an SSH client, so nothing needs installing:

1. Open PowerShell or Command Prompt
2. Type ssh pi@g1os.local and press Enter
3. The first time, it asks whether to trust the host — type yes
4. Enter the password raspberry. Nothing appears as you type — no dots, no stars. That is normal; type it and press Enter

PuTTY works too, if you prefer a window to a prompt: host g1os.local, port 22.

macOS and Linux

1. Open Terminal
2. ssh pi@g1os.local
3. Accept the fingerprint, then enter raspberry

If g1os.local does not resolve

Use the printer’s IP address instead — Mainsail shows it under Machine → System Info. ssh pi@192.168.1.50, with your own address.

.local names rely on mDNS, which some networks and VPNs block.

Where things live

Path	What it is
~/printer_data/config/	Every configuration file Klipper reads
~/printer_data/logs/	klippy.log, moonraker.log, KlipperScreen.log
~/printer_data/database/	Moonraker’s database, and G1.Conf with the printer’s serial
~/klipper/, ~/moonraker/, ~/mainsail/	The components themselves
~/G1-Configs/	The shared Ginger layer — see G1OS software stack

Commands worth knowing

Watch a log while something fails. This is the single most useful one — leave it running, reproduce the fault, and read what appears:

tail -f ~/printer_data/logs/klippy.log

Press Ctrl+C to stop watching.

Check whether a service is running:

systemctl status klipper moonraker KlipperScreen g1-flask

Restart a service:

sudo systemctl restart klipper

See the version of a component:

cd ~/moonraker && git describe --tags

Free disk space, which matters because a full card corrupts the database:

df -h /

Rules

• Do not edit files under ~/G1-Configs/. They are the shared layer and are replaced on the next update. Machine-specific changes belong in printer.cfg
• Do not run sudo commands you found in a forum without knowing what they do. The Pi is the printer’s brain, and a wrong command means reflashing the card
• Log out with exit

Related notes

• G1OS software stack — what each service does
• G1OS installation — reflashing when it is beyond repair
• Klipper firmware update