Customizing ports #812
-
I'm having trouble viewing the web UI, and I think since I refreshed my image, it may be having trouble with other ports as well. The default web UI uses port 5000, but this is the same port that's used by Blue Iris's code project AI. I can try changing that port, but I know I had it working before on port 5001 using the following docker-compose.yml text (password / username redacted obviously) version: '2.4' I recently had to purge my containers and images and I re-installed my wyze cam under a new name, and docker appears to show the bridge working, but it looks like it's trying to use the default port 5000 as well, and I don't understand why. Below is the output in my docker desktop log. 🚀 STARTING DOCKER-WYZE-BRIDGE v2.1.7 [WyzeBridge] 🔍 Could not find local cache for 'auth'
Edit: I have tried using the info from https://github.com/mrlt8/docker-wyze-bridge/wiki/WebUI#custom-ports but it hasn't made any difference, even after deleting my container and re-building. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
You should be able to ignore that in the log messages as that's the internal port that it's listening on. You'll need to update your yaml to point to the internal port: - 5001:5000 # WEB-UI Note that the second port is 5000 as that's the port on the container which is listening on port 5000. |
Beta Was this translation helpful? Give feedback.
-
this change ( ▶ lsof -i:5000
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
ControlCe 434 dev 11u IPv4 0xc147a515a95518 0t0 TCP *:commplex-main (LISTEN)
ControlCe 434 dev 12u IPv6 0xe8e1cac731dcf025 0t0 TCP *:commplex-main (LISTEN) |
Beta Was this translation helpful? Give feedback.
You should be able to ignore that in the log messages as that's the internal port that it's listening on.
You'll need to update your yaml to point to the internal port:
Note that the second port is 5000 as that's the port on the container which is listening on port 5000.