Troubleshooting

NPM Registry Issues

Error messages include:

• Failed to check registry.npmjs.org for updates ...
• Failed to search the npm registry ...

This is not an issue with Homebridge Config UI X in most cases.

Look for these keywords in the error message to help troubleshoot the issue:

• getaddrinfo - your DNS resolver could not resolve registry.npmjs.org. Check your internet connection and DNS settings.
• ETIMEDOUT or Timeout - the request took to long, the npm registry may be down, slow, or you may have internet issues, check https://status.npmjs.org/.
• Request failed with status code 503 - the npm registry is down, check https://status.npmjs.org/.
• certificate has expired - check the date / time on your server is correct
• certificate is not yet valid - check the date / time on your server is correct

Eero Routers

If you are using an Eero brand router, see How To Fix Eero Router Internet and DNS Connectivity Issues.

Multiple Instances Of Homebridge Found Installed

This message will be displayed when the UI has found multiple copies of Homebridge installed in different locations. This is usually caused by multiple versions of Node.js installed using different methods.

See the following guides to fix your setup:

• How To Fix Node.js Install Issues On Linux
• How To Fix Node.js Install Issues On macOS

If you're running on Docker, run this command inside the container:

npm uninstall homebridge
rm -rf /homebridge/node_modules/homebridge

Unable To Find Homebridge Installation

This message is displayed when the UI cannot find the Homebridge package. Try installing it:

sudo npm install -g --unsafe-perm homebridge