You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a self-hosed Supla Cloud instance running via docker on my Synology NAS. This is reachable via https://192.168.20.3:8089 (from my internal network only). I can reach the web UI easily with this address.
However, I can't get the iOS app to accept this address - I just get a 'Host not found' error. I thought perhaps it required a domain so I setup a rule in my DNS resolver to resolve a domain name to that IP and tried that but no joy. This is currently blocking my Supla deployment so I'd be keen to get it sorted!
I've had a look through the iOS sources (I'm an experienced iOS engineer and have determined that the error is originating from supla_client_connect in the supla-core C library rather than the iOS code, but since it's impacting the iOS app, have raised the bug here.
The text was updated successfully, but these errors were encountered:
I've sat it in front of a reverse proxy to get it onto port 443 and a trusted certificate to prevent SSL challenges which has solved the problem. (443 is contested heavily on this host so needed to be reverse proxied by hostname.)
Likely worth a couple of lines in the supla-docker README highlighting this limitation as the docs talk about changing to non-standard ports without mentioning that the iOS (and presumably Android) clients aren't compatible with non-standard ports.
In time it'd be nice to have the option of specifying a port in the client apps but that's obviously a more involved solution than a documentation update.
I have a self-hosed Supla Cloud instance running via docker on my Synology NAS. This is reachable via https://192.168.20.3:8089 (from my internal network only). I can reach the web UI easily with this address.
However, I can't get the iOS app to accept this address - I just get a 'Host not found' error. I thought perhaps it required a domain so I setup a rule in my DNS resolver to resolve a domain name to that IP and tried that but no joy. This is currently blocking my Supla deployment so I'd be keen to get it sorted!
Tried:
192.168.20.3:8089
https://192.168.20.3:8080
192.168.20.3:8089
http://192.168.20.3:8088
mydomain:8099
I've had a look through the iOS sources (I'm an experienced iOS engineer and have determined that the error is originating from
supla_client_connect
in the supla-core C library rather than the iOS code, but since it's impacting the iOS app, have raised the bug here.The text was updated successfully, but these errors were encountered: