Jump to content
The Uniform Server Community

BobS

Super Moderator
  • Posts

    331
  • Joined

  • Last visited

Everything posted by BobS

  1. First off, yes, the tray icon is gone, BUT there is a plugin that resolves this. Actually, there are three, and I suggest you use either the full or intermediate version. Secondly, there is a BOATLOAD of documentation, with pictures, INCLUDED with 8-Coral, and it makes using it and all the features available, much easier. For most problems you don't even have to post questions on the forum... Regards, BobS
  2. BobS

    Who is user pma?

    PhpMyAdmin puts this user in by default. It is described as the "control user," and it has only restricted access to the pmadb. This db is used exclusively by phpMyAdmin. If you search on "phpMyAdmin pma user", you'llfind several articles that describe this user and what it can and cannot do. The short answer is, no, don't delete it, but be sure it has a good password. Regards, BobS
  3. Interesting. I assume this is on Win7. Unfortunately, you don't show exactly where you put UniServer, which would be a big clue to the problem. Look at the includes directory and see if the mysql_password file is writable (for a start). See if there is a set_password.sql file, which would have been written by the script. When you run Start_as_program.exe, does UAC request authorization? It needs this to run the scripts properly. In any case, it seems that this is likely related to the location of UniServer. Regards, BobS
  4. Rustyp, First off, well wishes for your new site. The Uniform Server is a good starting point. As traxxus says, make sure you have only port 80 open and aimed at the proper machine. I expect that you have a NAT router in front of it. Consider it like a DMZ and don't have any other stuff running on it. That way you can back it up and restore in case of an attack. This may rule out using your "home computer", unless you have a second one for all your important information. If someone hacks through to the machine, you want to be able to kill and reload it. I'm not suggesting that breaches happen all the time. It's just that there are bots looking for easy targets. I run an ftp server at home, and the log shows daily probes for common user name logon attempts. These are from bots at work. The WinXP firewall isn't as secure as the Vista/Win7 version, which can be secured enough to forgo mod_security, which is likely overkill at this point. I'll look it over to see how it can be set up as a plugin. One thing you didn't mention is the audience type for your server, and whether you expect it to be open to everyone or just a select few. Will you need it to be found by search engines? Regards, BobS
  5. This symptom can be caused by several things. One cause (and the one I suspect to be most likely) is that you have an alternative MySQL config file somewhere else (like c:\windows) and it is being used instead of the one in The Uniform Server. You may also see a similar error on Windows 7 when running older versions of The Uniform Server. This is due to the change to prefer IPv6 for localhost. You can see this by using a command prompt and doing a ping localhost. Instead of 127.0.0.1, you'll get ::1 as the resulting address. In general, MySQL doesn't like this; it's expecting an IPv4 address. Since the message is coming from MySQL, we can assume that the .htaccess isn't blocking you. Regards, BobS
  6. Of course, if you had run Server Status, you would have seen that the programs were installed as services. Guess it will take some time for us all to get used to the new tools. Remember, you'll be better off if you WRITE DOWN what you are doing when you start out with a new system. That way you can go back and read what you did to get into the mess you're in. Regards, BobS
  7. This really sounds like UAC interference. Another possible agent of denial is your antivirus or antimalware system. Either of these will prevent Apache and MySQL from performing properly, since they will block the TCP ports. Since you're on Vista, you probably still have an IPv4 address scheme for localhost, so that is one less avenue to worry about. What makes this difficult to resolve is the lack of detailed error information. For example, if there is an Apache error.log created, that implies that Apache can at least start, but may not run. The contents of the file would be instructive. Secondly, there may be some useful info in the system event logs. You can also temporarily turn off the UAC to see what effect that has. Regards, BobS
  8. Why deprive yourself? Get them both! You can use the MultiServer capability in either one to change the ports and have both running together on the same machine. Just change the name of the UniServer directory, or install it as a subdirectory (eg., C:\Coral_8\UniServer). Experiment along with us and then you'll be ready for anything! Regards, BobS
  9. So it looks like you have a portable server and you tried to start it on Windows 7/Vista. Yep, that requires admin privileges. Regards, BobS
  10. For the first problem, this is totally new. Unfortunately, we need more details, such as file names, date and time, etc. and what was happening when these files appeared. The second problem is much easier. The UniTray plugin, doesn't install into the "plugins" directory, but rather to the UniServer directory (where the Start_as_Program.exe resides). It will add information to the plugins directory. In the future, when you have doubts about where a particular zip/7z/exe will extract files, you can always create new empty directory, use that as the target, and then inspect it to see what files and subdirectories are created. Regards, BobS
  11. The quickest way is to stop Apache, rename both logs to what you'd like to keep them as (such as access-2011-12-12.log) and then zip/7z the file to save space. You can then move it to somewhere else for later analysis. When you restart Apache, it will create new, empty logs. The more complex but automatic way is to run rotatelogs.exe, which is part of the Apache program set. This is done by changing the CustomLog directive in httpd.conf. I won't give a tutorial here about how to do this. Instead, read the Apache docs on rotatelogs: http://httpd.apache.org/docs/2.0/programs/rotatelogs.html for proper examples. This latter solution requires TESTING of your chosen parameters, unless you really know what you're doing. I have seen this used in conjunction with Webalyzer on other systems, but we haven't updated it for use with Orion or Coral. That's a new set of projects we'd enjoy some help in completing. Regards, BobS
  12. Thank you! That's the kind of response that energizes us and makes all the hours spent (well, most of them ) worthwhile. I'm sure I can speak for the rest of the group that we feel The Uniform Server is also our first choice. All kidding aside, thanks again, BobS PS, We DO look for additional help from others, and I noted from your subsequent post that you're suggesting a change. Please continue tossing those our way.
  13. I can agree with you for the production environment, but I do like indexes on for development. The problem with building a front-end is what to include and exclude. We're still looking for input, though. We'll entertain other thoughts you have for future releases. Regards, BobS
  14. Wow! That's quite a bit to process in one bite. We'll have to do some study to understand it, incorporate the changes and retest. Thanks for your suggestions! We all need to have extra eyeballs looking over the code. That's one of the great advantages of open source. Regards, BobS PS, you might try writing in Portuguese and letting us run the translation :-)
  15. Very interesting, Sehnor Agnaldo! Obrigado. After looking at the original code, I agree that this is factored much more effectively. I tried out the code, and it works properly. For the general audience, we'd probably not want Google do Brasil. Using your code as a base, I'll set it up for inclusion in an update to 7-Orion. Just now, we're still working on getting 8-Coral fully released. Ric does a great job of getting things running, but we all need help with the maintenance. Could I send you a list? ;-) (Just kidding, although that might be a line to follow...) Regards, BobS
  16. Well, it's not Winbinder (Ric knows), but if you look through some of the code, I think it will be easy to see what to do. The main place to look is in uni_con\includes\core_functions_inc.vbs. That's where the move functions are. Send a PM to Ric or me with your first tries, and we'll reply with suggestions. Regards, BobS
  17. Thanks mas123! This was a good idea. I had seen similar action in another WAMP and had thought of swiping the code. A modified version of your code is now in 8-Coral www\index.php, and I wanted to give you credit for inspiring it. Regards, BobS
  18. I guess I'm missing the intent behind this. OF COURSE it's supposed to be an improvement. But if you haven't looked it over in detail, or you don't care about usability features, that may be why you started this grumble without being specific. Remember, open source projects "REQUIRE" that if you complain, you must then back it with a suggested alternative, preferably a coded solution. That's why there are code snippets in this forum. Regards, BobS
  19. D'oh! You're EXACTLY right on the names! It always takes a fresh pair of eyes to find these obvious things. HOWEVER, that's a pretty well integrated name set, so it will take a bit to fix it. It took a wile just to change the spelling error on "development" a while back. ;-) CHANGING from Prod to Dev should be done by using the Unicontroller Server Configuration >PHP >Switch to Development Configuration file. It really works! You'll find that the php.ini changes to have the contents of the php.ini.development file. Regards, BobS
  20. Sorry, I didn't see the ref until just now. We'll discuss it. Regards, BobS
  21. Cool. Just wanted to get a feel for the frequency. It doesn't seem to be a regular occurrence (10-15 times/day). Regards, BobS
  22. I can see why you'd want those options. As you can guess from Ric's reply, though, "it's left as an exercise for the user." :-) One question I have is, why do you need to restart the server? That's not normally necessary, unless you make changes to the server configuration files. Regular "code" (HTML XHTML, PHP, etc.) doesn't require this. At most you may only need to flush your browser cache. Regards, BobS
  23. Spammers have pushed us over the tipping point. Open self-registration for The Uniform Server Wiki now requires that you request registration via the Forum. Specifically, register as a member and then (when approved) send a message to BobS. While the Forum also has problems with spammers, it has different ways available to deal with them. Hopefully this change will not be too annoying for sincere people who want to contribute to this community. Regards, BobS
  24. Thanks for posting this, stream. If weren't so busy getting working on The Uniform Server, the Wiki and answering Forum questions, we would give you more help. Perhaps in a few more months (March-April?). I also should add that what you're doing is EXACTLY what The Uniform Server was intended to do: create a platform for others to develop new add-on solutions. We obviously agree! These are just tools and you must learn how to use them first. THEN you can use the tools to help create the money-making business. Regards, BobS
  25. So I guess what you're really asking is, "If your WAMPS are so hot, why don't you use them to power your sites?" Right? The MAIN reason: Our hosting providers use a different solution to do their business. The PRIMARY purpose of a WAMP/LAMP solution is to create a test environment for your web development, one that doesn't actually put it out in public for all to see. The advantage of The Uniform Server is that it CAN be made Internet available (production-ready), provided you understand and address all the security risks. By this, I'm saying that you should always use the latest version of The Uniform Server in order to keep Apache, MySQL and PHP (and other components) properly patched. You must also have your operating system (Windows) highly secured and updated in order to make it Internet-safe. That's a lot of work for a small site, and requires vigilance. Also, if you expect a lot of traffic, you'll also have to have a machine and Internet connection that can handle it. Your local ISP would NOT be happy if you got 500,000 hits in a day on you home connection. This is why it makes more sense for a popular website to be professionally hosted. Hope this answers your question adequately. Regards, BobS PS. There are several more WAMP/LAMP solutions out there than you listed. Of all the offerings, I notice that none are updated as often or as quickly as The Uniform Server. Because of this, they present a bigger security problem.
×
×
  • Create New...