I was using the part of the settings.cfg where I could just put an IP Adress for the Webserver, but its gone in the latest iteration. Is there any way to bring it back?
For now I just copied the settings.cfg, Webserver.py and it is working even though I get some errors, it still runs in the background. But I would really like the chance to define it as there are some other webservers running on my machine and I have a second interface IP which I would like plexconnect to use.
Any ideas?
Regards,
Jan
You need to give us A LOT more information. Pc/mac/linux? Versions of pms and plexconnect. I dont understand why you are mixing and matching files from different builds of plexconnect generally this is bad. What is your 1st and 2nd eth interface full ip address etc? Webserver ports? Etc etc etc the more the better…
As said, I have another running webserver on my machine which I need (amahi) on ubuntu server. Thats why I have set another interface for my network eth0 which is now eth0:1. My normal IP adress is 10.0.1.3 and my second is 10.0.1.6 for plexconnect only. I have no idea how to do it if not like this. Latest PMS Version and now latest plexconnect. Ive tried to mix those files in order to use the old webserver adress in the settings.cfg, but I just figured its not working anyway. I know its not a good idea anyway but I cant run latest plexconnect without it.
I hope this was clear enough :)
Regards,
Jan
So do you have multiple webservers running on just one eth device? Can you isolate your webserver to just that device? Why do you need to change your settings file to point at your webserver? If you are just pointing to your open eth device strictly for plexconnect I dont see the need to change the settings file at all. Is your webserver comming across port 80 on both devices, what ports are in use?
I was able to do so before. Even the FAQ still suggests it. Im using amahi on top of Ubuntu which is using apache2 on default webserver port 80. Thats why before I just changed the plexconnect webserver ip to my second interface ip.
I dont see the harm in adding the webserver option to the new settings.cfg, if it works then use it, just compare the two files and edit as needed.
I did. I changed the IP_self variable in Webserver.py and DNSServer.py but after that I cant get it to work anymore, sadly. If I was able to make it work there I would have changed the settings.cfg that I could easily edit it there, but as already said, I wasnt successful
Does plexconnect shutdown when you run it? What does your log file say?
No it doesn't. It even intercepts it. Gimme a sec Ill change it again and post it
20:55:01 PlexConnect: ***
20:55:01 PlexConnect: PlexConnect
20:55:01 PlexConnect: Press CTRL-C to shut down.
20:55:01 PlexConnect: ***
20:55:01 PlexConnect: started: 20:55:01
20:55:01 PlexConnect: IP_self: 10.0.1.3
20:55:01 DNSServer: started: 20:55:01
20:55:01 DNSServer: ***
20:55:01 DNSServer: DNSServer: Serving DNS on 10.0.1.6 port 53.
20:55:01 DNSServer: intercept: ['trailers.apple.com', 'atv.plexconnect'] => 10.0.1.6
20:55:01 DNSServer: restrain: ['mesu.apple.com', 'appldnld.apple.com', 'appldnld.apple.com.edgesuite.net'] => 127.0.0.1
20:55:01 DNSServer: forward other to higher level DNS: 8.8.8.8
20:55:01 DNSServer: ***
20:55:02 WebServer: started: 20:55:02
20:55:02 WebServer: ***
20:55:02 WebServer: WebServer: Serving HTTP on 10.0.1.3 port 80.
20:55:02 WebServer: ***
20:55:02 PlexGDM: ***
20:55:02 PlexGDM: looking up Plex Media Server
20:55:02 PlexGDM: ***
20:55:02 WebServer: started: 20:55:02
20:55:02 WebServer: ***
20:55:02 WebServer: WebServer: Serving HTTPS on 10.0.1.3 port 443.
20:55:02 WebServer: ***
20:55:03 PlexGDM: servers discovered: 1
20:55:03 XMLConverter: PlexGDM - PMS: 10.0.1.3:32400
20:55:07 DNSServer: DNS request received!
20:55:07 DNSServer: Source: ('10.0.1.14', 61034)
20:55:07 DNSServer: Domain: trailers.apple.com
20:55:07 DNSServer: ***intercept request
20:55:07 DNSServer: -> DNS response: 10.0.1.6
20:55:08 DNSServer: DNS request received!
20:55:08 DNSServer: Source: ('10.0.1.14', 65535)
20:55:08 DNSServer: Domain: trailers.apple.com
20:55:08 DNSServer: ***intercept request
20:55:08 DNSServer: -> DNS response: 10.0.1.6
So you see, it even intercepts it. I just still get the error that Trailers is unavailable.
your websever should be on 10.0.1.6 for 80 and 443 on plexconnect. Also you ipself is grabbing your 1st ethernet device. Your appletv is 10.0.1.14 obviously. 10.0.1.3 is you original eth device which is causing your conflict this is where you host your apache webserver i assume. Your atv dns should point to 10.0.1.6.
No, I have always used Webserver on 10.0.1.3 and DNS on 10.0.1.6, and I also dont know why this should be a problem as I have defined them both in seperate files, but Ill give it a try
Looks like pms setting should be changed to 10.0.1.6 as well which needs to be changed on pms itself.
No, why should it. As already said, its running on both interfaces and this doesnt change anything, actually its still the same interface so theres no need to change it. I can access my PMS at 10.0.1.3 and 10.0.1.6
Plexconnect uses port 80 and 443, dont you want that on 10.0.1.6? Dont you use apache on 10.0.1.3? I dont know your ports or your situation, you do. Something is up with your routes obviously otherwise it would work. When you run with your old files how does you log look? Maybe you can see what is holding you up in there. I dont think plexconnect is your issue, I think your issue is in your ports/ip addresses
Exactly, and thats why I use 2 interface IPs. I want it to use port 80&443 from 10.0.1.3 and DNS Port from 10.0.1.6.
And no, its not. I had it perfectly running before, I even have my old setup here, theres just the seekbar problem. Just the latest gives me this problem
If all the ports were correct you wouldnt be getting trailers unavailble i would think. I would look at the logs, you have a very unique situation, personally i would try to simplifly things to one interface for plexconnect, then use another for apache but thats me, maybe you can start to troubleshoot from there. It seems like you know enough to get it done it just gonna take some time to dig around and find what is missing or added between the versions that is messing you up. If you cant give me more info about your ports ips etc i really cannot help you any further sorry. Wish you luck.
Maybe swap your apache completely to 10.0.1.6?
If the ports were incorrect it wouldnt intercept it. The point is I dont know anymore what it could be, with the old settings it was far easier for me to be honest :) Theres no need for info about ports, as I use the default ports given by plexconnect. I just use a second network ip and thats all, and I basically just need to change the IP of the DNSServer, but when doing that its not working anymore
I have the newest pms and plexconnect, i didnt edit any plexconnect files. The only difference is I only use one ethernet for everything pms, plexconnect and apache on a different port then 80 of course. Everything works perfect. You have quite a setup there with multiple ethernets, I would hate to try to remember all that lol. Sounds like you are close to getting it though.
Well, the thing is I use bind9 DNS Server on my server (where also plexconnect is running on)
I also edited the DNSServer.py before and just changed a line where it says DNS.bind = blablabla to my second ip, meaning 10.0.1.6
this now does not work anymore as it doesnt let me access it anymore and I still dont know why, its not very complicated.
Ive also tried to add this to my current dns server bind9, but I cant get it to run though it yet
