Step 1: Put Your Plugin In Debug Mode
First, you need to put your plugin into debug mode and restart it. Based on your plugin install type, choose an option:Linux CLI - Bambu Connect / Elegoo Connect / PrusaLink / Klipper Companion
Linux CLI - Bambu Connect / Elegoo Connect / PrusaLink / Klipper Companion
If you installed Bambu Connect, Elegoo Connect, or the Klipper Companion via SSH, you must retrieve your logs from the device where the plugin is running.This SCP command copies the log file from the remote device at the specified IP address to your device’s home directory.
- SSH into the device running the OctoEverywhere plugin.
- Go to your user home.
cd ~
- Depending on your plugin type, look for the following directory. If you have multiple plugins, a
-#will be appended to the directory name.- Bambu Connect
~/.octoeverywhere-bambu/
- Elegoo Connect
~/.octoeverywhere-elegoo/
- Klipper Companion
~/.octoeverywhere
- Bambu Connect
- Edit the plugin config:
nano <plugin data root>/octoeverywhere.conf
- Enable debug logging:
- Set
log_leveltoDEBUG
- Set
- Exit the editor
- Press Ctrl + X to exit, press
Yto save.
- Press Ctrl + X to exit, press
- Restart the plugin or restart the device.
Windows Desktop Plugin Manager App
Windows Desktop Plugin Manager App
If you’re using the Windows Plugin Manager App:
- Open the app
- Click the “Open Data Folder” button next to the plugin you want.
- Use a text editor to edit the
octoeverywhere.conffile - Set
log_leveltoDEBUG - Restart the plugin or restart your computer.
Docker Container
Docker Container
If you’re using the Docker container for any plugin type, your config file is located in the mapped root of the Docker data folder.Use a text editor to open the file and set the value of
log_level to DEBUG. Be sure to restart the Docker container or reboot the computer.Klipper / Moonraker
Klipper / Moonraker
Mainsail:
- 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.
- 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.
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
Step 2: Reduce The Issue
Once you have the plugin in debug mode and have started the plugin, reproduce the issue, ideally a few times. After you have reproduced it, give the plugin about a minute to fully output the logs.Step 3: Get The Plugin Log
Now you need to get the log file and send it to our support team.Linux CLI - Bambu Connect / Elegoo Connect / PrusaLink / Klipper Companion
Linux CLI - Bambu Connect / Elegoo Connect / PrusaLink / Klipper Companion
- SSH into the device running the OctoEverywhere plugin.
- Go to your user home.
cd ~
- Depending on your plugin type, look for the following directory. If you have multiple plugins, a -# will be 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
Windows Desktop Plugin Manager App
Windows Desktop Plugin Manager App
If you’re using the Windows Plugin Manager App:
- Open the app
- Click the “Open Data Folder” button next to the plugin you want.
- Open the
logsfolder - Share the
octoeverywhere.logfile in the folder.
Docker Container
Docker Container
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:
- 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.
- 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
- Find the “octoprint.log” file row and click the download icon.

