Failed to establish a new connection: [Errno 113] No route to host

[cheme75]

Sorry if already addressed elsewhere - did not see this mentioned exactly elsewhere - just started getting this error - I am not using 2FA yet - most of the similar errors mention 2FA issues so not sure why its not connecting tp authenticate - if addressed else where, would appreciate a pointer to the issue. FWIW, homebridge is still connecting just fine and the bulbs and plugs are working in homekit - seems just this bridge is not connecting for the cams. Note: tried using the beta url for login, it failed as well.

2022/11/10 10:50:55 [WyzeBridge] 🚀 STARTING DOCKER-WYZE-BRIDGE v1.9.0

2022/11/10 10:50:55 [WyzeBridge] LL-HLS Enabled 2022/11/10 10:50:55 [WyzeBridge] 🔐 Generating key for LL-HLS

• Serving Flask app 'frontend'
• Debug mode: off 2022/11/10 10:50:55 [WyzeBridge] WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
• Running on all addresses (0.0.0.0)
• Running on http://127.0.0.1:5000
• Running on http://172.18.0.2:5000 2022/11/10 10:50:55 [WyzeBridge] Press CTRL+C to quit 2022/11/10 10:50:55 [WyzeBridge] 🔏 Generating certificate for LL-HLS 2022/11/10 10:50:55 [WyzeBridge] 🔍 Could not find local cache for 'user' 2022/11/10 10:50:55 [WyzeBridge] 🔍 Could not find local cache for 'auth' 2022/11/10 10:50:55 [WyzeBridge] ☁️ Fetching 'auth' from the Wyze API... 2022/11/10 10:51:14 [WyzeBridge] HTTPSConnectionPool(host='auth-prod.api.wyze.com', port=443): Max retries exceeded with url: /user/login (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fed8dd494e0>: Failed to establish a new connection: [Errno 113] No route to host')) 2022/11/10 10:51:39 [WyzeBridge] ☁️ Fetching 'auth' from the Wyze API... 2022/11/10 10:51:54 [WyzeBridge] HTTPSConnectionPool(host='auth-prod.api.wyze.com', port=443): Max retries exceeded with url: /user/login (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fed8ee41720>: Failed to establish a new connection: [Errno 113] No route to host'))

[cheme75]

Update - waited a few hrs, shutdown docker desktop, restarted, restarted bridge, all is good! Maybe some oddball wyze glitch.

[cheme75]

I now see this is similar to #580 - however, I did have docker running as admin. Simply exxiting docker desktop and restarting it seems to fix the glitch. However, I found that it was only successful for the 3 "retail" wyze cams - the beta db3 I'm using still work in the wyze app for live streaming and are still being accepted by their qr code when adding to the app - and tthey were connecting to the bridge and working fine until just recently with this connection error - I removed the beta db3 from my white list and all seems fine. Anyone else out there using a beta cam?

[mrlt8]

The bridge should pull the data for all cameras on the account in one request, so it shouldn't matter if they're beta or not. You can cache the wyze data locally so the bridge doesn't have to talk to they wyze servers by mounting the tokens directory locally with something like:

volumes:
    - /path/to/local/tokens/:/tokens/

[cheme75]

Wasn’t clear on that exactly. I unfortunately cleared the log after the restart with new white list so can’t show it - will try the tokens volume.

I assume the path should be fully qualified like: volumes:

• c:/docker/bridge/tokens/ : /tokens/

does this require also mounting the volume in docker?

[mrlt8]

I actually have mine set to relative so everything is in the same directory:

./tokens/:/tokens/

[cheme75]

I actually have mine set to relative so everything is in the same directory:

./tokens/:/tokens/

ok will try it this way.

[cheme75]

here's yml - i see some files in the /tokens folder now: version: '2.4' services: wyze-bridge: container_name: wyze-bridge restart: unless-stopped image: mrlt8/wyze-bridge:latest ports:

• 1935:1935
• 8554:8554
• 8888:8888
• 5000:5000 volumes:
• ./tokens/:/tokens/ environment:
• TZ=America/New_York
• WYZE_EMAIL=myemail@gmail.com
• WYZE_PASSWORD=1234-abcd@5678&9
• FRESH_DATA=true
• IGNORE_OFFLINE=true
• FILTER_NAMES=front-door, entry, patio, gatecam
• ROTATE_DOOR=True
• ROTATE_CAM_ENTRY=true
• LLHLS=true
• ON_DEMAND=true

here's error - think I'll reboot machine - seems like maybe a system service glitch maybe? 2022/11/11 23:19:10 [WyzeBridge] 🚀 STARTING DOCKER-WYZE-BRIDGE v1.9.0

2022/11/11 23:19:10 [WyzeBridge] LL-HLS Enabled

• Serving Flask app 'frontend'
• Debug mode: off 2022/11/11 23:19:10 [WyzeBridge] WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
• Running on all addresses (0.0.0.0)
• Running on http://127.0.0.1:5000
• Running on http://172.18.0.2:5000 2022/11/11 23:19:10 [WyzeBridge] Press CTRL+C to quit 2022/11/11 23:19:10 [WyzeBridge] 🔍 Could not find local cache for 'user' 2022/11/11 23:19:10 [WyzeBridge] 🔍 Could not find local cache for 'auth' 2022/11/11 23:19:10 [WyzeBridge] ☁️ Fetching 'auth' from the Wyze API... 2022/11/11 23:19:22 [WyzeBridge] HTTPSConnectionPool(host='auth-prod.api.wyze.com', port=443): Max retries exceeded with url: /user/login (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7efc8b46d4e0>: Failed to establish a new connection: [Errno 113] No route to host')) 2022/11/11 23:19:47 [WyzeBridge] ☁️ Fetching 'auth' from the Wyze API... 2022/11/11 23:20:00 [WyzeBridge] HTTPSConnectionPool(host='auth-prod.api.wyze.com', port=443): Max retries exceeded with url: /user/login (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7efc8c571720>: Failed to establish a new connection: [Errno 113] No route to host'))

[mrlt8]

hmm. could you try:

docker-compose down
docker-compose up

[cheme75]

hmm. could you try:

docker-compose down
docker-compose up

Tried a restart before I saw this and docker failed to find vm. So some weird glitch - maybe file corruption during power blip. Uninstalled/reinstalling docker now. Will see how it goes, this is the latest docker update.

[cheme75]

Update: reinstalled docker 4.12 and ignoring the update just in case something in the update is causing problems. Now have the user, auth and other key files in /tokens/. Pulled container and now running all 4 cams again - 2 v2, 1 db3, 1 db3 beta - all snapshots pop open in web ui and homekit just sent me a motion detection from the db so it seems back to normal so far, video seems fine too, mostly - the beta db seems to lag or buffer at times or fail to display when switching to video and I see a "get /favicon.ico http/1.1" 404 - or a "get /snapshot/gatecam.jpg?blahblah http/1.1" 307 - or a "timeed out connecting to gatecam (20s)" - so far its the only one so it could be that being a gen2 beta hardware and firmware are the problem - I think it was gen 4 that went retail - I have a couple of gen 3 that may be closer to retail but its time to start cleaning up and packing stuff to prep house for sale in order to relocate hopefully by march. At least for now the 3 important cams are working.

[mrlt8]

Are they all on the latest firmware? I've noticed some improvements in performance with my cameras on the latest firmware.

[cheme75]

Are they all on the latest firmware? I've noticed some improvements in performance with my cameras on the latest firmware.

That’s another problem with the beta db cams, old firmware. can’t update and the db lacks SD card so no option to force a hack or other fw. Things seem stable since I reinstalled the previous version of docker 4.12. Can’t be sure it’s the issue, but over 24 hrs looking ok. The db does display, it’s just slow. Will keep eye on log periodically to check for glitches.