Moonraker warnings found. I have only ran into this twice so far. Once when I was doing the original install and just now today again, after a power outage. First I tried to update everything. Updated. No help, still has the error. Restarting didn’t do anything. Something must have gotten corrupted. If you head over to the OpenNeptune3D GitHub there is a solution posted there under the display_connector repository in the issues/bug tracker. I will also detail it here.
- [update_manager]: Failed to load extension display: It reports an invalid path for the option virtualenv in section [update_manager display] . The specified path /home/mks/display_connector/venv does not exist.
- Unparsed config option ‘primary_branch: main’: This is detected in section [update_manager display]. It suggests the option may no longer be available or could result from a failed module. A warning indicates this will cause a startup error in the future.
- Unparsed config option ‘requirements: requirements.txt’: This is also detected in section [update_manager display] and may no longer be available or caused by a failed module. A similar warning states this will lead to a startup error in the future.
- Unparsed config option ‘origin’: The text includes a URL: https://github.com/OpenNeptune3D/display_connector.git, which is detected in section [update_manager display]. It may no longer be an available option or the result of a failed module, with a warning that this will cause a startup error in the future.
If you log into Fluidd and see this Moonraker warning message don’t worry, there is an easy fix. You will need to SSH into the 3D printer to run some commands.
SSH into the printer from a terminal on your computer/phone/tablet, whatever you are using.
1 2 |
Username: mks Password: makerbase |
1 |
ssh mks@your_printers_ip_address |
After you login you should be in the home directory for the user mks . We need to change directories and enter display_connector to run the installer.
From the terminal type cd /home/mks/display_connector
Now we need to run the display service installer, which should clear up the issue.
Type ./display-service-installer.sh
Now you can head back to your Fluidd window and refresh the page. The issue should be gone now.