Not that this is your problem, but this kinda stood out to me as a potential other problem you may encounter in the future:

if ($servername eq "localhost"){

           # Define remote user if working locally
       $remoteuser = 'me';
           $file = 'E:/WAIWeb/mysql_login.txt';
        } elsif ($servername eq "www.wilcoxassoc.com"){
            # Define remote user when on production server
            $remoteuser = $ENV{'REMOTE_USER'};
            $file = '/var/www/mysql_login.txt';

         } else {
            foreach $key (sort(keys %ENV)){
                print ("<p>$key = $ENV{$key}");
            }
            &dienice("Could not connect to unknown servername of: $ser
+vername");
}
[download]

Ignoring, for the moment, the complete lack of consistant indentation (whitespace is important, folks! Just not to perl itself...), what would happen, for example, if someone set "localhost" in their hosts.conf file (or equivalent) to be your IP address? They'd get in with your privileges! While I have to admit, this is unlikely for most people to accidentally do, some enterprising hacker may figure it out, and suddenly have debug access to your entire setup.

Instead, you're better off putting this in a machine-specific config file - so that it becomes impossible for a hacker to become you short of compromising the box itself. Securing ssh, ftp, etc., is probably much easier than securing your application against this, so I'd highly suggest rethinking how you get into your "me" mode.