I sent you a pm.
so I have to put 192.168.0.4 in place of 192.168.178.10?
this was not explained in the guide btw, I have read the guide over and over. still doesn't work either.
It was not explained in the guide because you would not have turned off the advanced setting for auto discovery if you followed the guide. The advanced settings in settings.cfg are explained on the wiki but should not be tampered with unless you know what you are doing ;)
oh and btw plex star, I have never heard anybody refer to local ip addresses as subnets. So of course that is going to cause confusion.
Um that is not my name but title (related to number of posts). I didn't refer to IP addresses as subnets but i could see that the IP addresses were on different subnets (subnet masks and subnets are also different but related things).
It might be best to stop PlexConnect, delete settings.cfg and restart PlexConnect so that it uses the generic settings; this is what the guide tells you to use to avoid problems ;)
I turned off the advanced setting for auto discovery because it was not working and people on these forums have told me in the past that gdm can cause problems sometimes with plex connect.
I have already tried using plexconnect with default settings and it did not work, that is why I ended up tinkering with the settings in the first place.
Funnily enough, I have tried plexconnect in windows bootcamp (on the same mac system) with default settings and it works no problem after disabling iis service. But for some reason it is just not working on mac. This must mean my router settings are fine and all the ports are forwarded correctly. What this leaves me with is that it must be a software related problem.
I have been troubleshooting the problem with wahlman.j and we both believe that the problem is something is blocking port 80 since when I type http://192.168.0.3 in url it does not give me error response and instead just fails to connect (my ip has changed now since I have not done dhcp reservations yet). However when I type http://192.168.0.3:3400/ it does load plex media server. This is what led us to believe port 80 is the problem. I have tried netstat and another terminal command which I cannot really remember and it turned out apache 2 was using port 80 so wahlman.j had me edit httpd file to use port 1234 and reboot. Now it appears nothing is using port 80 after using the terminal command to check for ports again, but still plexconnect is not working. I strongly suspect that there is a background service running which is blocking port 80, perhaps related to icloud or something of that nature.
By any chance do you have an idea of any background services/features in mac which could be conflicting with plexconnect?
If not I guess I will just cycle through all the features of the os which utilise network, trial and error. It would be nice to know a good place to start looking though.
Internet sharing can use port 80
I do actually have internet sharing on I think. I will try disabling that.
ok I disabled all sharing just to be sure. I still get the same problem. I set log level to high and I get the following:
00:01:19 WebServer: WebServer: Serving HTTP on 192.168.0.3 port 80.
00:01:19 WebServer: ***
00:01:19 ATVSettings: init class CATVSettings
00:01:19 ATVSettings: load settings
00:01:19 Settings: getsetting enable_webserver_ssl=True
00:01:19 WebServer: started: 00:01:19
00:01:19 Settings: getsetting port_ssl=443
00:01:19 Settings: getsetting certfile=./assets/certificates/trailers.pem
00:01:19 Settings: getsetting certfile=./assets/certificates/trailers.pem
00:01:19 WebServer: ***
00:01:19 WebServer: WebServer: Serving HTTPS on 192.168.0.3 port 443.
00:01:19 WebServer: ***
00:01:19 DNSServer: DNS request received!
00:01:19 DNSServer: Source: ('192.168.0.2', 62399)
00:01:19 DNSServer: Domain: trailers.apple.com
00:01:19 DNSServer: ***intercept request
00:01:19 DNSServer: -> DNS response: 192.168.0.3
00:01:37 DNSServer: DNS request received!
00:01:37 DNSServer: Source: ('192.168.0.2', 57644)
00:01:37 DNSServer: Domain: trailers.apple.com
00:01:37 DNSServer: ***intercept request
00:01:37 DNSServer: -> DNS response: 192.168.0.3
by the looks of it port 80 is not being blocked, since it is serving the http to port 80. however I still do not get the error response when visiting http://192.168.0.3.
I assume this means that port 80 is ok for outbound services, but for inbound services it may be conflicting. This would explain why I am unable to connect to port 80 with my browser, and why apple tv cannot access the certificate from my mac os. I am trying to think of anything which could possibly block inbound services on port 80 but am at a loss there, I have no firewall or av software running and my router settings must be right since they work on windows bootcamp.
If you try https?
already tried https since I seen it suggested in another post.
I very recently reinstalled osx mavericks and can confirm that plexconnect is now fully operational.
The hard drive I had was failing, but I do not believe that hard drive was the issue since I have never had plexconnect working before on mac os (tried for years). I have however had plex connect working on windows bootcamp partition (on the same mac system, and the same hard drive).
Therefore I am led to believe it was either because plexconnect requires a fresh install of os x mavericks (and not an install updated from a previous version of mac os), or that there was a software/script interfering with plexconnect. I have no idea which software/script was the problem and have no way of checking, but I would recommend doing a fresh install of os x to anyone who is having similar problems to me.
>>plexconnect requires a fresh install of os x mavericks (and not an install updated from a previous version of mac os)
I - on the other hand - can confirm: PlexConnect works on a Snow-Leopard to Mavericks upgraded machine as well. :-D
I also upgraded from Snow Leopard to Mavericks without an issue for Plexconnect.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
