OctoPrint fails to connect to printer until I reboot it

What is the problem?
After about 1 minutes of a successful print my printer it turned off using PSU Control plugin. It's set to "disconnect on power off"
If I then turn the printer back on and try and connect to the printer it cannot find the USB port.
If i reboot the pi in octoprint this usually works but sometimes i have to turn off the PI and then turn it back on.
I've also noticed that the pi does not respond to any http requests some times and again i have to re-start the pi..

What did you already try to solve it?
Restarting it or turning off the pi and back on again works..
I've added heat sinks to the Pi thinking it's an overheating issue.

What I'm thinking of trying
Reloading the Pi
Trying a new SD card in the PI.
Try a new cable (The current one is shielded)
Try a different power supply for the Pi

Logs (octoprint.log, serial.log or output on terminal tab, ...)
Serial.log
2019-06-25 15:03:28,843 - Recv: ok T:32.81 /0.00 (959.25) B:34.69 /0.00 (954.75) @:0 B@:0
2019-06-25 15:03:33,807 - Send: M105
2019-06-25 15:03:33,843 - Recv: ok T:32.79 /0.00 (959.31) B:34.66 /0.00 (954.81) @:0 B@:0
2019-06-25 15:03:38,808 - Send: M105
2019-06-25 15:03:38,844 - Recv: ok T:32.71 /0.00 (959.50) B:34.61 /0.00 (954.94) @:0 B@:0
2019-06-25 15:03:43,810 - Send: M105
2019-06-25 15:03:43,842 - Recv: ok T:32.63 /0.00 (959.69) B:34.56 /0.00 (955.06) @:0 B@:0
2019-06-25 15:03:48,812 - Send: M105
2019-06-25 15:03:48,843 - Recv: ok T:32.47 /0.00 (960.06) B:34.53 /0.00 (955.13) @:0 B@:0
2019-06-25 15:03:53,813 - Send: M105
2019-06-25 15:03:53,843 - Recv: ok T:32.50 /0.00 (960.00) B:34.35 /0.00 (955.56) @:0 B@:0
2019-06-25 15:03:57,363 - Connection closed, closing down monitor
2019-06-25 15:03:57,382 - Changing monitoring state from "Operational" to "Offline"
2019-06-25 15:54:00,215 - Changing monitoring state from "Offline" to "Detecting serial port"
2019-06-25 15:54:00,259 - Serial port list: []
2019-06-25 15:54:00,259 - Changing monitoring state from "Detecting serial port" to "Error: Failed to autodetect serial port, please set it manually."
2019-06-25 15:54:00,267 - Failed to autodetect serial port, please set it manually.
2019-06-25 15:56:00,809 - Changing monitoring state from "Offline" to "Detecting serial port"
2019-06-25 15:56:00,854 - Serial port list: []
2019-06-25 15:56:00,855 - Changing monitoring state from "Detecting serial port" to "Error: Failed to autodetect serial port, please set it manually."
2019-06-25 15:56:00,859 - Failed to autodetect serial port, please set it manually.
2019-06-25 15:59:35,582 - Changing monitoring state from "Offline" to "Detecting serial port"
2019-06-25 15:59:35,614 - Serial port list: []
2019-06-25 15:59:35,615 - Changing monitoring state from "Detecting serial port" to "Error: Failed to autodetect serial port, please set it manually."
2019-06-25 15:59:35,619 - Failed to autodetect serial port, please set it manually.

Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, ...)
Octo Print Version 1.3.11
OctoPi Version 0.16.0, running on Raspberry Pi 3 Model A Plus Rev 1.0
I have request exclusive access to the printer checked.

You might try using uhubctl to toggle OFF/ON power to the single Type A port on the Raspi 3A+ after turning the printer back on. You could do an ls /dev/tty* before/after to see if this affects which devices have been loaded.

Thank you for the suggestion. I'll give ti a go. Is there any way to run the command from within octoprint?

Well, that would be the next step. If it works using uhubctl from the command line, then consider adding my own OctoPrint-USBControl plugin (having read the README of course).

I have a similar issue. This is immediately after upgrading the Ender 3 V2 from 4.2.2 to 4.2.7. Both running latest Marlin. Once connected, everything is reliable. After printer shuts down and restarts, Octoprint cannot connect until I fiddle with cables or power cycling the printer. One would think it's the main board, since it worked fine on 4.2.2, but why?

Ok, so you're saying it actually should reconnect after the board errors. But a bug in Octoprint is stopping it?

I'm not seeing the mention of a bug here...?