Ever since I upgraded to version 2.0 I am getting the following error... Installation Error Proxy Configuration Daemon not Running.. Please reinstall Jaksta Recorder..
I have reinstalled the product over and over again.
Thank you for your help.
Are you running any kind of cleaning/auto-delete program, specifically a program called Clean My Mac 3 (or anything similar)?
We have seen this program cause this problem in the past as it detects and deletes the proxy config daemon file, thinking that it is an unnecessary file for whatever reason.
Also, do you have the app installed and running from the top level of the Applications folder? If not, that has been known to cause this issue as well.
One other thing that might help is updating your Mac OS, if you are happy to.
hi, no clean my mac or the like in it. I use appZapper for uninstalls. But ive been using it for 5years with no previous problemsCan you seed a screen shot of proxy setting and ill do it manually. when i search for that file its not there. what is the location of it?
"Are you running any kind of cleaning/auto-delete program, specifically a program called Clean My Mac 3 (or anything similar)?"
Yes, I'm running Clean My Mac 3.
Can you please copy the proxy config daemon file location on Mac so I can try to whitelist it?
Also, does missing proxy config daemon file really cause the endless spinning "beachball" as soon as Jaksta is run? Shouldn't it just report an error?
Hi Alan and T,
The location of the proxy config daemon file is: System/Library/LaunchDaemons/com.ProxyConfigDaemon.plist
'System' is the hard drive that your machine runs from. In my case that is Macintosh HD.
Do not go looking for the file in your user profile file directory. You will not find it.
If you do have trouble finding it then I would suggest using the 'Go to Folder' option in Finder > Go, and then just put in the file path as: /Library/LaunchDaemons/
The file itself is com.ProxyConfigDaemon.plist and that is what you will want to whitelist/exclude from any cleaning or exclusion protocols you may have running.
From what we have seen, Clean My Mac 3 often causes problems even when it shouldn't. We have had users before who have reported that even after setting it to ignore the PCD file, it either still deletes it or it continues to interfere with Jaksta for unknown reasons. If this looks to be the case for you T, then I would suggest removing the software.
Normally a proxy config daemon error is displayed when it is either missing or corrupted, but sometimes depending on the system or other factors (such as other software that interferes) it just hangs instead and gives the ongoing beach ball.
There is a couple of things I'll get you to check:
1. Are you running Jaksta from the top level of your Applications folder?
2. Is your Download Location in the Preferences > Downloads set to a place that still exists and is accessible? - ie. NOT an external drive that is no longer connected
Start with those checks and then let me know.
ok, if found the file, but i have only a adblocker running. so what do i do?
Thanks for your possible solutions, in all accounts, everything is running local, I am running the application from the application folder. Any other solutions? Like I mentioned before, the previous version ran with no issues at all, it was until I upgraded to version 2 that I am having issues. Do you need anything else? Can you help me get this resolved?
I am having the same problem ono 1.5.1 and V2
Can you please try running it again and then when it crashes open Console and go to var/log/ProxycongigDaemon.log, and send through the ProxycongigDaemon.log file.
The log is showing that crash reports are being generated as a result of the PCD error. So it would be helpful if we could get those.
You can find them by opening the Console app and then use the side menu to navigate to /Library/Logs/Diagnostic Reports/ and there should be something in there that stands out. Might look something like ProxyConfigDaemon.crash
If you don't see anything there then try looking in ~/Library/Logs/Diagnostic Reports/ (the paths look similar but one has the '~' at the start of the file path). There may be a file that looks something like Jaksta Media Recorder________________.crash, where the blank space has the date it was generated and an ID number. This may be the only crash file that you find. Regardless of what else you find, send through the one dated as the most recent.
Also, if you look in /var/log there should be a file called ProxyConfigDaemon.log. Send that as well as it contains additional PCD information.
The next best thing to do would be to send through a clean copy of the log file. From what we should hopefully be able to see when the problem starts and what causes it.
To get a clean log, you will need to do the following.
- Open JMR
- Go to Preferences > General > Find Log File
- Close JRM but keep the Finder window with the log file open
- Delete the log file and still keep the Finder window open
- Reopen JMR (this will generate a new log file)
- Run JMR until you get the error
- Close JMR
- Go back to the Finder window the new log file and grab that log file and attach it here (don't copy and paste the code in it - send the file itself)
At any point does the program actually crash at all? Or do you just get that message and then it stays open? If it crashes, then you might also be able to get a copy of the crash log. To get it, when you reopen JMR you should get a notice saying 'JMR has crashed etc.' and it will give you three options - Reopen, Report, Ignore. If you click on 'Report' then it should take you to another screen where you can press another button to get the crash log. If you get that far, then same thing again and just attach the file here so I can take a look.
Thanks for your support. Please, help me resolve this issue, I am very frustrated with the product, it worked fine for almost a year, then after the update it quit working.. as per your request, here is the log file.
Let me know what else I can do..
To answer the last part of your question, the program will not crash, it remains open but is not functional after that.