Error: Unable to set up server: bind: Address already in use

General Discussions
1

This question has been asked before and I’ve read the answers on the forums and tried their solutions, but I still get this error in my log and cant access plex. Even when I’m on my server and type in 127.0.0.1:32400/web/

Not sure what else todo.

2

That error occurs when another program is running and using the port already.

Since 32400 is only known to conflict on NAS’s, finding a conflict here is unusual.

In Linux: sudo fuser 32400/tcp and then ps -ef | grep _number_returned_from_fuser

If you’re using Windows, this should do the trick http://stackoverflow.com/questions/48198/how-can-you-find-out-which-process-is-listening-on-a-port-on-windows

3

vrd9yhzlva9g.png773×51 5.03 KB

Ran those commands and here are the results. Not sure exactly what this means. Please help

4

When you type in the

“sudo fuser 32400/tcp”

it returns a number value. then the next line you type would be:

“ps -ef | grep value_returned_from_Fuser_command_just_executed”

In my case I entered sudo fuser 32400/tcp and the value returned was 20074. So my next typed line reads “ps -ef | grep 20074”. This returned:

20074 root 206:49 ./Plex Media Server

Which is exactly what I expected it to return, as 32400 is used by Plex on my Linux based NAS. Your numeric value is likely different so don’t use mine, use the one returned by the fuser command on your machine…

5

Hey plexer2015,
do a *ps -ef | grep 7849 **
as 4749 was the number returned as PID
Another command to get the application is this one which also returnd pid
netstat -tulpn | grep 32400
Like this
tcp 0 0 0.0.0.0:32400 0.0.0.0: LISTEN 2510/Plex Media Ser

that command should show you which application is running on that port, what you have is a PID. which can be used to kill.

When we know which application it is, we can see if that can be rerouted to another port.

6

If you want to be all swoopy about it:

some text to make the forum happy

#
ps -ef | grep `sudo fuser 32400/tcp | awk -F':' '{print $1}'`
#

and some more

Produces:

[chuck@lizum ~/Digest.160]$ ps -ef | grep `sudo fuser 32400/tcp | awk -F':' '{print $1}'`
32400/tcp:          
plex     13833     1  0 Nov20 ?        00:04:14 /usr/lib/plexmediaserver/Plex Media Server
plex     13853 13833  0 Nov20 ?        00:02:17 Plex Plug-in [com.plexapp.system] /usr/lib/plexmediaserver/Resources/Plug-ins-3355680/Framework.bundle/Contents/Resources/Versions/2/Python/bootstrap.py --server-version 1.3.0.3004-3355680 /usr/lib/plexmediaserver/Resources/Plug-ins-3355680/System.bundle
plex     13920 13833  0 Nov20 ?        00:00:28 Plex Plug-in [com.plexapp.plugins.WebTools] /usr/lib/plexmediaserver/Resources/Plug-ins-3355680/Framework.bundle/Contents/Resources/Versions/2/Python/bootstrap.py --server-version 1.3.0.3004-3355680 /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Plug-ins/WebTools.bundle
[chuck@lizum ~/Digest.161]$
7

i did everything and nothing was displayed :frowning:

as far as I can tell 32400 port isn’t used by any program.

8

before you did that, did netstat -an | grep 32400 show any output ?

9

fuser -k 32400/tcp

should kill anything running on plex port @ChuckPa I can see plex using other ports shuch as 32401, can that also be the casue of this?

10

fuser only reports what it finds. it doesn’t kill anything.

grab your log files and your console output. put the console output in a text file and attach here with the PMS zip of your log files (settings - server - help)