PlexAPI - Target service not allowed

Dev Community Apps & Creations
1

Hi,

I tried to use the newest version of PlexConnect but get an error.

 

When I start the trailer app on ATV3, I get the message "No Plex Library Sections Available".

The logfile looks like this:

23:12:48 PlexConnect: ***
23:12:48 PlexConnect: PlexConnect
23:12:48 PlexConnect: Press CTRL-C to shut down.
23:12:48 PlexConnect: ***
23:12:48 PlexConnect: started: 23:12:48
23:12:48 PlexConnect: IP_self: 192.168.0.3
23:12:48 DNSServer: started: 23:12:48
23:12:48 DNSServer: ***
23:12:48 DNSServer: DNSServer: Serving DNS on 192.168.0.3 port 53.
23:12:48 DNSServer: intercept: ['trailers.apple.com', 'atv.plexconnect'] => 192.168.0.3
23:12:48 DNSServer: restrain: ['mesu.apple.com', 'appldnld.apple.com', 'appldnld.apple.com.edgesuite.net'] => 127.0.0.1
23:12:48 DNSServer: forward other to higher level DNS: 8.8.8.8
23:12:48 DNSServer: ***
23:12:48 WebServer: started: 23:12:48
23:12:48 WebServer: ***
23:12:48 WebServer: WebServer: Serving HTTP on 192.168.0.3 port 80.
23:12:48 WebServer: ***
23:12:48 WebServer: started: 23:12:48
23:12:48 WebServer: ***
23:12:48 WebServer: WebServer: Serving HTTPS on 192.168.0.3 port 443.
23:12:48 WebServer: ***
23:12:52 DNSServer: DNS request received!
23:12:52 DNSServer: Source: ('192.168.0.130', 64299)
23:12:52 DNSServer: Domain: trailers.apple.com
23:12:52 DNSServer: ***intercept request
23:12:52 DNSServer: -> DNS response: 192.168.0.3
23:12:52 WebServer: serving  C:\Users\User\Desktop\PlexConnect-master\PlexConnect-master\assets\js\application.js
23:12:52 DNSServer: DNS request received!
23:12:52 DNSServer: Source: ('192.168.0.130', 52173)
23:12:52 DNSServer: Domain: atv.plexconnect
23:12:52 DNSServer: ***intercept request
23:12:52 DNSServer: -> DNS response: 192.168.0.3
23:12:52 WebServer: serving .xml: /
23:12:52 PlexAPI: ***
23:12:52 PlexAPI: looking up Plex Media Server
23:12:52 PlexAPI: ***
23:12:53 PlexAPI: GDM: Servers discovered: 1
23:12:53 PlexAPI: Servers (local+MyPlex): 1
23:12:53 WebServer: serving .xml: /PlexConnect.xml
23:12:53 WebServer: serving  C:\Users\User\Desktop\PlexConnect-master\PlexConnect-master\assets\js\utils.js
23:12:53 WebServer: serving .xml: /library/sections
23:12:53 PlexAPI: No Response from Plex Media Server
23:12:53 PlexAPI: We failed to reach a server. Reason: Target service not allowed
23:12:53 WebServer: serving  C:\Users\User\Desktop\PlexConnect-master\PlexConnect-master\assets\js\utils.js

The last version of PlexConnect from end of september works fine, but with the newest version it stopped working.

Can you give me a hint on what the problem might be?

Thanks in advance.

2

Are you running a PMS and have you added any sections and media to it?

3

Yes, I'm running PMS on the same machine. When I close PlexConnect and start the old version (0.2 i think) it is working. But I want to use the newest version of PlexConnect.

4

did you add the certs to the new version?

5

Yes I copied it over from the old version.

6

Probably the fastest way to get it work would be to rename your plexconnect to something else. Redownload the latest version of plexconnect. Run plexconnect.py one time to generate a default settings, quit plexconnect and start it again. Dont edit anything or change any settings on any of the files whatsoever. Put the trailers.pem where it needs to be and point your atv dns to your device running plexconnect and post results. I assume you have already loaded trailers.pem on to your atv. Use these links to troubleshoot as well. If that doesnt work remove pms completely & reinstall pms, add library’s etc.

https://github.com/iBaa/PlexConnect

https://github.com/iBaa/PlexConnect/wiki

7

Thanks for your answers, I finally found the problem. I'm using a proxy server for surfing the internet and configured it in Internet Explorer. When I disable the proxy, everything is working fine but as soon I activate it again, I got the error "Target service not allowed". When I exclude the own ip of my pms (192.168.0.3 in that case) in proxy settings, it's working.

Can you tell me how PlexConnect is related to the proxy settings of IE? I don't get the causality on that.

8

Good question...

Check the log for IP_self in either case. Maybe the lookup algorithm gets screwed somehow?

9

It probably screws with traffic on port 80/443 - that is the detailed technical explanation ;)

10

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