I run PMS and PlexConnect on my mac Mini which has an active Ethernet and Wifi Connection. The ethernet is 192.168.x.3 and the wifi is 192.168.x.4.
I would like My PMS and PlexConnect to both run on the ethernet (192.168.x.3), but for some reason PlexConnect seems to keep choosing the wifi (192.168.x.4).
Since I have all my apple TVs pointed to the .3 address, this causes it not to work on the AppleTVs.
If I disable my wifi and reboot the mac mini, everything works fine, but unfortunately i need to have both connections enabled.
I can see that there is a line in the settings.cfg file which will allow me to explicitly set the ip address but unfortunately when I try to edit the file it tells me the file is locked.
Can anyone tell me how to make this work so that it always chooses the ethernet connection instead of the wifi?
@bdee1 said:
I run PMS and PlexConnect on my mac Mini which has an active Ethernet and Wifi Connection. The ethernet is 192.168.x.3 and the wifi is 192.168.x.4.
I would like My PMS and PlexConnect to both run on the ethernet (192.168.x.3), but for some reason PlexConnect seems to keep choosing the wifi (192.168.x.4).
Since I have all my apple TVs pointed to the .3 address, this causes it not to work on the AppleTVs.
If I disable my wifi and reboot the mac mini, everything works fine, but unfortunately i need to have both connections enabled.
I can see that there is a line in the settings.cfg file which will allow me to explicitly set the ip address but unfortunately when I try to edit the file it tells me the file is locked.
Can anyone tell me how to make this work so that it always chooses the ethernet connection instead of the wifi?
In windows (although this should be similar in mac), you can change your Network Priorities, so if I have wireless and ethernet active I can set one to have more priority than the other.
I done a quick google search regarding if this is possible for mac, now I don’t know your OS but essentially you do the following. Source: Apple
1- Go to System Preferences, then click Network.
2- Choose Set Service Order from the Action pop-up menu.
3- Drag a service, such as Ethernet, to the top of the list.
4- Click OK, then click Apply to make the new settings active.
Those instruction are for OS X Mavericks, but it should be similar for other mac OS’s.
thanks for your reply! I actually had that same thought last night and I did move the ethernet priority up above the wifi priority in system preferences. Once I rebooted, PMS seemed to be grabbing the ethernet IP address, but plexConnect still seems to be grabbing the wireless ip address.
@bdee1 said:
thanks for your reply! I actually had that same thought last night and I did move the ethernet priority up above the wifi priority in system preferences. Once I rebooted, PMS seemed to be grabbing the ethernet IP address, but plexConnect still seems to be grabbing the wireless ip address.
So perhaps PlexConnect is using the wifi IP by default because it was originally set-up when wifi was the first priority in your network settings? (Although this is purely an assumption)
In that case shutdown PlexConnect by pressing CTRL-C when the terminal window is focused and wait for the processes to be stopped, then attempt to edit settings.cfg.
If you are still not able to edit the file then perhaps deleting it instead will resolve the problem?, To do this simply run PlexConnect after deleting settings.cfg and then cleanly shutdown the application (using CTRL-C), which will then create a new settings.cfg file, hopefully this will set-up the ethernet as your source for your local IP.
to clarify - when I go to stop plexConnect, I click the openPlex icon on my menu bar and then click the “Stop PlexConnect” button - but that doesnt seem to unlock the plexsettings.cfg file
@bdee1 said:
when you say press CTRL-C when the terminal window is focused, i’m not sure what terminal window you mean.
I do not have a terminal window open with the process running, so I am not sure how to kill the plexconnect process and unlock the settings file?
Sorry, I thought you were using the terminal when running PlexConnect… I’m assuming you have it running as a Daemon? If so then you need to enter a command to shut it down.
You will need to run terminal and enter sudo launchctl unload /Library/LaunchDaemons/com.plex.plexconnect.bash.plist for more information on this you can view additional commands at GitHub/PlexConnect//Install-Guide-Mac
thanks very much! I was able to stop the daemon, delete the settings.cfg file, replace it with a modified version with the ip explicitly set and reboot.
unfortunately after the reboot, plexConnect seems to still be starting on the wireless IP instead of the ethernet ip that i specified in settings.cfg
@bdee1 said:
thanks very much! I was able to stop the daemon, delete the settings.cfg file, replace it with a modified version with the ip explicitly set and reboot.
unfortunately after the reboot, plexConnect seems to still be starting on the wireless IP instead of the ethernet ip that i specified in settings.cfg
Did you check the settings.cfg to see if the IP you specified is still there? I’m thinking maybe PlexConnect is overwritting the settings.cfg file changing the IP back…
The above is based on the following information from the gethub.
PlexGDM
Disabling GDM auto discovery of your Plex Media Server
GDM is used to auto discover your PMS server, if you are having issues with it not automatically discovering your PMS or it is showing the wrong IP then you can disable this and hard code your PMS’s IP (and port if using a non-standard one).
GDM auto discovery is may get confused if you are running VmWare (or similar) or a VPN because of the IP addresses generated by these; the symptoms are usually that you cannot see your content thumbnails and content will not play, disabling GDM and setting a manual IP has been shown to resolve this particular issue.
NB if GDM is not disabled it will override any hard coded PMS IP. A sample configuration is shown below (note the capital ‘F’):
In some environments PlexConnect is unable to figure out the local IP address of its host system. You can disable the auto detect feature by editing the following lines, specifying your local IP address.
NB if you do not disable the auto detect then it will override any IP that you have hard coded in settings.cfg.
What is IP_SELF set to when you are running it without the setting? is it the local IP from your wireless or is it displaying your public IP address?, I think just having
If that doesn’t work, then the only thing to do would be to delete the cfg file run PlexConnect, then properly shut it down (using the commands provided previously), in order to generate the settings.cfg file, if plex starts up without the DNSServer issue, then using the newly pre-configured settings.cfg file do the following.
First back up the file so you have an original copy.
Enter these details enable_plexgdm = False ip_pms = 192.168.1.3 port_pms = 32400
Save the file, start PlexConnect, check the log. Hopefully the matter is resolved at this point, if not and if the issue is the DNSServer, then try restarting the machine again. Then we’ll have to go from here to find the cause of the issue…
There has to be a conflict somewhere… I’d assume the port wouldn’t need forwarded… but then again if it works on x.4 and not x.3 then maybe it is a port forwarding issue…
ok so i deleted the settings.cfg file and restarted the plexconnect daemon. This did generate a new settings.cfg file and the service started up without the dns error.
However the settings.cfg file is locked again and when I stop the plexconnect daemon the settings.cfg file remains locked - just like when I started…
@bdee1 said:
ok so i deleted the settings.cfg file and restarted the plexconnect daemon. This did generate a new settings.cfg file and the service started up without the dns error.
However the settings.cfg file is locked again and when I stop the plexconnect daemon the settings.cfg file remains locked - just like when I started…
Are you able to view the file? as long as you can get the content and back it up then you can create a settings.cfg with the same data and simply just modify that one part…
Do you have Plexconnect running with the highest privalage? maybe try running a text editor with the same privalages in order to edit the file?
Or perhaps try changing the permission of the file?
Just a quick search on how to do this in Mac… not sure what MAc Os you’re on… so hopefully that helps.
The goal is to backup the settings.cfg then modify or create another settings.cfg but with only the following settings changed. enable_plexgdm = False ip_pms = 192.168.1.3 port_pms = 32400
In theory since this is the only part of the file you are changing, then this should resolve all the issues.
Not sure why you need both the wifi and ethernet enabled simultaneously but for whatever reason…
Stop PlexConnect from the Settings Tab (This will stop it also via launchctl since OpenPlex runs PlexConnect via launchctl by default so PlexConnect starts as a daemon @ boot)
Copy your Settings.cfg file from the /Applications/PlexConnect folder to your desktop once its there you can edit it easily by changing this to your proper ip (it won’t let you edit it from within the /Applications/PlexConnect folder due to folder/file permissions and is easier to just copy it to your desktop to easily edit it, it is locked by design by iBaa most files are locked from editing wishing the PlexConnect base dir)
Once you are done editing it copy it back into the /Applications/PlexConnect folder. Now goto the advanced tab and backup your edited Settings.cfg. Next goto the extras tab and turn on the settings.cfg auto loader. Now start PlexConnect back up from the Settings tab. Check you log by clicking the log button and confirm its using the proper ethernet ip. If your router supports DHCP reservation I would highly recommend using it.
