I still think taht the problem has something to do with the parameters of the request which gets send if you cli9ck on the Auto Detect buttons.
If Jeremy enters a full URL of a file on a remote server then the request seems to get redirected to the front page or the 404 page of the blog (and the log file was empty)
Maybe it is some kind of a security feature of those servers. Which does not allow requests with URLs which include a further URL to a remote server (or to a different domain).
If one enters a full URL as the location of a media file then a typical requests looks like
And the problem seems to exists only if auch an request includes an URL of a different domain:
1. Auto detect works fine on local hosted mp3s whether I just enter the filename or I enter the complete url.
Jeremy, I think that you could ask the hosting provider if there is a server side feature which filters request like the one above.
I will take further look on the encoding of the value of the