{"action":"created","issue":{"url":"https://api.github.com/repos/home-assistant/home-assistant/issues/17678","repository_url":"https://api.github.com/repos/home-assistant/home-assistant","labels_url":"https://api.github.com/repos/home-assistant/home-assistant/issues/17678/labels{/name}","comments_url":"https://api.github.com/repos/home-assistant/home-assistant/issues/17678/comments","events_url":"https://api.github.com/repos/home-assistant/home-assistant/issues/17678/events","html_url":"https://github.com/home-assistant/home-assistant/issues/17678","id":372362323,"node_id":"MDU6SXNzdWUzNzIzNjIzMjM=","number":17678,"title":"Google WiFi component issue","user":{"login":"deanrparry","id":9539280,"node_id":"MDQ6VXNlcjk1MzkyODA=","avatar_url":"https://avatars0.githubusercontent.com/u/9539280?v=4","gravatar_id":"","url":"https://api.github.com/users/deanrparry","html_url":"https://github.com/deanrparry","followers_url":"https://api.github.com/users/deanrparry/followers","following_url":"https://api.github.com/users/deanrparry/following{/other_user}","gists_url":"https://api.github.com/users/deanrparry/gists{/gist_id}","starred_url":"https://api.github.com/users/deanrparry/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/deanrparry/subscriptions","organizations_url":"https://api.github.com/users/deanrparry/orgs","repos_url":"https://api.github.com/users/deanrparry/repos","events_url":"https://api.github.com/users/deanrparry/events{/privacy}","received_events_url":"https://api.github.com/users/deanrparry/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-10-21T22:10:31Z","updated_at":"2018-10-22T18:33:34Z","closed_at":null,"author_association":"NONE","body":"I run a docker container with latest 0.80.3 home assistant and obviously google wifi :)\r\n\r\nNow i cannot confirm which is the issue as they happened at the same time...\r\n\r\n1. the upnp stuff incorporated into the latest home assistant version\r\n\r\nor\r\n\r\n2. a google wifi update was installed on the same day\r\n\r\nBasically what happens is it kills loopback attempts and ALL other containers get killed aswell and are only accessible remotely with port forwarding or local with ip address, you cannot use ddns name etc...\r\n\r\nWhat does happen is on an attempt to login using ddns local when i eventually login via local ip it shows a persistent notification with a failed login attempt from 192.168.86.1 which is my routers address which is what made me disable the google_wifi: component and low and behold i am back to normal service!\r\n\r\nthank you"},"comment":{"url":"https://api.github.com/repos/home-assistant/home-assistant/issues/comments/431927865","html_url":"https://github.com/home-assistant/home-assistant/issues/17678#issuecomment-431927865","issue_url":"https://api.github.com/repos/home-assistant/home-assistant/issues/17678","id":431927865,"node_id":"MDEyOklzc3VlQ29tbWVudDQzMTkyNzg2NQ==","user":{"login":"deanrparry","id":9539280,"node_id":"MDQ6VXNlcjk1MzkyODA=","avatar_url":"https://avatars0.githubusercontent.com/u/9539280?v=4","gravatar_id":"","url":"https://api.github.com/users/deanrparry","html_url":"https://github.com/deanrparry","followers_url":"https://api.github.com/users/deanrparry/followers","following_url":"https://api.github.com/users/deanrparry/following{/other_user}","gists_url":"https://api.github.com/users/deanrparry/gists{/gist_id}","starred_url":"https://api.github.com/users/deanrparry/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/deanrparry/subscriptions","organizations_url":"https://api.github.com/users/deanrparry/orgs","repos_url":"https://api.github.com/users/deanrparry/repos","events_url":"https://api.github.com/users/deanrparry/events{/privacy}","received_events_url":"https://api.github.com/users/deanrparry/received_events","type":"User","site_admin":false},"created_at":"2018-10-22T18:33:34Z","updated_at":"2018-10-22T18:33:34Z","author_association":"NONE","body":"Something broke it and it's one of the above ;-) when the component is activated it causes havoc with all other containers in docker, don't care if it gets fixed or not but the decent thing is to report the issue for other poor users that get caught by this horrible bug"}}
{"actor":{"display_login":"deanrparry"}}