Can't connect to my Plex media server since 9/29/22

Server Version#: 4.92.0
Player Version#: not listed under Plex Web, Player, or General.
No server log attached.

I need help with the message, “The server “MediaCenter” is unreachable. Make sure it’s running, double check your network, and try again.” It keeps trying to connect but is unsuccessful.
My server & Plex are on the same desktop computer which is connected to the internet. I’ve checked for Plex updates for my Win 7, 64-bit desktop but there is not an update for my computer.
I’ve signed out and in several times.
I’ve read the support article, “Why can’t the Plex app find or connect to my Plex Media Server?” I do not have a VPN

I’ve solved this problem in the past but today I’m at a loss. Please help. Thanks!

The server can say that if it’s unclaimed. Because the server and player are on the same PC, what do you get when you type this?

http://127.0.0.1:32400/identity

If it says claimed=0, then you should be able to (re)claim it.
If it says claimed=1, then it is claimed.

The document to read these days if you have to do so: You need to reclaim your server, but don't dare to touch the Windows Registry

When I enter http://127.0.0.1:32400/identity or the address of my Plex server, Firefox states: “Unable to connect. Firefox can’t establish a connection to the server at …”
When I enter these addresses in Edge I get: “Can’t reach this page. 127.0.0.1 refused to connect.”
I am connected to the internet and can connect to email, etc.

Is plex running in the task bar? are you opening the 127 link on the same computer that has plex?

a thought…
pms x64 isn’t supported on win7 x64, in case you’re trying that.
pms x86, the 32bit version works afaik.

My Plex server is open in a Firefox tab. I’ve always had it open in a Firefox tab. I open another tab, next to my Plex server tab for 127.xxx.
I haven’t changed anything I’ve done in the past.

Those errors are telling you the same thing. It’s what you would see if Plex Media Server was not running because nothing would be listening on port 32400.

PMS spawns a web server to listen on that port. Although PMS might be running, the web server may have crashed.

@dbirch and I are therefore curious if you see PMS running in your taskbar. We ask if you can see it there because PMS has no GUI window whatsoever. That web page you say is always open is actually a Player. The server just sort of runs in the background as a service or a daemon if that makes sense. The server may have crashed but that web page wouldn’t close. It might say Server Unavailable or have yellow exclamation points if it crashed or the web server crashed.

Thanks for clarifying your Firefox and your PMS are on the same computer (and therefore can use 127.0.0.1). Let us know if you can see PMS running via a task bar icon (which you may have to unhide).

Whatever happens, we will eventually hope you can find server logs by copying them from the folder manually. Zip and attach them here.

Okay, using your command prompt, type:

netstat -a and paste the results here, that will allow us to see if anything is listening on port 32400.

I ran into this problem earlier because some how I accidentally enabled ivp6 support and it some how prevented plex from even trying to listen on ivp4.

So, to resolve this, I simply used the app.plex.tv to login to my account and it was able to get me back into my plex to see my settings and I was able to fix it from there.

I don’t know if that is what is happening to you but let’s see if anything is listening. Then as others have said, you’re going to want to post your logs.

Thank you everyone for your help and ideas. The next day, 9/30, everything was working well, as before - my desktop that has my Plex media server was connected and all my android devices were connected as before. I’m assuming the web server did crash which caused my Plex media server to not connect. So I don’t need to post any logs now.

Regarding Plex on the task bar: I clicked on the PlexMediaCenter.exe file and it tries to open up but nothing appears and Plex does not appear as an application in my Task Manager, but it (PlexMediaCenter.exe) does appear as a process in my
Task Manager. This is what I observed on 9/29 when I couldn’t connect to my Plex media server and on 9/30 when somehow it did connect to my Plex media server.

Regarding listening with netstat -a typed in the command prompt: On 9/30, it showed it was listening. I wish I had tried this on 9/29 to verify the assumption that it was not listening.

I’m just glad it’s fixed. Thank you all for your help and ideas which helped me feel that I’m not alone with my problem and I felt encouraged to keep trying. Much gratitude from me to all of you who posted. Thanks!

1 Like

There is no such file, unless you are using a software version which is 10 years old!

I installed Plex software on my desktop in March or Feb of this year. Plex Media Server.exe does appear in C:\Program Files (x86)\Plex\Plex Media Server

PlexMediaCenter.exe != Plex Media Server.exe

Try You need to reclaim your server, but don't dare to touch the Windows Registry

I’m having a very similar issue that started one or two upgrades ago I think. Plex installed on my Desktop PC. Win10 Pro Ver 21H2, 32gb, Ryzen7 5700G, Radeon RX6600.

After a couple of days my plex server stops responding and I have to reboot my computer to get it to work again. I’ve run through similar steps and I think the web service may be crashing not the server maybe? What are next steps to diagnose? I looked through the Plex Media Server.log and didn’t see anything that was a smoking gun, but I’m not that familiar with it. Happy to send the logs as a PM to someone that might understand them better? I’m at my wits end with this. As a temp setup, I my computer reboots every Monday AM at 2am, but It’s Thursday and I can’t reach my server again…

http://127.0.0.1:32400/identity
“Site can’t be reached” message on chrome

Taskbar RMC on Plex server open plex server →
loads a cached version of the web page, but getting the server unreachable message

Windows Task Manager details tab->
Plex Media Server.exe shows as running ~217,040k
Plex.exe shows as running

netstat -a was a new one for me. I’m guessing nothing it listening by these results? Is this an indication that the web server crashed?

Netstat -a results for port 34200->
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61295 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61296 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61333 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61334 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61359 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61360 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61439 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61440 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61452 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61453 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61473 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61474 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61484 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61485 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61487 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61488 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61517 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61518 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61542 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61543 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61572 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61573 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61595 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61596 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61617 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61618 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61640 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61641 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61666 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61667 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61707 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61708 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61730 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61731 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61751 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61752 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61772 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61773 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61792 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61793 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61809 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61810 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61868 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61869 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61889 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61890 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61933 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61934 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61946 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61947 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61963 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61964 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61976 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61977 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61981 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61982 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:61983 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62000 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62001 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62020 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62022 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62023 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62025 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62042 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62043 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62054 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62055 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62070 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62071 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62090 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62091 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62097 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62098 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62106 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62107 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62116 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62117 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62124 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62125 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62134 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62135 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62148 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62149 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62164 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62165 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62180 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62181 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62199 CLOSE_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:62200 CLOSE_WAIT

Just for Fun, I rebooted my computer and checked things again
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:58262 TIME_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:58263 TIME_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:58268 TIME_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:58280 TIME_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:58281 TIME_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:58286 TIME_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:58287 TIME_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:58301 TIME_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:58343 TIME_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:58344 TIME_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:58345 TIME_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:58347 TIME_WAIT
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:58552 FIN_WAIT_2
TCP 127.0.0.1:32400 DESKTOP-RPHKRFQ:58553 FIN_WAIT_2

/identify gets me this →
<MediaContainer size="0" claimed="1" machineIdentifier="3111871fbd8716b94e4043e4c763a8886afbc280" version="1.29.0.6244-819d3678c"> </MediaContainer>

Start a new topic for yourself with the above details.
This is marked solved and isn’t likely to be noticed.
You probably need to follow

Update. My problem came back & the following message appeared: "app.plex.tv is unable to connect to “Media Center” securely.
After gaining access to my “Media Center”, by claiming it using the software link provided in this thread, I went into my router and designated port forwarding for 32400.
I did this yesterday and I believe everything is working as usual.

Thanks nibbles. posted to a new topic → Server stops responding

I haven’t gone through the reclaim the server yet because it comes back as soon as I restart. Last time I tried something like that I managed to ‘fix’ it so well that I had to start from a clean install. So I’m hesitant to go deep into things unless I know for sure that is the issue.

I recently set up a docker instance with plex on my NAS. I’ve got a different tuner hooked up to to that one to see if I like it better. Sounds like that has been more stable for people than the windows server and I’d like to be able to actually turn off my PC eventually! Fingers crossed that it works because having to restart my computer every day is not high on my list of things to deal with.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.