unable to connect to homebridge running on docker
I followed the blog post on setting up homebridge on docker, but I can't connect to the container through the url.
the networking is set to use host
my Firewalla gold is set to router mode
the container shows running, but I can't connect - I tried several different ports and also tried to reset the docker install
-
Michael,
Thank you for all your efforts on this project!
Just posting this here in case you or someone else has any insight as to why this error is appearing after running the script. Docker says the container is running, but it looks like node has an issue:
Docker version 19.03.6, build 369ce74a3c
Homebridge Terminal
Node.js Version: v20.12.2
Node.js Path:
Plugin Path: /var/lib/homebridge/node_modules
Update Node.js: hb-service update-node
Install Plugin: hb-service add homebridge-plugin-name
Remove Plugin: hb-service remove homebridge-plugin-nameERROR:
# node[611]: std::unique_ptr<long unsigned int> node::WorkerThreadsTaskRunner::DelayedTaskScheduler::Start() at ../src/node_platform.cc:68
# Assertion failed: (0) == (uv_thread_create(t.get(), start_thread, this))
----- Native stack trace -----
1: 0xccd047 node::Assert(node::AssertionInfo const&) [node]
2: 0xd4c2ee node::WorkerThreadsTaskRunner::WorkerThreadsTaskRunner(int) [node]
3: 0xd4c3cc node::NodePlatform::NodePlatform(int, v8::TracingController*, v8::PageAllocator*) [node]
4: 0xc6f786 [node]
5: 0xc70c84 node::Start(int, char**) [node]
6: 0x7f9aae814d90 [/lib/x86_64-linux-gnu/libc.so.6]
7: 0x7f9aae814e40 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
8: 0xbc7afe _start [node]
Aborted (core dumped) -
Michael,
Wow, I appreciate the assistance if you do uncover something, in addition to all the time you have already spent on this, including working with other users!
My take or my knee-jerk reaction was to upgrade the version of Docker installed, but I hesitated because I haven't fully checked everywhere under the hood of the 🔥Firewalla box yet so-to-speak, and I assume there are a number of customizations or deviations from a standard Ubuntu install. -
I attempted setup ~6 months ago, failed, and backed off to an older oznu one that worked. But I was unable to update or add new plug-ins. So now back at it for the newer version because I REALLY want to get it working for additional plugins.
First I removed all traces of the Homebridge docker images, containers, data directory, and docker-compose directory. Then I ran Michael Bierman's script identified previously in this stream, and all appeared to work fine, and the homebridge docker container running when I do a "docker ps". But similarly, I can't connect to the UI via browser. I also notice that no config.json is created in /data/homebridge, so I can't even edit that for mdns changes prescribed. If I tail the docker log, I get the following messages repeating infinitely with a new set every couple seconds:
Re-installing homebridge...
# node[470]: std::unique_ptr<long unsigned int> node::WorkerThreadsTaskRunner::DelayedTaskScheduler::Start() at ../src/node_platform.cc:68
# Assertion failed: (0) == (uv_thread_create(t.get(), start_thread, this))
----- Native stack trace -----
1: 0xcc25c7 node::Assert(node::AssertionInfo const&) [node]
2: 0xd4272e node::WorkerThreadsTaskRunner::WorkerThreadsTaskRunner(int) [node]
3: 0xd4280c node::NodePlatform::NodePlatform(int, v8::TracingController*, v8::PageAllocator*) [node]
4: 0xc76427 [node]
5: 0xc77984 node::Start(int, char**) [node]
6: 0x7f74c1863d90 [/lib/x86_64-linux-gnu/libc.so.6]
7: 0x7f74c1863e40 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
8: 0xbcae3e _start [node]
Aborted (core dumped)
# /opt/homebridge/bin/node[467]: std::unique_ptr<long unsigned int> node::WorkerThreadsTaskRunner::DelayedTaskScheduler::Start() at ../src/node_platform.cc:68
# Assertion failed: (0) == (uv_thread_create(t.get(), start_thread, this))
----- Native stack trace -----
1: 0xcc25c7 node::Assert(node::AssertionInfo const&) [/opt/homebridge/bin/node]
2: 0xd4272e node::WorkerThreadsTaskRunner::WorkerThreadsTaskRunner(int) [/opt/homebridge/bin/node]
3: 0xd4280c node::NodePlatform::NodePlatform(int, v8::TracingController*, v8::PageAllocator*) [/opt/homebridge/bin/node]
4: 0xc76427 [/opt/homebridge/bin/node]
5: 0xc77984 node::Start(int, char**) [/opt/homebridge/bin/node]
6: 0x7f08770fed90 [/lib/x86_64-linux-gnu/libc.so.6]
7: 0x7f08770fee40 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
8: 0xbcae3e _start [/opt/homebridge/bin/node]I've tried rebooting the Firewalla as well, removing all signs of Docker and HomeBridge and starting from scratch, but same thing happens.
Some pertinent info:
Firewalla Gold, Box version 1.9780 (Release Type: Stable Release)
OS Release is: Ubuntu 18.04.3 LTS (Bionic Beaver)
"lsb_release -rs" yields "18.04"
Any and all help is SO much appreciated!
-
So you can flash your Gold to a later version of the OS—22. I don’t remember off the top of my head which version of node is installed, but there is no issue with running latest homebridge with the latest firewalla. I can check if there’s an issue with the older 18.x build and post back.
Update: I don't have a box that has 18.x handy so it isn't easy for me to confirm if there are issues with 18 and latest homebridge, but to the best of my knowledge there is not an issue.Very likely the issue could be with the homebridge plugins as they are going through some changes that require plugins to update. This isn’t a firewalla related issue.
How are you trying to connect to homebridge after iinstall?
Update: I updated the uninstall instructions slightly. You could also try removing and starting again. I suggest testing with just homebridge before you try adding any plugins. If that works you can be sure homebridge is running and you can contact the plugin owner to see if they will update for the latest homebridge.
Please sign in to leave a comment.
Comments
8 comments