BillyBlaze / OctoPrint-TouchUI

A touch friendly interface for a small TFT module or phone
https://billyblaze.github.io/OctoPrint-TouchUI/
GNU Affero General Public License v3.0
274 stars 92 forks source link

Cannot connect to TouchUI after Octoprint update #474

Closed bdiesel1369 closed 3 years ago

bdiesel1369 commented 3 years ago

I get a white screen error of localhost refused to connect after upgrading OctoPrint to recent release. I have added allowFraming: true and localNetworks: fixes to respective files and cannot get the localhost refused to connect to work.

saronatart commented 3 years ago

Hi, I have the same problem. No one a solution?

yet-another-average-joe commented 3 years ago

sudo nano ~/pi/TouchUI-autostart/chromium.xinit

In CHROME_ARGS, replace touchui localhost IP with http://0.0.0.0 You may also want to disable pinch if you have a capacitive multitouch : add --disable-pinch

This is what my autostart looks like

CHROME_ARGS=" --no-first-run --kiosk $TOUCHUI_ARGS $TOUCHUI_DEBUG --dns-prefetch-disable --disable-sync-preferences --disk-cache-size=1 --disk-cache-dir=/dev/null --disable-java --disable-plugins --disable-extensions --disable-infobars --user-agent='TouchUI (X11, Chrome $CHROME_VERSION$OCTOPI) (P:$PORT)' --start-maximized --window-position=0,0 --user-data-dir=$CONFIG_DIR --disable-pinch http://0.0.0.0"

(known issue, known fix)

github-actions[bot] commented 3 years ago

This issue has been automatically marked as inactive because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

bdiesel1369 commented 3 years ago

Added the suggested lines and got a different error message. See attached picture. 20210131_153706

yet-another-average-joe commented 3 years ago

I realize the command line is not correct :

sudo nano ~/pi/TouchUI-autostart/chromium.xinit

makes no sense ! It's obviously :

sudo nano ~/TouchUI-autostart/chromium.xinit

Normally http://127.0.0.1 and http://0.0.0.0 work (just tested again). And why isn't OctoPrint service running ????

Did you try :

sudo service octoprint start or restart
sudo service touchui start or restart

And what the log file does tell to you ?

A wrong URL in TouchUI does not prevent octoprint service from starting (AFAIK). There might be something else... I will not be able to test again, as I'm reflashing with the new OctoPi 0.18.0, and will not install TouchUi autostart (not needed with larger screens (7" here : TouchUI can be toggled in OctoPrint menu - witch is impossible with the autostart)

Maybe you should consider that. Your screen looks like it's a 7" or so. Just boot with Chromium in kiosk mode.

bdiesel1369 commented 3 years ago

My screen is a 4 inch THT I/O screen I am not using HMDI to connect to screen. After making changes I rebooted raspberrypi, which should have restarted touchui service I will have to include the log file next.

github-actions[bot] commented 3 years ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.