Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong server status of running services only on iOS browsers #238

Closed
kennymc-c opened this issue Mar 23, 2019 · 7 comments
Closed

Wrong server status of running services only on iOS browsers #238

kennymc-c opened this issue Mar 23, 2019 · 7 comments

Comments

@kennymc-c
Copy link
Contributor

When I access the config page on my iPhone X / iOS 12.1.4, the services (Homebridge / Console) are displayed as not running with both safari and chrome. The search for Homebridge updates also takes forever. On macOS they are displayed as running and that's correct. I also can't reproduce it by changing the user agent on the Mac. I've had this problem before when I haven't switched to the Docker Image. But after that it didn't happen anymore. Now it has occurred again. Could it be related to the new update to 3.10?

@oznu
Copy link
Member

oznu commented Mar 23, 2019

It sounds like the web socket connection is not being established.

I can't replicate this issue on the same version of iOS. Perhaps try clearing your browser cache / try a private tab?

The changes in 3.10.0 were mainly cosmetic.

@kennymc-c
Copy link
Contributor Author

Clearing Browser cache or using a private tab didn‘t help

@oznu
Copy link
Member

oznu commented Apr 17, 2019

Changes in 4.0.0 to how WebSockets are handled may have fixed this.

@kennymc-c
Copy link
Contributor Author

kennymc-c commented Apr 17, 2019

I'm afraid not. What I noticed before the update was that when I opened the log an error message appeared saying that the connection to the WebSocket could not be established. This message does not appear any more and the log remains completely empty. However, if you return from the console tab, the status for the console changes to green. Nevertheless the log remains empty.

@oznu
Copy link
Member

oznu commented Apr 19, 2019

@kennymc-c, I've added a new flag websocketCompatibilityMode. This will allow socket.io to fallback to using xhr/polling if a native WebSocket connection cannot be established. After upgrading to 4.0.2 you can enable this by setting "websocketCompatibilityMode": true. Example:

"platforms": [
    {
      "platform": "config",
      "name": "Config",
      "port": 8080,
      "websocketCompatibilityMode": true,
      ... // the rest of your config
    }
]

@kennymc-c
Copy link
Contributor Author

Enabling websocketCompatibilityMode solved my problem. Thanks!

@oznu
Copy link
Member

oznu commented Apr 19, 2019

Thanks for confirming!

@oznu oznu closed this as completed Apr 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants