PlexConnect - error import plexGDM....line 120

Hi folks,

 

trying to run the first time PlexConnect.py.

Environment: WHS 2011, fully patched

Python 3.3.3

 

Running CMD: python.exe PlexConnect.py

Result: (see Screenshot)

....

import plexGDM

File ".....PlexGDM.py", line 120

Print ''IP:'', getIP_PMS()

SyntaxError: invalid syntax

 

Do you need additional informaton to help me concerning this issue?

 

Any suggestions?

 

Thx a lot in advance.

Alex

PlexConnect is Python 2.x only. Best bet is 2.7.5.

2.5 gives limited performance (if at all...), 2.6 should work - but you never know. Development/Testing is mostly done on 2.7.5.

Python 3.x is not quite backward compatible. It would need some work.

ok. next error message. hmmm. Remotaccess for WHS2011 is active. tried to deactivate. same result.
Any ideas?

See the wiki troubleshooting section about ports in use.

Plus make sure to generate a certificate... install it into aTV as well as PlexConnect. See wiki installation guides.

like a drama :-((

ok step by step:

I'm trying to use PMS on my WHS2011 together with the already working WebServer. I followed exactly this tutorial to run PlexConnect with the IIS:

https://forums.plexapp.com/index.php/topic/70321-running-with-local-dns-server-and-iis/

I installed everything mentioned in the thread and did everything as mentioned.

Running PlexConnect.py still tells me the socket error for port 80. Is it possible to keep the IIS alive when I configure the rewirteURL etc?

Then I tried to create the certificate. While installing OpenSSL light it tells me that the Visual C++ 2008 Restistributables are missing. Ok installed them, though the 2010 redists are still installed. Started the server again. Message still comes up. Ignored it.

Now I try to generate the certificate. Got an error message concerning the openssl.cnf (is missing).

Any ideas?

thx

Alex

>>Message still comes up. Ignored it.

Ignoring might not be the correct method for errors...

I know that ignoring warning may result in problems. But the redists are really installed. Do you think the error message concerning the missing openssl.cfn has something to do with that?

any other suggestions?

I have no idea...

What happens when you "cd" into the openssl directory and start it from there?

first rule: ask google. ;-)

http://jaspreetchahal.org/warning-cant-open-config-file-usrlocalsslopenssl-cnf/

Certificate is fine now.

Still the port 80 issue. Can someone answer my question if it is possible to run my existing IIS with the rewrite method or do I absolutly have to cancel the IIS?

In another thread there was mentioned "net stop http". Tried this also, but after shutting down all services I got the message, that http can't be stopped. hmmmm. Port 80 issue still alive.

>>http://jaspreetchaha...sslopenssl-cnf/

Isn't setting a path the same as starting the executable within that directory?

>>port 80

Easiest thing would be to re-map your IIS to another port, thus freeing up #80.

Drawback: When you want to access your server, you have to add that port number.

I am no expert on IIS (or any other web server for that matter)... but I think bwynants and others did set up a redirect for Apache on Synology. Check out their thread, you might find something useful there.

maybe that has nothing to do with the IIS.

I have in netstat two entries which make me a little bit nervous.

  TCP    myServer:80       PCofMyDaughter:58390   LISTENNING
  TCP    myServer.2:445       PCofMyDaughter:58391   ESTABLISHED
(no owner information available)
 
what can this mean? On the PC of my daughter I can't anything suspicious. 
How can I get additional information to that?
 
After deactivation and reactivating the WLAN on the PC of my daughter there is the following entry in the netstat log (port has changed)
 TCP    myServer:80       PCofMyDaughter:58436   LISTENNING

some sort of internet sharing active?

Strike. Get it now. Yipppiieeee  :)  :)  :)

Check it out here: https://forums.plexapp.com/index.php/topic/88912-error-10013/

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