Unanswered Remote Access Printer Using Robo App

I think you need to mess around with HAProxy on the rPi to get it to work. There is tons of info on the web on how to get OctoPrint visible to the outside world.

 

Did you use OctoPi or did you build your OctoPrint server yourself? If you used OctoPi that is probably a question for the OctoPi guy (no pun intended here)

https://github.com/guysoft/OctoPi

 

@CDitty I built my own image as I did not like some of the choices that OctoPi made to change default directories. My image is smaller than his also. I am just missing the Robo theme that is here: https://github.com/Robo3D/OctoPrint-robotheme

Don't actually know what they plan to do with this, it is a fork of a fork of work started by the guys that make the Voxel8. Since all the new stuff they built into the C2/R2 is on top of OctoPrint, the source inherits the GPL license from OctoPrint. At some point they will need to release source and that should make setting up OctoPrint so much easier for use Robo users.

 

He changed a bunch of default directories. I rarely change default installs unless absolutely necessary. I believe he started with Debian Jessie with Desktop and removed the desktop apps where I started from Jessie Lite (no x-windows or desktop). He also chose OctoPiPanel for the local LCD control, which I think is just ugly and wanted to go a different route. It is hard to undo all of what he did even if you can read his scripting and understand what he was doing.

I have an old Acer Aspire that has some god-awful slow Intel Atom in it, If I wanted my OctoPrint server to do more than serve one printer I might try to install Linux on that Intel garbage and use it instead of a rPi. The rPi is really only good at a single thing at a time, especially since the CPU has to control all I/O from the USB ports and the network port (the rPi has no dedicated chips for all input/output). It is really too slow for any kind of computational (slicing) or multi-tasking workloads.