Pi touchscreen fails to display but works on remote browser

[mannyr7]

I have Octoprint working and TouchUI installed. On the pi, Octoprint starts and TouchUI starts but stalls on the "Connectng to TouchUI" splashscreen. When I load octopi.local remotely on my Windows browser, Touch UI displays correctly and is connected to octoprint. So it appears perhaps this could be related to pi's Chromium or the modal frame failing to connect to octoprint and maybe TouchUI is waiting for that to happen? This is a RPi model B+ (I am not attempting to print from this, only configuring this to pop the SD into a RPi 3 or 4 soon), Octoprint / OctoPI versions 1.4.0 / 0.17.0, TouchUI version current as of June 13, 2020. Config.yaml follows: (I X'd out any keys or IDs, there are valid values in the actual file) accessControl: autologinAs: XXXXXXXXXXX autologinLocal: true localNetworks:

• 127.0.0.1/8
• ::1/128 salt: XXXXXXXXXXXXXXXXXXXXXXXXXXX api: key: XXXXXXXXXXXXXXXXXXXXXXXXXXXX plugins: announcements: _config_version: 1 channels: _blog: read_until: 1589460900 _important: read_until: 1521111600 _octopi: read_until: 1573722900 _plugins: read_until: 1591938000 _releases: read_until: 1583322300 cura: cura_engine: /usr/local/bin/cura_engine discovery: publicPort: 80 upnpUuid: XXXXX errortracking: unique_id: XXXXX softwareupdate: _config_version: 7 tracking: enabled: false unique_id: XXXXXXXX printerProfiles: default: _default server: allowFraming: true

[stale[bot]]

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.

[github-actions[bot]]

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.