# Plex server not available during initialization

**URL:** <https://forums.plex.tv/t/plex-server-not-available-during-initialization/846225>\
**Category:** Plex Media Server\
**Tags:** server-windows\
**Created:** [July 3, 2023, 4:05am UTC](https://forums.plex.tv/t/plex-server-not-available-during-initialization/846225 "2023-07-03T04:05:53Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![altv8](https://avatars.discourse-cdn.com/v4/letter/a/f6c823/32.png) [@altv8](https://forums.plex.tv/u/altv8)\
**Post date:** [July 3, 2023, 4:05am UTC](https://forums.plex.tv/t/plex-server-not-available-during-initialization/846225/1 "2023-07-03T04:05:53Z")

</div>

Server Version#:1.32  
Player Version#:  
\<If providing [server logs](https://support.plex.tv/articles/200250417-plex-media-server-log-files/) please do NOT turn on verbose logging, only [debug logging](https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/#toc-1) should be enabled\>  
[Plex error log.txt](https://forums.plex.tv/uploads/short-url/1xkoNhNdf2x9zk4V5e7Jv5t6G8r.txt) (33.2 KB)

---

<div class="post-metadata">

**Author:** ![dane22](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/dane22/32/4389_2.png) [@dane22](https://forums.plex.tv/u/dane22)\
**Post date:** [July 6, 2023, 10:34am UTC](https://forums.plex.tv/t/plex-server-not-available-during-initialization/846225/2 "2023-07-06T10:34:12Z")

</div>

Hello.

From the looks of it, the server fails to lookup information about it self

What happens, if you in a browser on the server itself browse to : `http://127.0.0.1:32400/identity` ?

Please post a screen capture of the output

---

<div class="post-metadata">

**Author:** ![altv8](https://avatars.discourse-cdn.com/v4/letter/a/f6c823/32.png) [@altv8](https://forums.plex.tv/u/altv8)\
**Post date:** [July 6, 2023, 3:50pm UTC](https://forums.plex.tv/t/plex-server-not-available-during-initialization/846225/3 "2023-07-06T15:50:28Z")

</div>

Here is the info:  
This XML file does not appear to have any style information associated with it. The document tree is shown below.

`<MediaContainer size="0" claimed="1" machineIdentifier="6dc0cbc766ad318a067c4■■■526fbee5703624a6" version="1.32.5.7210-77f7f99fa"> </MediaContainer>`

---

<div class="post-metadata">

**Author:** ![dane22](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/dane22/32/4389_2.png) [@dane22](https://forums.plex.tv/u/dane22)\
**Post date:** [July 6, 2023, 5:24pm UTC](https://forums.plex.tv/t/plex-server-not-available-during-initialization/846225/4 "2023-07-06T17:24:01Z")

</div>

Hmm…

Above shows that the server is up running, and claimed

What happens, if you browse to `http://127.0.0.1:32400/web` ?

---

<div class="post-metadata">

**Author:** ![altv8](https://avatars.discourse-cdn.com/v4/letter/a/f6c823/32.png) [@altv8](https://forums.plex.tv/u/altv8)\
**Post date:** [July 6, 2023, 7:01pm UTC](https://forums.plex.tv/t/plex-server-not-available-during-initialization/846225/5 "2023-07-06T19:01:31Z")

</div>

Here is what I get.  
[Problem loading page.txt](https://forums.plex.tv/uploads/short-url/ydiMhv68KXvzN8E9Sh5yeOOGieb.txt) (1.4 KB)

---

<div class="post-metadata">

**Author:** ![altv8](https://avatars.discourse-cdn.com/v4/letter/a/f6c823/32.png) [@altv8](https://forums.plex.tv/u/altv8)\
**Post date:** [July 6, 2023, 7:02pm UTC](https://forums.plex.tv/t/plex-server-not-available-during-initialization/846225/6 "2023-07-06T19:02:57Z")

</div>

Also just an FYI:  
I have a fixed IP Address .  
 ![Screenshot 2023-07-06 at 11-51-50 AX11000 MU-MIMO Tri-Band Gaming Router](https://global.discourse-cdn.com/plex/original/4X/a/d/e/ade282b1e762edbaf2a3f96843fc70b570d3a0ba.png)  
& this is what I did on my TP-Link router

---

<div class="post-metadata">

**Author:** ![DTR](https://avatars.discourse-cdn.com/v4/letter/d/9fc348/32.png) [@DTR](https://forums.plex.tv/u/DTR)\
**Post date:** [July 6, 2023, 7:09pm UTC](https://forums.plex.tv/t/plex-server-not-available-during-initialization/846225/7 "2023-07-06T19:09:37Z")

</div>

Only `172.16.0.0` to `172.31.255.255` are considered reserved for private network communications within `172.0.0.0/8`. `172.162.0.0/16` is a public block, so that might be confusing Plex (some reverse lookup services say that 172.162.1.60 is used by Microsoft’s Azure services).

---

<div class="post-metadata">

**Author:** ![altv8](https://avatars.discourse-cdn.com/v4/letter/a/f6c823/32.png) [@altv8](https://forums.plex.tv/u/altv8)\
**Post date:** [July 6, 2023, 8:18pm UTC](https://forums.plex.tv/t/plex-server-not-available-during-initialization/846225/8 "2023-07-06T20:18:48Z")

</div>

Please remember that this is an internal IP address and not an external.  
I have an entire network based on these with multiple fixed IP addresses within my organization (my house) including NAS, printers, etc.  
What you are talking about is outside my internal NAT. Correct?

---

<div class="post-metadata">

**Author:** ![DTR](https://avatars.discourse-cdn.com/v4/letter/d/9fc348/32.png) [@DTR](https://forums.plex.tv/u/DTR)\
**Post date:** [July 6, 2023, 8:36pm UTC](https://forums.plex.tv/t/plex-server-not-available-during-initialization/846225/9 "2023-07-06T20:36:16Z")

</div>

Yes, and the fact that it’s an internal IP might be why things are going wrong. Plex does quite a few things beyond what a printer or other devices will do on your local network, like automatically generating SSL certificates for both public and private IPs, and publishing those IPs so remote clients know how to connect to your server. It’s hard to say for certain without knowing anything about Plex’s code, but I wouldn’t be surprised if using a public IP range for internal communications is part of the problem.

---

<div class="post-metadata">

**Author:** ![altv8](https://avatars.discourse-cdn.com/v4/letter/a/f6c823/32.png) [@altv8](https://forums.plex.tv/u/altv8)\
**Post date:** [July 6, 2023, 8:47pm UTC](https://forums.plex.tv/t/plex-server-not-available-during-initialization/846225/10 "2023-07-06T20:47:52Z")

</div>

What about 162.162.1.1 thru 162.162.1.100.  
Would that be better?

---

<div class="post-metadata">

**Author:** ![DTR](https://avatars.discourse-cdn.com/v4/letter/d/9fc348/32.png) [@DTR](https://forums.plex.tv/u/DTR)\
**Post date:** [July 6, 2023, 9:03pm UTC](https://forums.plex.tv/t/plex-server-not-available-during-initialization/846225/11 "2023-07-06T21:03:56Z")

</div>

`10.0.0.0/8` (`10.0.0.0-10.255.255.255`), `172.16.0.0/12` (`172.16.0.0-172.31.255.255`), and `192.168.0.0/16` (`192.168.0.0-192.168.255.255`) are the only ranges officially recognized as reserved for private local communication: [Reserved IP addresses - Wikipedia](https://en.wikipedia.org/wiki/Reserved_IP_addresses)

---

<div class="post-metadata">

**Author:** ![dane22](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/dane22/32/4389_2.png) [@dane22](https://forums.plex.tv/u/dane22)\
**Post date:** [July 7, 2023, 12:37pm UTC](https://forums.plex.tv/t/plex-server-not-available-during-initialization/846225/12 "2023-07-07T12:37:57Z")

</div>

With our new claiming method private address space is no longer required  
See: [New Claiming Requirement for Windows](https://forums.plex.tv/t/new-claiming-requirement-for-windows/839096)

Also, when @altv8 browsed to the `/identity` endpoint, it showed that the server was indeed claimed already

Since this is a new install, I recommend @altv8 uninstall, restart the server and then install again  
After installing, select `Open Plex` from the system tray, as mentioned in the new claiming post I linked towards

And lastly, @DTR is correct in recommending you to use private address space due to security

---

<div class="post-metadata">

**Author:** ![glhermans](https://avatars.discourse-cdn.com/v4/letter/g/bc8723/32.png) [@glhermans](https://forums.plex.tv/u/glhermans)\
**Post date:** [July 16, 2023, 10:55am UTC](https://forums.plex.tv/t/plex-server-not-available-during-initialization/846225/13 "2023-07-16T10:55:46Z")

</div>

I have the same issue,

i did a clean install from my pc (windows 11)  
installed plex but can not complete the setup

When i check the link [http://127.0.0.1:32400/identity](http://127.0.0.1:32400/identity) i receive the following

```xml
<MediaContainer size="0" claimed="1" machineIdentifier="removed-before-posting" version="1.32.4.7195-7c8f9d3b6"> </MediaContainer>

```

when i go to [http://127.0.0.1:32400/web](http://127.0.0.1:32400/web) i get the following message

 ![image](https://global.discourse-cdn.com/plex/original/4X/8/4/a/84ae25bd14a91cbeec8985ad88557d8c0c98d1a3.jpeg)

But then i finally resolved it by using this.

```auto
Windows Registry Editor Version 5.00

[-HKEY_CURRENT_USER\SOFTWARE\Plex, Inc.\Plex Media Server\PlexOnlineHome]
[-HKEY_CURRENT_USER\SOFTWARE\Plex, Inc.\Plex Media Server\PlexOnlineMail]
[-HKEY_CURRENT_USER\SOFTWARE\Plex, Inc.\Plex Media Server\PlexOnlineUsername]
[-HKEY_CURRENT_USER\SOFTWARE\Plex, Inc.\Plex Media Server\PlexOnlineToken]
[-HKEY_CURRENT_USER\SOFTWARE\Plex, Inc.\Plex Media Server\PreferredNetworkInterface]

[HKEY_CURRENT_USER\SOFTWARE\Plex, Inc.\Plex Media Server]
"PublishServerOnPlexOnlineKey"=dword:00000001
"ManualPortMappingMode"=dword:00000000
"LogVerbose"=dword:00000000
"secureConnections"=dword:00000001

```

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\
**Post date:** [October 14, 2023, 10:56am UTC](https://forums.plex.tv/t/plex-server-not-available-during-initialization/846225/14 "2023-10-14T10:56:16Z")

</div>

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