Mumble-Server: The bound address is already in use???????

[alankasprzyk23]

Description

I am trying to host a Mumble server for my friends outside of my LAN and i am trying to use Mumble-Server but it says that my local ip is already in use? Like how? Here is the log btw:

Steps to reproduce

1. Opened Mumble-Server.exe (.ini file is already created)

Mumble version

1.14.287

Mumble component

Server

OS

Windows

Reproducible?

Yes

Additional information

No response

Relevant log output

<X>2023-03-28 18:57:48.342 SSL: OpenSSL version is 'OpenSSL 1.1.1k  25 Mar 2021'
<W>2023-03-28 18:57:48.343 Initializing settings from C:/Users/AlanK/AppData/Roaming/Mumble/murmur.ini (basepath C:/Users/AlanK/AppData/Roaming/Mumble)
<W>2023-03-28 18:57:48.343 Binding to address 192.168.1.20
<W>2023-03-28 18:57:48.522 MetaParams: TLS cipher preference is "TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:AES256-SHA:AES128-SHA"
<W>2023-03-28 18:57:48.529 SSL: CA certificate filter applied. Filtered size: 136, original size: 136
<W>2023-03-28 18:57:48.533 ServerDB: Opened SQLite database C:/Users/AlanK/AppData/Roaming/Mumble/murmur.sqlite
<W>2023-03-28 18:57:48.533 ServerDB: Using SQLite's default rollback journal.
<W>2023-03-28 18:57:48.534 Murmur 1.4.287 running on Windows: Windows 10 Pro 2009 19045.2728 [x64]: Booting servers
<W>2023-03-28 18:57:48.548 1 => Server: TCP Listen on 192.168.1.20:41342 failed: The bound address is already in use
<W>2023-03-28 18:57:48.552 1 => Stopped

Screenshots

No response

[davidebeatrici]

Is the port 41342 already used by something else?

[Hartmnt]

Have you, by any chance, started the murmur server multiple times? (If you are not sure, you could check with TaskManager for example)

[github-actions[bot]]

As there has been no activity on this issue for a couple of days, we assume that your issue has been fixed in the meantime. Should this not be the case, please let us know.

If no further activity happens, this issue will be closed within 3 days.