After having to disconnect my printer from my pi to remove a filament jam octoprint is not connecting to the printer it shows "No more candidates to test, and no working port/baudrate combination detected."
What did you already try to solve it?
Removed all plugs and power cables from printer and pi for 5+ minutes then reconnected cables and turned pi and printer. Tried restarting octoprint from browser and using putty as well and still not connnecting.
OctoPrint version 1.6.1, OctoPi version 0.18.0 running on Raspberry Pi 4 Model B, printer Prusa Mini+, firmware 4.3.1, browser Opera, operating system Windows 10, SSH Putty
Seems like the USB/serial simply isn't being found.
Try this:
Connect to OctoPi via SSH
Disconnect the printer USB cable.
Execute dmesg -w over SSH and press Enter a few times to add some blank lines.
Plug in the USB cable from the printer. You should see some output afterwards. Paste that here. If you don't see anything then the Pi isn't detecting your printer at all. Check connections, swap USB cables, try different USB ports, try another USB device and see if any output is generated.
Unfortunately OctoPrint still won't connect still shows "No more candidates to test, and no working port/baudrate combination detected." I tried all the ports on the pi same thing. Unfortunately I don't have another usb to micro-usb cable right now to test with.
the next line had nothing to do with it, I tried doing ctrl+c to copy when I was trying to get the info. The last line that came up after plugging the printer back in was the usb 1-1.2: USB disconnect, device number 6. I don't have another computer to use.
Just got a new usb to micro usb cable to try and now it's connecting. Guess there was a sharp bend that must have kinked the first cable now I have a more flexible one.
Thanks, that helped a lot. In my case the issue was caused by brltty-udev.service that was causing my ttyUSB0 disconnected.
I have disabled brltty-udev.service because I dont need any brail related services and octoprint connected succesfully.
On screen below you can see on top, failed scenario then below sucess after running: