What is the problem?
Every print is offset by roughly half an inch from the origin. The GCode visualizer shows everything perfect, but when the print starts it's not in the right spot. This leads to large prints exceeding the boundaries and throwing everything off.
It's your firmware's responsibility to correctly interpret the commands that get created by your slicer and sent to it (here through OctoPrint). For some reason it appears to think it needs to apply an internal offset which leads to the coordinate shift you are seeing. I'd start with checking my firmware's EEPROM settings and config.
The bounding box has nothing to do with that, it merely tells OctoPrint that something outside of the regular build envelope is still safe to move to, so that it won't warn you when you try to print a file where the printhead moves outside the bed borders.
