Touch Ui does not appear on some devices


I was using octoprint on a Pi3 for some month now.
It was working fine.
The attached display was running well as well and touch-ui was started automatically at startup.

Some weeks ago after a system update, touch-ui was not coming up anymore.

As you may know ... When a system is running without probs you loose all tipss and tricks and how tos :slight_smile:

As I was using octoprint from my desktop pc as well, I did note take care about the small attached display.

Today I was feeling strong enough to fix it.

I was using this command to re-configure touch-ui:
sudo ~/TouchUI-autostart/helpers/install

It finished without any probs. After restarting the pi ... my octoprint is completely dead.

" The OctoPrint server is currently not running"

I have no idea how to aproach this issue?

Does anyone have any advice on what i could do best?


Going to assume OctoPi,

Run the following and report back with the output. Do not exclude any information other than what may be considered sensitive:

ps auxww | grep octoprint
sudo systemctl status octoprint
cat /home/pi/.octoprint/logs/octoprint.log


thanks for ur response.
I do my very best to provide the requested information.
1st command returns:

pi        1928  0.0  0.0   4368   572 pts/0    S+   17:22   0:00 grep --color=auto octoprint

2nds outbut is:

● octoprint.service - LSB: OctoPrint daemon
   Loaded: loaded (/etc/init.d/octoprint; generated; vendor preset: enabled)
   Active: active (exited) since Wed 2021-04-28 17:17:05 CEST; 24h ago
     Docs: man:systemd-sysv-generator(8)
  Process: 486 ExecStart=/etc/init.d/octoprint start (code=exited, status=0/SU
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/octoprint.service

Apr 28 17:17:05 octopi systemd[1]: Starting LSB: OctoPrint daemon...
Apr 28 17:17:05 octopi octoprint[486]: Starting OctoPrint Daemon: OctoPrint.
Apr 28 17:17:05 octopi systemd[1]: Started LSB: OctoPrint daemon.

the log cat is quite big ... I've attached it
1585912835462.remmina.log (27.5 KB)
I hope you can do more with it than me!?

Thanks for ur support.


Not too much there. Lets try this

rm -f /home/pi/.octoprint/logs/*
source /home/pi/oprint/bin/activate
/home/pi/oprint/bin/python /home/pi/oprint/bin/octoprint serve --basedir /home/pi/.octoprint --safe
# check if web ui works. if not, 
# open another ssh connection
cat /home/pi/.octoprint/logs/octoprint.log


this was quick ... :slight_smile:

... returns:

2021-04-29 17:45:38,929 - octoprint.startup - CRITICAL - Could not initialize settings manager: Error parsing the configuration file /home/pi/.octoprint/config.yaml, it is invalid YAML. The parser reported an error on line 3, column 15.
2021-04-29 17:45:38,930 - octoprint.startup - CRITICAL - There was a fatal error starting up OctoPrint.
Could not initialize settings manager: Error parsing the configuration file /home/pi/.octoprint/config.yaml, it is invalid YAML. The parser reported an error on line 3, column 15.
There was a fatal error starting up OctoPrint.

Either you have a corrupt SD card or changes were made to the config file that it doesn't like.
Would need to see a copy in order to have an idea. You can grab it from /home/pi/.octoprint/config.yaml using something like FileZilla.

config.yaml (13.9 KB) SDcard was unning well for years now.

The issue accurs after an octoprint update.
touch-ui did not start anymore.

After updating or reinitializing touch.ui octoprint crashed ...

here comes config.yaml (just changed user names @259 and 300)

  autologinLocal: true
  autologinAs: cappy
    autologinAs: cappy
    autologinLocal: true
    - ::1/128
    salt: [REDACTED]

Notice the autologinAs bit and what follows?
See Access Control β€” OctoPrint master documentation

Also notice the spacing is different there in general. yaml is picky about tab spacing. Either adjust to 4 space tabbing or 2.

I just found a config.backup at the .octoprint folder.
It was obviously created automatically before changing the touch-ui settings!?

Server is running now again.

Unfortunately touch-ui is still down :frowning:

Hi again,

I still need some help to get touch-ui back?
My display (attached to the pi) alsways starts up at standard web interface!?

Mind uploading fresh logs?

Are you using a device with a touchscreen?

a fresh log is attached.

octoprint.log (239.7 KB)

My Display is a touch and attached to the Pi, yes.
It was running very well in the past.
Touch-UI was activated automatically.

Since an update, I can not date exactely it is coming up shoing the default web-interface of octopi.
There is no option to switch to touch-ui.

It is the same, if I connect via android-phone.
It was showing touch-UI as well ... currently only the default web-interface.

Does it make sense to uninstall the plugin and install again?

thanks 4 ur help


This is what I did latest:

sudo apt-get upgrade

sudo service touchui stop
cd ~/TouchUI-autostart/ && git pull

sudo cp ~/TouchUI-autostart/touchui.init /etc/init.d/touchui
sudo chmod +x /etc/init.d/touchui
sudo systemctl daemon-reload

sudo service touchui start
sudo reboot

Did not bring up touch-ui :frowning:

Any help ideas!?


Good morning,

I have changed the headline because there are new findings.

Meanwhile OCTOPRINT is running again.

Curiously TOUCH UI is coming up on only a few divices.
I just purchased a new android tablet.
Using chrome to connect octoprint TOUCH UI is loaded automaticlly.
(Resolution is HD)
Wondering about that, I used chrome on my cell phone instead of MiBrowser ... TOUCH UI is comming up as well.

The pi-attached display does not show TOUCH UI and my MiBrowser does still not.

Is there a way to "reset" TOUCH UI to identify the pi-touch as mobile device again?
what should I do?