{"action":"created","issue":{"url":"https://api.github.com/repos/rednut/docker-unifi-controller/issues/5","labels_url":"https://api.github.com/repos/rednut/docker-unifi-controller/issues/5/labels{/name}","comments_url":"https://api.github.com/repos/rednut/docker-unifi-controller/issues/5/comments","events_url":"https://api.github.com/repos/rednut/docker-unifi-controller/issues/5/events","html_url":"https://github.com/rednut/docker-unifi-controller/issues/5","id":127697423,"number":5,"title":"Can't connect","user":{"login":"thom-nic","id":95562,"avatar_url":"https://avatars.githubusercontent.com/u/95562?v=3","gravatar_id":"","url":"https://api.github.com/users/thom-nic","html_url":"https://github.com/thom-nic","followers_url":"https://api.github.com/users/thom-nic/followers","following_url":"https://api.github.com/users/thom-nic/following{/other_user}","gists_url":"https://api.github.com/users/thom-nic/gists{/gist_id}","starred_url":"https://api.github.com/users/thom-nic/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/thom-nic/subscriptions","organizations_url":"https://api.github.com/users/thom-nic/orgs","repos_url":"https://api.github.com/users/thom-nic/repos","events_url":"https://api.github.com/users/thom-nic/events{/privacy}","received_events_url":"https://api.github.com/users/thom-nic/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-01-20T14:44:33Z","updated_at":"2016-01-20T20:04:07Z","closed_at":null,"body":"Apologies as I suspect this is a PEBCAK but for some reason even though I can see the listening ports and running java process, every connect attempt is closed immediately.  \r\n\r\nif I `docker-machine ssh` into the box I can see the listening ports and running java process but still can't connect:\r\n```\r\ndocker@dev:~$ netstat -anlt\r\nActive Internet connections (servers and established)\r\nProto Recv-Q Send-Q Local Address           Foreign Address         State       \r\ntcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      \r\ntcp        0      0 10.0.2.15:22            10.0.2.2:53390          ESTABLISHED \r\ntcp        0      0 :::8080                 :::*                    LISTEN      \r\ntcp        0      0 :::8880                 :::*                    LISTEN      \r\ntcp        0      0 :::22                   :::*                    LISTEN      \r\ntcp        0      0 :::8443                 :::*                    LISTEN      \r\ntcp        0      0 :::37117                :::*                    LISTEN      \r\ntcp        0      0 :::2376                 :::*                    LISTEN      \r\ndocker@dev:~$ curl http://localhost:8080\r\ncurl: (52) Empty reply from server\r\ndocker@dev:~$ curl http://localhost:8880\r\ncurl: (52) Empty reply from server\r\ndocker@dev:~$ curl https://localhost:8443\r\ncurl: (35) Unknown SSL protocol error in connection to localhost:8443 \r\n```\r\n\r\nJava process is running but not mongod:\r\n```\r\ndocker@dev:~$ ps ax|grep java\r\n 7196 ?        SNl    0:04 /usr/lib/jvm/java-6-openjdk-amd64/jre/bin/java -Xmx256M -jar /usr/lib/unifi/lib/ace.jar start\r\n 7467 pts/0    S+     0:00 grep java\r\ndocker@dev:~$ ps ax|grep mongo\r\n 7478 pts/0    S+     0:00 grep mongo\r\n```\r\n\r\nHowever no errors in the log:\r\n```\r\n$ docker logs unifi\r\n/usr/lib/python2.7/dist-packages/supervisor/options.py:295: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a \"-c\" argument specifying an absolute path to a configuration file for improved security.\r\n  'Supervisord is running as root and it is searching '\r\n2016-01-20 14:38:59,688 CRIT Supervisor running as root (no user in config file)\r\n2016-01-20 14:38:59,688 WARN Included extra file \"/etc/supervisor/conf.d/supervisord.conf\" during parsing\r\n2016-01-20 14:38:59,704 INFO RPC interface 'supervisor' initialized\r\n2016-01-20 14:38:59,704 CRIT Server 'unix_http_server' running without any HTTP authentication checking\r\n2016-01-20 14:38:59,704 INFO supervisord started with pid 1\r\n2016-01-20 14:39:00,708 INFO spawned: 'unify' with pid 8\r\n2016-01-20 14:39:01,709 INFO success: unify entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)\r\n```\r\n\r\nAny thoughts?"},"comment":{"url":"https://api.github.com/repos/rednut/docker-unifi-controller/issues/comments/173344283","html_url":"https://github.com/rednut/docker-unifi-controller/issues/5#issuecomment-173344283","issue_url":"https://api.github.com/repos/rednut/docker-unifi-controller/issues/5","id":173344283,"user":{"login":"thom-nic","id":95562,"avatar_url":"https://avatars.githubusercontent.com/u/95562?v=3","gravatar_id":"","url":"https://api.github.com/users/thom-nic","html_url":"https://github.com/thom-nic","followers_url":"https://api.github.com/users/thom-nic/followers","following_url":"https://api.github.com/users/thom-nic/following{/other_user}","gists_url":"https://api.github.com/users/thom-nic/gists{/gist_id}","starred_url":"https://api.github.com/users/thom-nic/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/thom-nic/subscriptions","organizations_url":"https://api.github.com/users/thom-nic/orgs","repos_url":"https://api.github.com/users/thom-nic/repos","events_url":"https://api.github.com/users/thom-nic/events{/privacy}","received_events_url":"https://api.github.com/users/thom-nic/received_events","type":"User","site_admin":false},"created_at":"2016-01-20T20:04:07Z","updated_at":"2016-01-20T20:04:07Z","body":"I did use `-v` as described in the README like so `-v /usr/local/lib/unifi/data:/usr/lib/unifi/data` but the directory is empty on my host side.  Should I only use it if I have a preexisting unifi controller data dir?  I was expecting the dockerized controller to bootstrap and add data to that directory on first boot but it's still empty. No logs directory.  \r\n\r\nAlthough now I wonder if I'm experiencing this https://github.com/docker-library/mysql/issues/44#issuecomment-73318805 since yes, I am on osx and using `docker-machine` which uses boot2docker under the hood..."}}