Bambu Connect / Elegoo Connect / Companion
Bambu Connect / Elegoo Connect / Companion
If you installed Bambu Connect, Elegoo Connect, or the Klipper Companion via SSH using the command line, you must retrieve your logs from the device on which the plugin is running.This SCP command copies the log file from the remote device specified by its IP address to the home directory on the device you’re on.
- SSH into the device running the OctoEverywhere plugin.
- Go to your user home.
cd ~
- Depending on your plugin type, look for a directory as follows. If you have multiple plugins, there will be a
-#appended to the directory name.- Bambu Connect
~/.octoeverywhere-bambu/
- Elegoo Connect
~/.octoeverywhere-elegoo/
- Klipper Companion
~/.octoeverywhere
- Bambu Connect
- In the OctoEverywhere data root, the log path is:
<plugin data root>/log/octoeverywhere.log
Docker Containers
Docker Containers
If you’re using the Docker container for any plugin type, your log files are located in the mapped Docker data folder root.
Klipper / Moonraker
Klipper / Moonraker
Mainsail:
- Enable Debug Logging
- Open the Mainsail web UI
- Click
Machinein the left navigational menu - In the
Config Filessection, find the file namedoctoeverywhere.cfg - Click
octoeverywhere.cfgto open it for editing. - Change
log_level = INFOtolog_level = DEBUG - Click
Save & Restartat the top right.
- Reproduce The Issue
- If you can reproduce the issues on demand, reproduce them and capture the logs.
- If not, wait until you see the issues again, and then try to capture the logs ASAP.
- Capture The Logs
- Open the Mainsail web UI
- Click
Machinein the left navigational menu - In the
Config Filessection, find the box labeledroot. The box defaults to the valueconfigas the root. - Change the
rootdrop-down tologs. - Find the most recent
octoeverywhere.logfile. - Right-click the log file and select
Download.
- Enable Debug Logging
- Open the Fluidd web UI
- Click
Configurationin the left navigational menu - In the
Config Filessection, find the file namedoctoeverywhere.cfg - Click
octoeverywhere.cfgto open it for editing. - Change
log_level = INFOtolog_level = DEBUG - Click the disk save icon at the top right.
- Click the
Xto close the config editor. - Restart the device to ensure the new logging level takes effect.
- Reproduce The Issue
- If you can reproduce the issues on demand, reproduce them and capture the logs.
- If not, wait until you see the issues again, and then try to capture the logs ASAP.
- Capture The Logs
- Open the Fluidd web UI
- Click
Configurationin the left navigational menu - Scroll down to the box labeled
Other Files - Be sure the
LOGStab is selected, it should be by default. - Find the most recent
octoeverywhere.logfile. - Click the log file and select
Download.
OctoPrint
OctoPrint
Here’s how to get your logs:
- Open your OctoPrint web portal.
- Open the OctoPrint settings
- Go to “Logging” in the settings
- Delete your current logs:
- Find the log row that says “octoprint.log”
- Click the trash can icon to delete it.
- Set Logging Level:
- Under “Logging Levels” find “octoprint” and make sure the value is DEBUG
- Press “Save” to close the settings UI
- Reproduce your issue - ideally a few times.
- Restart OctoPrint:
- Click the power icon in the top right of OctoPrint’s web portal
- Select “Restart OctoPrint”
- Go back to the OctoPrint settings, then to the Logging settings panel.
- Find the “octoprint.log” file row and click the download icon.

