Troobleshooting with My Plex Server- Connexion plex.tv refused

Plex Media Server
1

Hi ,

I can’t acces to my librairy.
I have the message “Not Authorized” You do not have access to this server.

this is the Plex Media Server.log :

Jan 06, 2023 19:58:40.158 [0x7f734e5f0b38] INFO - Plex Media Server v1.27.2.5929-a806c5905 - Debian GNU/Linux PC x86_64 - build: linux-x86_64 debian - GMT 01:00
Jan 06, 2023 19:58:40.158 [0x7f734e5f0b38] INFO - Linux version: 8 (jessie), language: en-US
Jan 06, 2023 19:58:40.158 [0x7f734e5f0b38] INFO - Processor: 8-core Intel(R) Xeon(R) CPU W3520 @ 2.67GHz
Jan 06, 2023 19:58:40.158 [0x7f734e5f0b38] INFO - Compiler is - Clang 11.0.1 (https://plex.tv 9b997da8e5b47bdb4a9425b3a3b290be393b4b1f)
Jan 06, 2023 19:58:40.158 [0x7f734e5f0b38] INFO - /usr/lib/plexmediaserver/Plex Media Server
Jan 06, 2023 19:58:40.112 [0x7f7351dd60d0] INFO - Running migrations. (EPG 0)
Jan 06, 2023 19:58:40.130 [0x7f7351dd60d0] INFO - Running migrations. (EPG 0)
Jan 06, 2023 19:58:40.150 [0x7f7351dd60d0] INFO - [CERT/OCSP] Successfully retrieved response from cache.
Jan 06, 2023 19:58:40.176 [0x7f734c994b38] WARN - [HttpClient/HCl#1] HTTP error requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx (7, Couldn’t connect to server) (Failed to connect$Jan 06, 2023 19:58:40.176 [0x7f734c9d9b38] ERROR - [MediaProviderManager] Error parsing content.
Jan 06, 2023 19:58:40.176 [0x7f734c9d9b38] ERROR - [MediaProviderManager] Error parsing XML: Error parsing file.
Jan 06, 2023 19:58:40.178 [0x7f734c994b38] WARN - [HttpClient/HCl#2] HTTP error requesting GET https://plex.tv/api/v2/server/access_tokens?auth_token=xxxxxxxxxxxxxxxxxxxx (7, Couldn’t connect to server) (Failed $Jan 06, 2023 19:58:40.178 [0x7f734c994b38] WARN - [HttpClient/HCl#3] HTTP error requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx (7, Couldn’t connect to server) (Failed to connect$Jan 06, 2023 19:58:40.179 [0x7f734c9d9b38] ERROR - [MediaProviderManager] Error parsing content.
Jan 06, 2023 19:58:40.179 [0x7f734c9d9b38] ERROR - [MediaProviderManager] Error parsing XML: Error parsing file.
Jan 06, 2023 19:58:40.180 [0x7f734c994b38] WARN - [HttpClient/HCl#4] HTTP error requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx (7, Couldn’t connect to server) (Failed to connect$Jan 06, 2023 19:58:40.180 [0x7f734c9d9b38] ERROR - [MediaProviderManager] Error parsing content.
Jan 06, 2023 19:58:40.180 [0x7f734c9d9b38] ERROR - [MediaProviderManager] Error parsing XML: Error parsing file.
Jan 06, 2023 19:58:40.181 [0x7f734c994b38] WARN - [HttpClient/HCl#5] HTTP error requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx (7, Couldn’t connect to server) (Failed to connect$Jan 06, 2023 19:58:40.181 [0x7f734c9d9b38] ERROR - [MediaProviderManager] Error parsing content.

CURL command in my linux server :
curl -v https://plex.tv

  • Rebuilt URL to: https://plex.tv/
  • Hostname was NOT found in DNS cache
  • Trying 52.48.60.59…
  • connect to 52.48.60.59 port 443 failed: Connexion refusée
  • Trying 52.49.138.125…
  • connect to 52.49.138.125 port 443 failed: Connexion refusée
  • Trying 34.243.47.112…
  • connect to 34.243.47.112 port 443 failed: Connexion refusée
  • Trying 52.19.183.102…
  • connect to 52.19.183.102 port 443 failed: Connexion refusée
  • Failed to connect to plex.tv port 443: Connexion refusée
  • Closing connection 0
    curl: (7) Failed to connect to plex.tv port 443: Connexion refusée

Please help me !

3

May I have the full tar.gz or ZIP of the Logs directory.

This can’t be diagnosed from a snippet captured after all the critical init.

4

ALSO.

  1. You show Linux in this log fragment

  2. Plex.tv has a deleted Windows server (JAN 4)

PLATFORM WINDOWS 
PLATFORM VERSION 10.0 (BUILD 19045) 
VENDOR MICROSOFT 
DEVICE PC 
MODEL X64-X64 
DELETED WED, 04 JAN 2023 22:17:01 +0000 
LIBRARIES 0

Which server should be there?

5

I don’t know what this windows server is!

I swear that my server is a Linux debian. Do you have the windows server ip address?

6

@mir0of

Check your PM. I sent you info. All is good now.

I do need your server logs.

  1. Stop Plex
  2. Start Plex
  3. Wait 3 minutes
  4. Stop it again
  5. Make a tar.gz or ZIP of the Logs directory
  6. Attach here please
7

log.zip (581.4 KB)
Ok Sir ChuckPa

8

You turned off DEBUG – I can’t see what’s happning.

Please leave DEBUG logging on? It saves a lot of time for both of us at no extra cost.

Seeing 443 errors, with no debug, i can’t even guess why

This looks like you MIGHT have your own certificate on the host getting in the way of PMS - Plex.tv communication. Yes?

Jan 06, 2023 22:39:22.547 [0x7f2447e1ab38] ERROR - PublicAddressManager: Unable to get public IP adddress from myPlex (httpCode=-7): 
Jan 06, 2023 22:39:22.547 [0x7f2447f50b38] WARN - [HttpClient/HCl#28] HTTP error requesting GET https://plex.tv/api/v2/user/privacy?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx (7, Couldn't connect to server) (Failed to connect to plex.tv port 443: Connection refused)
9

Sorry, i turn debug enabled and zip New log
logdebug.zip (581.8 KB)

what certificate are you talking about? SSL letsencrypt for HTTPS?

10

Yes, Does this host have its own certificate installed for HTTPS?

If not, let me know.

We’ll do a hard reset of your server certificate

Also, is the server time sync’d to NNTP ? HTTPS fails if the clocks are too far out of sync.

11

Yes i have a letsencrypt certificate generate with DNS challenge. I use the certificate for my custom plex url.

My synchro ntp is OK.

12

I have reset your certificate.

In /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Cache

you’ll see cert-v2.p12.

Remove it.

Restart PMS.

ALSO,

I need ask you, what is the 91.x.x.x LAN address you have ?

I see 91.x.x.x and 192.168.x.x.

Is this a hosted server ?

13

I remove cert et restart PMS, but not solved problem :frowning:

Server has 2 network interfaces : LAN (192.168.x.y) and WAN with my public adress (91.x.y.z)

Yes is a hosted server

The file cert-v2.p12 is still missing After i restart PMS.

14

Now we have the root problem. PMS can’t update its certificate / get out to the internet corectly

I will send you a PM. We can continue there in private and discuss the server details.

1 Like
15

My published IP 55.xx in PMS is wrong. Maybe it’s the issue ?

16

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