Troubleshooting, FAQs and Support

I have released this script as a service to the broader community, as is, in an unsupported manner with no guarantees of support from either myself or my employer (The Australian National University). Hopefully this website and the following information however of assistance. If you still require support, try the options listed under Support.


Things to try

Try running munkiimport manually
If you can't import items with munkiimport, will fail. The most likely problems are that the repo isn't mounted and / or your user doesn't have permissions to write to the repo.

Try a verbose run
Try running --verbose --data /path/to/individual/data.plist. This will show more information that may help in tracking down the problem. A second --verbose can be used for even more information.

Look at the log file
Open the log file in your favourite text editor. There maybe some useful information in it. The default location for the logs are /Library/​Logs/​autoMunkiImporter. The log location can be overridden by the data plist however.


curl is used to access the web pages, handle redirects, and finally check if the application should be downloaded, and if so to download the application. You will occasionally get different results from curl then from Safari, so testing curl manually may be helpful.

The best strategy is to use curl --head --location and review its content. Sites like Google Code block retrieving headers which is required for this script to work. In this case one of the returned headers will be X-Content-Type-Options: nosniff.

Also try using different (or no) User Agent (curl --user-agent "my agent").

Frequently Asked Questions

I could use this to automatically deploy updates via Munki couldn't I?
Yes... BUT you shouldn't use it for that purpose. If you want to automatically deploy software you are not running a managed environment, and in that case you should let the applications run their own self updaters, or users install updates themselves.

Auto Munki Importer can get major version changes which could have a material impact on your business. Each new application update should be tested and approved before being released to your production clients.

I would only suggest automatically deploying to machines used by the systems administrator(s) for internal testing.

Auto Munki Importer downloaded previous version fine, but it hasn't downloaded the latest version...
As the tool is monitoring websites that we have no control over, a change in the website can stop the script from running. There is no guarantee that Auto Munki Importer will continue to work for a site it's previously worked on. You may need to update the data plist, or try a different type depending on the changes.

Can I trust Auto Munki Importer to always download the latest version?
No! As Auto Munki Importer monitors websites that are outside of our control there is no guarantee that it will always work. You should from time to time review all of your monitored apps and ensure that you have downloaded the latest version. The status plist at /Library/​Logs/​autoMunkiImporter/​autoMunkiImporterStatus.plist is a good place to start as it lists the download history of every application that's being monitored.

Can Auto Munki Importer handle "delta" updates (e.g. Adobe Creative Suite or Microsoft Office updates)?
No. It's designed for complete applications that could be deployed independently of any other requirements.

I want to make some changes to Auto Munki Importer. Will you accept the changes?
If you would like to see changes you make merged into the Auto Munki Importer codebase, please make a pull request in Github. The changes will be assessed and considered for inclusion.

I wish Auto Munki Importer could do "x". Will you add it?
Please log feature requests via the Auto Munki Importer Issue Tracker, however I can offer no guarantees that they will be actioned. Auto Munki Importer is however open source, so you can view the latest version of the source code at and possibly make the changes yourself.



Please consult the Auto Munki Importer Github Wiki. There maybe additional tips or tricks that may assist you.

Issue Tracker

If you have a problem, you can raise an issue at the Auto Munki Importer Issue Tracker.

To assist in resolving the problem, please use the following template, filling in the details between the < > brackets:-

Application Name: <App Name>
Version: <Version>
URL of Website: <Website URL>

Complete Data Plist:
<Data Plist>

Output from --verbose run:
<Verbose Run>

Auto Munki Importer Version:
<output of --version>

Example Data Plists

A number of data plists are included with the installer, however additional data plists may be shared by members of the community, and where possible will be collated at

Data plists can be submitted via the Issue Tracker, and / or via a Github pull request.

Source Code

Auto Munki Importer is a Perl script, as such all of the source code is easily accessible. You can view the latest version of the source code at The comments in the source code may help identify the issue.