-
Notifications
You must be signed in to change notification settings - Fork 147
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
Debian 10 won't run this module #252
Comments
Following the advice from homebridge/homebridge#613: I rebooted the system, just to make sure everything is going, and no change:
|
Found this: https://www.truenas.com/community/threads/try-to-run-airsonos-issue-with-registering-on-the-network.36428/ There user @tslw says there are Went to https://manpages.debian.org/testing/avahi-daemon/avahi-daemon.conf.5.en.html and discovered the Avahi configuration file is located at /etc/avahi/avahi-daemon.conf. So I Still no change in result. |
Hi, I have encountered this error when a device is registered in avahi (it was found on the local network) but could no longer be resolved (I think it's the job of
In
(copied from mine, may vary. The important bit is If you don't care about name resolution, you can customize the name resolution step in mdns to skip it. |
Hi I am getting same error as described above. Any updates @cjohnweb ? My environment is
|
Here's some context:
On a new, small express sample project I
npm install mdns --save
Then I write a simple piece of server side code in a class to broadcast that I have a web server on port 80, which looks something like this:
But when I
npm start
, I get the following:So line 31 of my service-mdns.js looks like this:
const httpAd = mdns.createAdvertisement(mdns.tcp('http'), parseInt(port))
I've read some projects which claim that lines starting with
*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
is normal and to just ignore it. But as you can see, I can't simply ignore it. I've installed previous versions, like 5.2.1. I've tried installing/updating everything from my build tools to the avahi library installed on my system.I'm assuming it's an issue with the npm package, but I'm not certain. Is anyone else having similar issues? If so, what fixed it for you? Or is this package being phased out as some claim?
Thanks
PS. My package.json file:
The text was updated successfully, but these errors were encountered: