I’ve just installed MT 4.23 and get quite far through the wizard. It lets me type in the config details and setup the first user, but when clicking next, it says the usual “You don’t have permission to access /cgi-bin/mt/mt-upgrade.cgi on this server.”
Any ideas?
Running on Linux
Reported on Movable Type 4.2

The last screen I see is the "Create Your First Blog" screen, then press "Finish install".
Do you know if your server is running SELinux?
http://budgibson.com/home/archives/2007/08/installing-movabletype-4-on-red-hat-enterprise-linux-5.shtml
Check the chmod of the files and all parent directories and or SELinux configuration as mentioned earlier
Thanks for the replies and your help guys, appreciated.
I am not using SELinux. I made sure all the permissions were correct, all the way to the top, but it is still having the same problem. Over the last few years I've installed Movable Type a few times now, and this always happens. I can't figure it out, it seems completely logical and I followed a set of instructions (although each set I read, even from Movable Type is different) and it just never works.
This is so infuriating.
Any other ideas, other than sitting here staring at CHMOD boxes?
Whose version of Linux are you using?
Thanks for replying Mike.
I am using CentOS 4.7.
Hmmm, are you sure that you don't actually have SELinux up and running? It's a default on RHEL, and CentOS is directly based on RHEL. Other than that, I don't know what to say other than 403 issues are Apache-related (obviously) and that's your best bet for looking.
On a related subject, unless they actually fixed it in 4.7, there is a long-standing, very, very serious performance bug in RHEL and CentOS' version of Perl. You might want to try the Linux version of XAMPP or look into either SuSE or Ubuntu Server if you can't get all of this resolved on CentOS.
Seems they fixed that Perl bug, at least for CentOS 5 and RHEL 5.
It would seem to me that something fails to write the index page and the web server having options indexes off. Which will result in a 403 error at the webroot of the blog. I assume the cgis still work.
If chmods are correct, are they correct for the right user? Care to share? What does the web server log for the 403 error?