Give that a go, but apart from finding something creating problems in the background I am out of ideas. So to check that, you would type: ps -ef | 'citrix' OR ps -ef | 'Citrix' Try searching for that citrix program you mentioned earlier, and see if that still isn't operating in the background. Where in the place of 'name of process' you would type in part of the name of a process that you might suspect is running - it is case sensitive as well. This will filter down the results, rather than showing you everything. You can also try: ps -ef | 'name of process' It will be a big, convoluted list but have a quick scan through and see if there is anything that stands out as something that might interfere with the proxy settings. It will give a long list of all the processes running, including ones that will sometimes not appear in Activity Monitor. So unless you are turning it off manually (which we know you are not), there must be something else messing with the settings.Ī more in-depth way you can check this is by using Terminal. 18:28:09.347 Jaksta Adapter Monitor Thread caught exception Couldn't get netmask for device awdl0 awdl0: no IPv4 address assigned while starting monitor for adapter awdl0įrom the log it looks like Jaksta is setting the proxy as it should but then its turning the monitoring off straight away for some reason. 18:28:09.347 Jaksta Stop Capturing awdl0 18:28:09.346 Jaksta Adding Adapter awdl0 18:28:09.346 Jaksta Start Capturing en0 (ip6 or ip) and tcp and ( port 1935 ) 18:28:09.341 Jaksta ConfigDaemonClient:Waiting For Commands 18:28:09.341 Jaksta Created Adapter Detector Thread, Checking Every 5000 ms. 18:28:09.341 Jaksta ConfigDaemonClient:Received SET PROXY 3129 OK 18:28:08.289 Jaksta ConfigDaemonClient:Sent start 3129 18:28:08.289 Jaksta ConfigDaemonClient:Received OK 18:28:07.901 Jaksta ConfigDaemonClient:Sent stop 18:28:07.895 Jaksta Stopped Capturing en0 (ip6 or ip) and tcp and ( port 1935 ) 18:28:07.129 Jaksta Started Listening On Proxy Server Socket port:3129 18:28:06.921 Jaksta Stopping Adapter en0 18:28:06.921 Jaksta Removed Adapter awdl0 18:28:06.921 Jaksta Stopping Adapter awdl0 18:28:06.918 Jaksta Cert Key Parsed Cert Ok:1 18:28:06.918 Jaksta Cert Auth Parsed Cert Ok:1 18:28:06.910 Jaksta JAK: Preferences changed 18:28:00.922 Jaksta JAK: PreferencesController.awakeFromNib 18:28:00.869 Jaksta JAK: PreferencesController.init In the logging it show it is messing with proxy setting It seems something is changing the proxy settings. 19:46:57.953 Jaksta JAK: PreferencesController.awakeFromNib 19:46:57.890 Jaksta JAK: PreferencesController.init 19:46:17.745 Jaksta Adapter Monitor Thread caught exception Couldn't get netmask for device awdl0 awdl0: no IPv4 address assigned while starting monitor for adapter awdl0 19:46:17.745 Jaksta Stop Capturing awdl0 19:46:17.743 Jaksta Adding Adapter awdl0 19:46:17.743 Jaksta Start Capturing en0 (ip6 or ip) and tcp and ( port 1935 ) 19:46:17.729 Jaksta ConfigDaemonClient:Waiting For Commands 19:46:17.728 Jaksta Created Adapter Detector Thread, Checking Every 5000 ms. 19:46:17.726 Jaksta ConfigDaemonClient:Received SET PROXY 3129 OK