No Server Access

[Fallenfederation]

Server Version#:1.15.3.858-fbfb913f7
Windows 10

I ended up having a router that failed on me. I replaced the router but my plex server just wont work right.

It tells me that the server need to be claimed, I go to claim it.

then this will happen

I cleared the registry entries, reinstalled/repaired server, logged out and back in, removed the server from authorized devices list, restarted pc, nothing seems to work. Am I missing something? Anyone have any suggestions.

[OttoKerner]

Use app.plex.tv and try again.

[Fallenfederation]

This is what I got under that link

[OttoKerner]

Please disable AdBlock and other web browser extensions. Use the incognito mode of the browser and try again.

[Fallenfederation]

Same result also cleared temporary internet files and history and tried Microsoft edge.

[OttoKerner]

There is no server signed into your account.
Which can mean 2 things:

• the server is already signed into a different Plex account
• the previous ‘claim’ attempt went wrong and the server is in a half-signed-in state

Try this procedure first https://support.plex.tv/articles/204281528-why-am-i-locked-out-of-server-settings-and-how-do-i-get-in/

If this fails as well, perform the steps 1 – 4 again, but then use this script to claim the server: https://github.com/ukdtom/ClaimIt

[remo427]

I think it’s your port forwarding on your router. Be sure to open port forwarding for both TPC and UTP. I just had this problem. It looked like the ports were open, but UTP was not. And this seems to be a change in the new version of Plex… it needs UTP 32400 open.

[Fallenfederation]

As far as I can see the ports are forwarded

[Fallenfederation]

I did both options neither helped.

[Fallenfederation]

is there a setting or file somewhere that is associating it to the old ip address?

[remo427]

Sorry my suggestion didn’t help. I used this sites tool to ensure the port forwarding was working:
https://www.yougetsignal.com/tools/open-ports/

It must have been a long day yesterday… I meant TCP and UDP in the message.

Good luck!

[remo427]

I also used this page for troubleshooting:
https://support.plex.tv/articles/200931138-troubleshooting-remote-access/

[OttoKerner]

1. activate debug logging (not ‘verbose’!)
2. quit Plex Server
3. wait 1 minute
4. perform https://support.plex.tv/articles/204281528-why-am-i-locked-out-of-server-settings-and-how-do-i-get-in/
5. wait 2 minutes
6. fetch log files manually and attach them here

[Fallenfederation]

Thanks everyone for the help and even if something you suggest did not help its still appreciated

Plex Media Server Logs_2019-04-06_11-28-47.zip (3.0 MB)

[Fallenfederation]

I kinda looked in the logs but I seen noting that pops out at me any ideas?

[sa2000]

I have gone through the logs and it may be to do with secure connections.

We have errors like this logged

Apr 05, 2019 21:01:40.857 [6164] DEBUG - CERT: incomplete TLS handshake: sslv3 alert certificate unknown

which continued into

Apr 06, 2019 11:28:33.946 [5784] DEBUG - CERT: incomplete TLS handshake: sslv3 alert certificate unknown

There were errors registering the server with plex.tv

Apr 05, 2019 21:02:45.545 [7784] DEBUG - HTTP requesting PUT https://plex.tv/devices/0c7c57f3a35905ee19ba157955bdc0d3a5c7fec9?Connection[][uri]=http://192.168.1.8:32400&httpsEnabled=1&httpsRequired=0&dnsRebindingProtection=0&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Apr 05, 2019 21:02:46.203 [7784] DEBUG - HTTP 400 response from PUT https://plex.tv/devices/0c7c57f3a35905ee19ba157955bdc0d3a5c7fec9?Connection[][uri]=http://192.168.1.8:32400&httpsEnabled=1&httpsRequired=0&dnsRebindingProtection=0&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx

Whilst trying the claim sequence on of my servers, i did actually get the No soup for you whilst claiming the server but it was only transient

I would like to see the plex web verbose log for when the No soup error is displayed and also a copy of the registry export (sent by private message)

As a side note for now - your screenshots for port forwards in the router shows you have created port forwards for the list of ports we mention as needing to be allowed in the firewall. They are not supposed to be port forwards - so delete all apart from the 32400 public to 32400 local for 192.168.1.8

This is what we say on the support article
https://support.plex.tv/articles/201543147-what-network-ports-do-i-need-to-allow-through-my-firewall/
You do not forward these ports !

With regards to how we get the web verbose log for no soup
Go to settings / web / show advanced / debug
change log level from default of disabled to verbose
save changes

Then when you get the No soup on the claim and when it is pernanent no soup (in my case it was transient) , take screenshot, and go to settings / web / show advanced / debug / view logs and select all and copy to text file
Then get server logs

and for the registry
Export this to txt file
HKEY_CURRENT_USER\Software\Plex, Inc.\Plex Media Server
and send to me by private message and provide the server and web logs and screenshot