BobS

Let's go back even further; what version of Windows are you on? WS2003 or WinXP? I assume you're not on later versions, but I don't know that, and it makes a big difference. Also, which revision of version 7? I have been using 7.0.0, but this may also be a problem source for you. That's likely because there's no conflict with port 80. I don't recall enough about old 3.3 to remember just why. So the first question is what do you mean by "turn off" and "restart"? These terms aren't clear enough to explain just exactly what is happening. I assume you mean stop all processes from 3.3 and remove disc W:, so that there are no leftover remnants. That means when you start version 7, it should create the icon This may be blocked by security restrictions. In any case if you can't see the icon, exactly how are you starting the servers? Then you say "restart," but don't say what exactly you're restarting, or how. Also, have you used task manager or process explorer to check on what is running? What are the results? Use the a_diagnostic/server_status.bat, which will show you the port status, plus much more. Regards, BobS

This depends on the version of Windows. For Win Server 2008, Win 7 or Vista, you MUST start the tray icon as an administrator. Following that, for any Windows version, just right-click on the tray icon and select "Install and Run All Services". This will set up MySQL and Apache as service processes that will auto-start when you boot. Note that the tray icon will not auto-start, just the services. Regards, BobS

First off, is IIS running? Are you using that in lieu of Apache? In any case, be sure to check the ports first. Regards, BobS

One source of this error is a block by IP address. Look in \UniServer\www\.htaccess. Note that only 127.0.0.1 is allowed. To add other machines on your local LAN (assuming it's on a simple router), add 192.168 to that line. This allows all addresses in the 192.168.x.x range to access your server. Order Deny,Allow Deny from all Allow from 127.0.0.1 192.168 Regards, BobS

Must be embarrassingly obvious from the logs

You could always look at the error.log and access.log files for a bit more info. You'll find them in \UniServer\usr\local\apache2\logs directory. Regards, BobS

Sorry, still missing some info, like what version (by number, like 7.0.1) and what OS (XP. Vista, 7). It's hard to take a shot in the dark, as Ric noted. Regards, BobS

Did you use http://localhost:500/ ? (Sorry, had to check the obvious first) If you're using UniTray.exe to start the servers, you also need to change \home\admin\www\redirect.html so it will go to localhost:500 Regards, BobS

Let's go back to the starting point, and then use the built-in server change capabilities to move things. That way we can more easily isolate the problem. Stop the servers and then access the server port change at the Unicon tray icon through ">Advanced>Move Servers multi-server operation". This fires off a command screen that prompts for verification of the changes; just accept all the suggested ports. Note that the tray icon changes to a 2. Then restart the servers. It's here that the firewall will flash up new blocks because the server ports have changed. Then after displaying the splash redirect screen, your browser should show http://localhost:81/index.php, the welcome page. If this does the job for you, stop here. Otherwise, take a look at the files that changed. For Apache, http.conf has three changes at the lines noted: 124: Listen 81 1010: NameVirtualHost *:81 1014: Similar lines are changed in ssl.conf for the secure server. In addition, the \home\admin\www\redirect.html needs to have the link modified: The other changes allow for unique names of the servers and Unicon. Hope you follow that... Regards, BobS

Thanks for saying what UniServer version you're using. I've had this type of problem myself, and I vaguely recall that it was related to the .htaccess files. Those "Allow From" lines can be very tricky. In my www\.htaccess I put Allow from 127.0.0.1 192.168 so that I can access the server from other machines on my LAN. My home LAN is on 192.168.3.xx and work is on 192.168.5.xx. By specifying only the 192.168, both those LANs work with my UniServer (it's on a USB drive). For externally available sites, you have to open it much further, and I think you have to change the whole block. It's in the Apache manual. If you're using IPv6 though, we're in a different situation. Hope that helps; give us some feedback. Regards, BobS

Where you have "F:\UniServer", for example, just change that to "\UniServer". Clearer?

No ideas. Not enough info to form an opinion, either. Need to see line #563 and surrounding 10 (or-so) lines. That way we can check the syntax. Oh, and also the first 10 lines of the file as well. I assume this is an SQL export file of another DB? BTW, MySQL 5.5.9 is not "old" in this sense. That's just a catch-all error msg. Regards, BobS

First off, you do NOT need to serve these files in order to read them. Just open them directly in a browser. Secondly, even if it seems a good idea, the one huge HTML file is BAD for this purpose, since it clogs your browser cache (and who knows what else). It contains all the graphics as well. everything is dying just doing the render. Sometimes the SIMPLE approach is the best. Corals is right; download the tar.gz.. HOWEVER, even this doesn't need to be served via UniServer. Just use a browser to open it directly. Regards, BobS

Thanks DanyO! This is good information for all of us. Well done.

Good question, with multiple answers, depending on what you really want to do. First, yes, you can change the initial page displayed, and there are various techniques to do it. However, I have to ask what your goal is for this; what is the behavior you're trying to create? Since the default action for UniServer's server start in the tray tool is to execute index.php, I assume that instead you want it to go instead to your program, which is "console.php." Now, the default index.php displays a lot of information about The Uniform Server makeup and status, and also has several links to other pages and sites. One of these goes to the Administrator panel, which is in home\admin\www. Was one of these two pages what you intended by the term "console.php"? In any case, one choice is to just replace the contents of index.php with what you would put in console.php. This essentially puts your code into the file which gets executed automatically. It's what I think is the best solution. You can also rename the current index.php to uniserver.php, thus preserving the code, which you can link to from your application, if desired. Another technique would be to use a redirect in the .htacces file. See the Wiki for details on this: http://wiki.uniformserver.com/index.php/Htaccess:_Redirect The good thing about this method is that it's very easy to change, very specific, and is quite portable. The redirect merely looks for a request for index.php and changes it to console.php, but just for the one directory. I don't recommend you do this next one, since it's a global change for a local effect. It's also usually not repeatable on hosting services. The search order for index pages to be displayed is governed by the DirectoryIndex directive in the httpd.conf file, which is in C:\UniServer\usr\local\apache2\conf (normally). Mine looks like: DirectoryIndex index.html index.shtml index.html.var index.htm index.php3 index.php index.pl index.cgi The first file that matches (from left to right) will be executed by the server. There are more details to this, but that's the essence. So one thing you could do is to add "console.php" to the start of this directive. Again, less than optimal. This next one is more detailed, since it gets into the details of UniCom, the Start.exe program, which is quite powerful. There are many things you can change. See the Wiki and the code for more details. The default sequence of operation is that when the Apache server is started, its first task is to display Uniserver\home\admin\www\redirect.html, which displays The Uniform Server splash screen and then jumps to index.php. You *might* change this to go to console.php, but when a new version of UniServer comes out (Ric is a busy lad), you'll have some work to do putting in the update. It also may create other problems, so again, it's less than optimal. Hope that helps, BobS

I agree, even though it doesn't run on Linux, only on Windows. That's why it's called a WAMP. I'm also happy 5.6.10 worked for you, but you could have used 5.7.5, which is even more up-to-date. Regards, BobS

I have used phpMyBackupPro on both Windows and Linux and found it to be very finicky to set up right. There are several aspects that don't work smoothly. The fact that it hasn't been maintained is another mark against it. I suggest you opt for an alternative. Regards, BobS

Unfortunately, that question is rather open to interpretation. In any case, Apache is secured the same way under any stack, not just UniServer. I suggest you look at The UniformServer Wiki for several articles about this. Plug this string into Google for a list of references: apache .htaccess site:wiki.uniformserver.com It will show you all the Wiki articles that are specific to UniServer and Apache and/or .htaccess. The key locations to check are in httpd.conf and www\.htaccess, which are the normal locations for most Apache installations. Check out these two other sites for good tutorials: http://httpd.apache.org/docs/current/howto/htaccess.html http://www.thesitewizard.com/apache/index.shtml Regards, BobS

This is a function of your application, not Apache or any UniServer program. IMHO, you should check with the RedAlert website for an update, or post on their forum. Regards, BobS

The fastest way to remove UniServer (any version) is to delete the entire directory. However, that also seems to delete the apps, too. To just update UniServer, I usually follow the procedure in this thread: http://forum.uniformserver.com/index.php?s...post&p=8729 Regards, BobS

Yes. The beauty of the Uniform Server system is that it's portable. What you may have to do, though, is to check whether your application needs to be adjusted if the domain name is changed. I know that WordPress requires this. It's a simple change in one of the database tables, specifically wp_options. The siteurl and home entries need to modified to reflect a new domain name. But if you use the same domain name, you should be good to go. Regards, BobS

It sure does, Simon. Thank you for writing this up. In general, your method is what I have been using for some years, and not only on UniServer. Obviously, if you have edited some of the vhost or other config info, it's "left as an exercise for the user" as to how to handle that. I would also add that you may want to do comparative update of php.ini, rather than copying the old one. It's just a feeling that there may be version updates reflected there that you'll lose otherwise. The KEY thing to do is to KEEP NOTES on what you changed in the configs and server base (everything outside of www and mysql\data), so that when you want to change the "undercarriage," you'll know what needs inspection. I also keep a spreadsheet of the apps with parameters, account names and passwords. This is in case I need to do a reinstall or forgot how to access it. The only problems I've had were with apps that weren't happy with the php version change. Other than that, everything moves across easily, just as you said. Regards, BobS

Great question, Jeret. I checked this out a while back, and at that time, the answer was "yes and no." Yes you could do it, but it's a real pain and isn't necessary. In reality, it's just like any other system that allows for multiple user accounts. Would you remove the Administrator account from your Windows machine? Probably not, but you *could* rename it to "admin" or "addy," right? In any case you DO need an account that has administration rights. Now, in UniServer, root is the account that ties MySQL, phpMyAdmin and the UniServer admin control together for MySQL. If you'd like to change or redesign it, feel free, but it sure will make updates a challenge. What is most practical IMHO is to put a really good password on root, then restrict access to the tools that use it to be only from the local machine. This means you actually have to be logged in to the controlling account before it will display your login screen. Hope that's clear, BobS

Busy, busy bee... Thanks, Ric. This may solve some of the support requests before they get posted

First off, .htaccess files are essentially extensions of the Apache configuration file. They direct the server in how it should treat various requests, and what information it can return, among other things. So using UniServer is not related to that aspect of the problem. That notwithstanding, the problem is directly related to what AceSEF is doing in relation to the contents of the .htaccess file. You WILL want to use it to control unauthorized access, but I'll caution you first that, even for programmers, the syntax is complex and somewhat difficult. The one key you included that might help concerns the 404 error. Usually this pops up when a directory is unavailable, or the rewritten request string is faulty, which gives the same result: server can't find the info. Look at the (Apache) access.log and error.log files for some additional clues. Without more details on your setup, it's hard to say just what may be the problem. Regards, BobS