Skip to content
Discussion options

You must be logged in to vote

This is caused by having the port in use by something else. ...or by trying to run two versions of Motion at the same time on the same port.

Reboot and try again. Double check that Motion is not running two instances via "top" application, and/or disable Motion being started as a service via systemctl disable motion

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@phasianus
Comment options

Answer selected by phasianus
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
2 participants
Converted from issue

This discussion was converted from issue #1668 on April 30, 2023 17:41.