October 18, 20232 yr ...are, unsurprisingly, causing a port conflict. So, when I create them (specifically, Readarr) I'm doing one at default 8787 and on at 18787. Should be fine. I'm routing them through an OpenVPN container, but I don't see that as the issue. Mostly because when I start my Readarr at 18787 I'm getting: Quote 2023-10-18 09:11:56,988 DEBG 'readarr' stdout output: [Fatal] ConsoleApp: Failed to bind to address http://[::]:8787: address already in use. This can happen if another instance of Readarr is already running another application is using the same port (default: 8787) or the user has insufficient permissions The only reference I can find to a port 8787 in the Docker setup for this container is this: So I edit that, to make it an 18787. But I still end up with the same complaint in the log: I've absolutely got another instance of Readarr running, but it shouldn't be on that same port. I've even gone so far as to remove the WebUI value and change it to 18787. Can anyone offer a suggestion as to how to get around this problem?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.