davidjgonzalez
commented
5 years ago I just ran into this after the QNAP update.
This appears to be a DNS issue - if you open a terminal for the Container and ping registry.npmjs.org it wont get a response, however if you try to ping the IP of registry.npmjs.org (ping 104.16.19.35) - you'll get a response - so the container does have network connectivity, it just cant resolve DNS.
To get around this, I set the Primary/Secondary DNS servers on the lxcbr0:
- Primary: 1.1.1.1 (which is Cloudflare's public DNS)
- Secondary: 8.8.8.8 (which is Google's)
You can, of course, use whatever DNS servers you want.
Make sure to click Apply on the bottom, which will restart your container, and it should work.
HTH!
DNichter
Maximus48p
Hello, looking for some help on an issue. I am using the GUI for QNAP instructions using the marcoraddatz docker. I follow the instructions exactly (I had it up and running without issue before). Now when I add the install.sh and config.json files to the shared folder on my NAS and restart the container. I am getting weird error below. Can anyone help me identify what the issue is?
Installing plugins from /root/.homebridge/install.sh.
npm ERR! code EAI_AGAIN
npm ERR! errno EAI_AGAIN
npm ERR! request to https://registry.npmjs.org/homebridge-netatmo failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org registry.npmjs.org:443
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-10-13T18_48_26_176Z-debug.log
npm ERR! code EAI_AGAIN
npm ERR! errno EAI_AGAIN
npm ERR! request to https://registry.npmjs.org/homebridge-nukiio failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org registry.npmjs.org:443
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-10-13T18_48_48_817Z-debug.log
npm ERR! code EAI_AGAIN
npm ERR! errno EAI_AGAIN
npm ERR! request to https://registry.npmjs.org/homebridge-synology failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org registry.npmjs.org:443
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-10-13T18_49_10_884Z-debug.log
npm ERR! code EAI_AGAIN
npm ERR! errno EAI_AGAIN
npm ERR! request to https://registry.npmjs.org/homebridge-tplink-smarthome failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org registry.npmjs.org:443
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-10-13T18_49_32_939Z-debug.log
npm ERR! code EAI_AGAIN
npm ERR! errno EAI_AGAIN
npm ERR! request to https://registry.npmjs.org/homebridge-nest failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org registry.npmjs.org:443
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-10-13T18_49_55_290Z-debug.log
npm ERR! code EAI_AGAIN
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-10-13T18_50_17_372Z-debug.log
[10/13/2018, 6:50:18 PM] Loaded config.json with 0 accessories and 3 platforms.
[10/13/2018, 6:50:18 PM] ---
[10/13/2018, 6:50:18 PM] No plugins found. See the README for information on installing plugins.
[10/13/2018, 6:50:18 PM] Loading 3 platforms...
/usr/local/lib/node_modules/homebridge/lib/api.js:122
throw new Error("The requested platform '" + name + "' was not registered by any plugin.");
^
Error: The requested platform 'Nest' was not registered by any plugin. (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
at API.platform (/usr/local/lib/node_modules/homebridge/lib/api.js:122:13)
at Server._loadPlatforms (/usr/local/lib/node_modules/homebridge/lib/server.js:316:45)
at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:86:36)
at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:45:10)
at Object.
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)