Creality K1 Max Moonraker Home Assistant fix guide: restore Moonraker after a firmware update so Home Assistant can connect again. ✅
Creality K1 Max Moonraker Home Assistant: what broke (and how it looks) 😵💫
After a firmware update, it’s common for K1 Max to stop exposing Moonraker on your LAN. When that happens, the Home Assistant integration (moonraker-home-assistant) can’t reach the printer anymore.
Typical symptoms:
- Home Assistant shows the printer as unavailable / disconnected.
- Opening
http://<K1 Max IP>:7125/access/inforeturns ERR_CONNECTION_REFUSED.
When you see “connection refused”, it usually means Moonraker is not running, not listening on the network interface, or the previous install got replaced/disabled by the firmware update.
This post documents a reliable fix: use Guilouz Helper Script to remove Moonraker + Nginx, then reinstall Moonraker + Nginx cleanly.
Links:
- Moonraker Home Assistant integration: https://github.com/marcolivierarsenault/moonraker-home-assistant
- Helper Script installation guide (Guilouz wiki): https://guilouz.github.io/Creality-Helper-Script-Wiki/helper-script/helper-script-installation/
- Mainsail guide (Guilouz wiki): https://guilouz.github.io/Creality-Helper-Script-Wiki/helper-script/mainsail/
Before you start ✅
You’ll need:
- Your K1 Max IP address
- A PC on the same network (Windows/macOS/Linux)
- SSH access as root (enabled from the printer settings)
Quick sanity check (optional but useful):
Try in a browser:
http://<K1 Max IP>/(Creality web UI, if available)http://<K1 Max IP>:7125/access/info(Moonraker API)
If the second URL refuses connections, the Moonraker service is not reachable, and Home Assistant won’t be able to connect.
K1 Max Moonraker Home Assistant: enable root so SSH works 🔓
On the K1 Max touchscreen, enable root access first. On many firmwares this is under something like:
- Settings → Root account information
Then:
- Read the warning/disclaimer
- Tick/confirm the agreement
- Wait a short moment (some firmwares show a ~30s countdown)
- Confirm to enable root
After root is enabled, you can SSH into the K1 Max.
SSH into K1 Max 🖥️
macOS / Linux:
ssh root@<K1_MAX_IP>
Windows:
- Use Windows Terminal (PowerShell) with the same
ssh root@<ip>command, or - Use an SSH client like MobaXterm / PuTTY.
If your firmware shows a root password on-screen, use that. If your K1 Max uses a default root password, use the one provided by your firmware / root-enable screen.
K1 Max Moonraker Home Assistant: reinstall Moonraker + Nginx using Helper Script 🛠️
This is the exact workflow that restored Moonraker and brought back the Home Assistant connection on K1 Max.
Step 1 — Download the Helper Script 📥
Run these commands over SSH:
git clone –depth1 https://github.com/Guilouz/Creality-Helper-Script.git /usr/data/helper-script
sh /usr/data/helper-script/helper.sh
If the script asks to update itself, let it update.
Step 2 — Remove Moonraker and Nginx (clean slate) 🧹
Inside the Helper Script menu:
- If it detects a previous install and asks what to do, choose the option for “previously installed” (in my case it was 2).
- Enter the Remove menu.
- Select Remove Moonraker and Nginx.
- Go back to the main menu (usually by pressing b).
Why this matters:
- A firmware update can leave you with mismatched components.
- Removing Moonraker and Nginx ensures there’s no broken/partial install blocking ports.
Step 3 — Install Moonraker and Nginx again ✅
Still inside Helper Script:
- Enter the Install menu.
- Select Install Moonraker and Nginx (commonly option 1).
At this point your K1 Max should have a clean Moonraker installation and Nginx configured for it.
K1 Max Moonraker Home Assistant: verify Moonraker is reachable again 🔍
From your PC browser:
http://<K1 Max IP>:7125/access/info
If Moonraker is working, you should get a JSON response (not a refusal).
Optional network test:
- If you previously got “refused”, but now you get a response, the Moonraker API is back.
Reconnect Home Assistant to Moonraker 🔁
Once Moonraker is reachable, Home Assistant should reconnect.
Do this in Home Assistant:
- Confirm the printer IP used by the integration is correct.
- If you still see stale errors:
- Reload the integration, or
- Remove and re-add the Moonraker integration.
Tip:
- If your router changes IP addresses (DHCP), reserve a static lease for your K1 Max. It prevents random breakage of Home Assistant ↔ Moonraker connections.
Why this works (short version) 🧠
On K1 Max, firmware updates can disrupt how Moonraker and Nginx are deployed and started. The Guilouz Helper Script is effective because it:
- Removes conflicting or broken Moonraker + Nginx installs
- Reinstalls clean, consistent components
- Restores the service that Home Assistant depends on
If you’re running K1 Max, Moonraker, and Home Assistant, this remove-then-install flow is often faster than manual debugging.
Final checklist ✅
- K1 Max root enabled
- SSH access works
- Helper Script installed
- Moonraker + Nginx removed
- Moonraker + Nginx installed
http://<K1 Max IP>:7125/access/inforesponds- Home Assistant integration points to the correct IP
Leave a Reply