I am setting up a fresh install of FlashForgeWebUI (v1.2.0-alpha.2) inside a Proxmox LXC container (Debian 12, unprivileged) to connect to a FlashForge Creator 5 Pro in LAN mode.
Both the container (192.168.1.218) and the printer (192.168.1.184) are on the same subnet, but the UI is unable to complete the handshake.
Environment Details
WebUI Version: v1.2.0-alpha.2 (Standalone Linux x64 binary, 175 MB)
OS: Debian 12 (Proxmox LXC)
Printer Model: FlashForge Creator 5 Pro (LAN Mode Enabled)
Network Setup: Same subnet (192.168.1.x)
Observed Issues & Bugs
-
Missing Dropdown Profile
In the Printer Type dropdown, there is no option for Creator 5 or Creator 5 Pro (even after clearing browser cache on a clean VM install). Only 5M / 5M Pro (New API) and Legacy Printers (Old API) are available.
-
Port Mismatch (ECONNREFUSED on 8899)
Attempting to connect using 5M / 5M Pro (New API) causes the backend to try to connect to TCP port 8899.
The Creator 5 Pro API communicates over HTTP on port 80 and does not use a check code, resulting in connection refusal:
Socket error: connect ECONNREFUSED 192.168.1.184:8899
3. Frontend Validation Blocks Workaround
Attempting to force the connection port manually in the host field by entering 192.168.1.184:80 triggers a frontend validation error:
"invalid IP address format"
4. Auto-Detection / Probe Failures
Letting the backend auto-scan or probe the IP triggers a 500 error:
[Detection] failed to probe 192.168.1.184: Failed to initialize control
[WebUI] POST /printers/detect - 500 (18383ms)
I am setting up a fresh install of FlashForgeWebUI (v1.2.0-alpha.2) inside a Proxmox LXC container (Debian 12, unprivileged) to connect to a FlashForge Creator 5 Pro in LAN mode.
Both the container (192.168.1.218) and the printer (192.168.1.184) are on the same subnet, but the UI is unable to complete the handshake.
Environment Details
WebUI Version: v1.2.0-alpha.2 (Standalone Linux x64 binary, 175 MB)
OS: Debian 12 (Proxmox LXC)
Printer Model: FlashForge Creator 5 Pro (LAN Mode Enabled)
Network Setup: Same subnet (192.168.1.x)
Observed Issues & Bugs
Missing Dropdown Profile
In the Printer Type dropdown, there is no option for Creator 5 or Creator 5 Pro (even after clearing browser cache on a clean VM install). Only 5M / 5M Pro (New API) and Legacy Printers (Old API) are available.
Port Mismatch (ECONNREFUSED on 8899)
Attempting to connect using 5M / 5M Pro (New API) causes the backend to try to connect to TCP port 8899.
The Creator 5 Pro API communicates over HTTP on port 80 and does not use a check code, resulting in connection refusal:
Socket error: connect ECONNREFUSED 192.168.1.184:8899
3. Frontend Validation Blocks Workaround
Attempting to force the connection port manually in the host field by entering 192.168.1.184:80 triggers a frontend validation error:
"invalid IP address format"
4. Auto-Detection / Probe Failures
Letting the backend auto-scan or probe the IP triggers a 500 error:
[Detection] failed to probe 192.168.1.184: Failed to initialize control
[WebUI] POST /printers/detect - 500 (18383ms)