Another update: Solved!
viewtopic.php?f=7&t=13646
Update!
I have narrowed it down to Apple/Safari/OSX/iOS issues and how OSX Safari and iOS handle communication with port 9999. Seems inbound communication from RPI on that port is blocked by Apple. Researching.
Chrome and Waterfox on OSX devices work well. Safari does not.
On iOS, neither Safari nor Chrome operate (I assume port 9999 is problematic at a lower level in the os...)
Android devices (Chrome) works fine.
Is Apple being overprotective?
Can another port other than 9999 be used?
-------------------------
OP...
Making progress. Created scenes and virtual console buttons QLC+ on MAC, everything fine.
Loaded .qxw file on Raspberry Pi, use Chrome on MAC Mojave 10.14.6 to log on and run on Pi. Everything fine.
Shut down MAC, connect via Android tablet. Everything works as expected.
Shut down Andriod, and connect via iPad Pro running IOS 12.3.1, open Chrome browser,
I log on using name & pw, then get QLC+ Connection Error! hit OK then QLC+ connection lost!
Choice of OK or Suppress Dialogs. Either choice shows Virtual Console, but is more or less dead.
Same on older iPad running IOS 9.3.6.
iPads work on everything else flawlessly, only have errors w/Pi running Masimos QLC+ image unmodified.
MAC and PI hardwired to router.
Android and iPads via WiFi.
Any ideas?
Something new:
MAC connecting via WiFi and Safari presenting the same problems as iPads.
MAC connecting via WiFi using Chrome or Waterfox running properly.
Maybe something with port issues on Safari and IOS devices.
iPad-QLC+ Connection Error!
-
fronk
- Posts: 10
- Joined: Sun Feb 17, 2019 4:54 pm
- Location: MD USA
- Real Name: frank kayser
So, let me ask another way:
Is there anyone using iPad to connect via websockets to the QLC+ app on Raspberry Pi using stock, unchanged image by Masimo?
Please just give me a yes or no (I've seen some using TouchOSC running on iPad, but that's not using the browser...)
From what I'm finding on the web, my belief is that Safari has either blocked, or more likely needs another "piece" to get websockets working - not a port 9999 issue.
Of course, I may be on the wrong track. An online test confirms websockets enabled.
WebSocket supported here!
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6)
AppleWebKit/605.1.15 (KHTML, like Gecko)
Version/12.1.2 Safari/605.1.15
test by jimbergman.net (based on Google sample code)
Similar message when same test performed with iPhone SE.
Is there anyone using iPad to connect via websockets to the QLC+ app on Raspberry Pi using stock, unchanged image by Masimo?
Please just give me a yes or no (I've seen some using TouchOSC running on iPad, but that's not using the browser...)
From what I'm finding on the web, my belief is that Safari has either blocked, or more likely needs another "piece" to get websockets working - not a port 9999 issue.
Of course, I may be on the wrong track. An online test confirms websockets enabled.
WebSocket supported here!
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6)
AppleWebKit/605.1.15 (KHTML, like Gecko)
Version/12.1.2 Safari/605.1.15
test by jimbergman.net (based on Google sample code)
Similar message when same test performed with iPhone SE.
-
fronk
- Posts: 10
- Joined: Sun Feb 17, 2019 4:54 pm
- Location: MD USA
- Real Name: frank kayser
Ah HA!
A different online test gave somewhat different results:
With Safari browser: Some immediate disconnects. One wonders...
Of note, the tests do not test port 9999, rather some other standardized ports.
WebSockets
Might Work for You!
Environment
WebSockets supported Yes✔
HTTP Proxy No
WebSocket protocol version rfc-6455
WebSockets (Port 80)
Connected No✘ Disconnected at 17:55:13
Data Receive Yes✔
Data Send Yes✔
Echo Test Yes✔
Server time 2019/8/16 21:57:00
WebSockets (Port 8080)
Connected Yes✔
Data Receive Yes✔
Data Send Yes✔
Echo Test Yes✔
Server time 2019/8/16 21:59:33
WebSockets (Port 443, SSL)
Connected No✘ Disconnected at 17:55:13
Data Receive Yes✔
Data Send Yes✔
Echo Test Yes✔
Server time 2019/8/16 21:57:00
Additional Details
Antivirus Name
Antivirus version
Result ID: 19043818
---------------------------------
And the same test using Waterfox...
WebSockets seem to
Work for You!
Environment
WebSockets supported Yes✔
HTTP Proxy No
WebSocket protocol version rfc-6455
WebSockets (Port 80)
Connected Yes✔
Data Receive Yes✔
Data Send Yes✔
Echo Test Yes✔
Server time 2019/8/16 22:07:16
WebSockets (Port 8080)
Connected Yes✔
Data Receive Yes✔
Data Send Yes✔
Echo Test Yes✔
Server time 2019/8/16 22:07:16
WebSockets (Port 443, SSL)
Connected Yes✔
Data Receive Yes✔
Data Send Yes✔
Echo Test Yes✔
Server time 2019/8/16 22:07:16
Additional Details
Antivirus Name
Antivirus version
Result ID: 19043829
This test was created to study implications of using WebSockets in real-life scenarios. Having WebSockets supported in your browser doesn't guarantee they will work for you. Antiviruses, firewalls and HTTP proxies may interfere WebSocket connections, sometimes rendering them useless.
On this page you can see how well WebSockets can work with your Internet Connection, your Antivirus and all other software you have. The test checks WebSocket operation by connecting to the WebSocket-enabled server and exchanging the data. The time displayed in "Server time" line should update every second if WebSockets work for you.
This server supports WebSocket Protocol proposed standard (RFC-6455, December 2011), per-frame-deflate-extension-00 draft, older websocket drafts as well as even older Hixie drafts 75 and 76 (August 2010) with the fix for HTTP reverse proxies.
Jan 31, 2011 - version 1.2
This test was created by Mikhail Platov, inspired by HTML5 test created by Niels Leenheer.
Hosted by:
Godville
Aggregated test results.
A different online test gave somewhat different results:
With Safari browser: Some immediate disconnects. One wonders...
Of note, the tests do not test port 9999, rather some other standardized ports.
WebSockets
Might Work for You!
Environment
WebSockets supported Yes✔
HTTP Proxy No
WebSocket protocol version rfc-6455
WebSockets (Port 80)
Connected No✘ Disconnected at 17:55:13
Data Receive Yes✔
Data Send Yes✔
Echo Test Yes✔
Server time 2019/8/16 21:57:00
WebSockets (Port 8080)
Connected Yes✔
Data Receive Yes✔
Data Send Yes✔
Echo Test Yes✔
Server time 2019/8/16 21:59:33
WebSockets (Port 443, SSL)
Connected No✘ Disconnected at 17:55:13
Data Receive Yes✔
Data Send Yes✔
Echo Test Yes✔
Server time 2019/8/16 21:57:00
Additional Details
Antivirus Name
Antivirus version
Result ID: 19043818
---------------------------------
And the same test using Waterfox...
WebSockets seem to
Work for You!
Environment
WebSockets supported Yes✔
HTTP Proxy No
WebSocket protocol version rfc-6455
WebSockets (Port 80)
Connected Yes✔
Data Receive Yes✔
Data Send Yes✔
Echo Test Yes✔
Server time 2019/8/16 22:07:16
WebSockets (Port 8080)
Connected Yes✔
Data Receive Yes✔
Data Send Yes✔
Echo Test Yes✔
Server time 2019/8/16 22:07:16
WebSockets (Port 443, SSL)
Connected Yes✔
Data Receive Yes✔
Data Send Yes✔
Echo Test Yes✔
Server time 2019/8/16 22:07:16
Additional Details
Antivirus Name
Antivirus version
Result ID: 19043829
This test was created to study implications of using WebSockets in real-life scenarios. Having WebSockets supported in your browser doesn't guarantee they will work for you. Antiviruses, firewalls and HTTP proxies may interfere WebSocket connections, sometimes rendering them useless.
On this page you can see how well WebSockets can work with your Internet Connection, your Antivirus and all other software you have. The test checks WebSocket operation by connecting to the WebSocket-enabled server and exchanging the data. The time displayed in "Server time" line should update every second if WebSockets work for you.
This server supports WebSocket Protocol proposed standard (RFC-6455, December 2011), per-frame-deflate-extension-00 draft, older websocket drafts as well as even older Hixie drafts 75 and 76 (August 2010) with the fix for HTTP reverse proxies.
Jan 31, 2011 - version 1.2
This test was created by Mikhail Platov, inspired by HTML5 test created by Niels Leenheer.
Hosted by:
Godville
Aggregated test results.