MrX

No problem

Just leave the host as localhost Uniform Server mySQL Defaults: Username = root ; Password = root Instructions on how to change the password can be found here.

What URL does your browser display in its address bar when you try to access your site?

Now I see what's wrong Why didn't I realize that you had the wrong password in $sql_pass earlier "67457e22ã1a15bd" is "root" encrypted, you shouldn't use the encrypted password to connect to mySQL

Get on #uniserver on irc.oftc.net

Ok, which server(s) are you currently in?

Have a look at this.

Come on IRC, I'll be there (at least for another hour)

Damnit, just remove everything that has to do with Virtual Hosts

I don't think Olajide would be pleased when he sees that link to XAMPP

You haven't been idling enough, then

If you want a quick reply, IRC should be your choice (if you're able to come on at the correct time)

Which distro are you using, when did you start using Linux and why? Installing Apache, mySQL, PHP and Perl (the main components of Uniform Server) are very easy if you have a distro with a decent package manager. You should be able to use Uniform Server's config files (httpd.conf, my.cnf and php.ini) on Linux, if you can't be bothered to create new ones from scratch. Uniform Server's directory structure is loosely based on that of Linux's, so you won't miss much of that Olajide has been pretty busy lately, so if a Linux version were to be made fast, it would probably be made by the community But then, how many people on this forum are using Linux? I know of a few who do, but they're still keeping their Windows PC(s) as they either have more than one PC or are willing to dual boot Linux and Windows. I do know of someone who certainly is "stuck" on Linux, and you sound like one as well. Anyway, you can still run Uniform Server on Linux by emulating a Windows PC with the help of VMWare (commercial) or QEMU (open source) Running Windows on Linux is one way, but if you're only trying to learn Linux, you could also run Linux on Windows as both VMWare and QEMU run on Linux and Windows. Another excellent way of running Linux on Windows is by using coLinux. With coLinux, you're able to run Linux at native speed, unlike what you would get if you used VMWare or QEMU

Ok, sorry for all that nonsense. I take back what I said. Now I know that "ScriptAlias" does the same thing as "AddHandler cgi-script .pl .cgi", thanks for telling me

I'm out of ideas, maybe you should try downgrading to PHP4?

I told Olajide about this mod_dav security flaw after AlleyKat's PC was "hacked", but he didn't fix it :| But I guess we can't blame him, considering how busy he is Anyway, if you don't need mod_dav or don't know what it does, then you'd better disable it with the instructions posted above. For those of you who really need (can't live without) mod_dav, you should protect it with a password, instructions on how to do that can be found at the mod_dav FAQ.

You're telling us that you were able to gain full access to Uniform Server's DocumentRoot without the need of a password, right? If no, then please provide more information. If yes, this problem probably has something to do with mod_dav being enabled by default. To solve this, make sure Uniform Server is running, then open W:\usr\local\apache2\conf\httpd.conf with notepad and search for "LoadModule dav_module modules/mod_dav.so". Comment that line (by adding # in front of it), it should now read "#LoadModule dav_module modules/mod_dav.so". Restart Uniform Server and try to gain access to Uniform Server with the method you mentioned above, you shouldn't be able to do it now. Hope that helps

Follow these instructions. The AS-Perl zip file mentioned in that article can be downloaded here. After you have everything installed, open a Command Prompt and type "perl -e "use DBI;"", if it gives you an error, then type "ppm install DBI" in the Command Prompt and try again. Tell me if it works

You're doing a port forward from 192.168.0.105:81 to us.defranks.net:80, right?

Who gave you the idea to comment that line by adding a # in front of it? By commenting something, you're telling Apache to ignore it. Also, what do you mean by extended config? Do you mean W:\usr\local\php\php.ini? If you do, I recommend that you don't modify that as you'll make it apply to the entire server. phpMyBackupPro might not be a poorly written script, but there certainly are some of those out there and who knows, you might just use one. Putting the config in the .htaccess file will make that setting only apply to phpMyBackupPro, which we know needs such a long time to complete as you have a big database and not because it is poorly written. Unless you're only going to use phpMyBackupPro with Uniform Server, I hope that you'll consider what I have said, change the php.ini setting back to what it was and use .htaccess instead.

What are you using? phpMyAdmin or phpMyBackupPro? The maximum execution time limit is a safety feature to prevent poorly written scripts from tying up the server, but sometimes it can also prevent good scripts from performing tasks that take a very long time to complete. Anyway, you can change the maximum execution time by opening W:\home\admin\www\phpMyBackupPro\.htaccess (it isn't there by default so you'll have to create it) in notepad and adding "php_value max_execution_time " to it, is the number of seconds a script is allowed to run before it is terminated. Something like 300 should work, but if you're still getting that error, keep increasing it by 60 until the error's gone Just remember that by increasing the maximum execution time, you'll be allowing scripts to use more resources on your server

No problem

Make sure the server is running and then open W:\usr\local\apache2\conf\httpd.conf with notepad. Firstly, search for "DocumentRoot "/www"" and replace that with "DocumentRoot "/httpdocs"". Next, search for "", there should be 2 of them, replace both of them with "". Then, search for "UserDir "/www/"", you can either comment that (add # in front of it) so that it now reads "#UserDir "/www/"" or change it to "UserDir "/httpdocs/"". Lastly, Don't forget to rename W:\www W:\httpdocs Hope that works