Yoni

I do not have apache httpd-mpm.conf in my installation so I'll assume you are in an older version. First you shouldn't comment that line to prevent MPM conf from loading. MPM (Multi-Processing Module) is the default for the Windows NT operating systems. It uses a single control process which launches a single child process which in turn creates threads to handle requests. That's what is broken in your install right now. ThreadsPerChild 150 is fine. It will start 150 worker threads as you set in the configuration. The default value for ThreadsPerChild is 64 when used with mpm_winnt as in the case of UniServer. This directive sets the number of threads created by each child process and this number should be high enough to handle the entire load of the server. The default for Coral and newer is 250 threads.

For whatever reason is not finding your virtual host so apache will default to the www folder. Chances are that your vhosts config is not properly configured.

I would be cautious when upgrading to PHP 5.4.0. There has been a number of changes that will certainly create issues for your php applications from earlier versions. PHP 5.4.0 as I've been reading has removed/updated few very commonly used functions. Your code will need to be updated in order to run it on PHP 5.4.0. Also note that safe mode is not longer supported. Magic quotes has been removed. get_magic_quotes_gpc() and get_magic_quotes_runtime() now always return FALSE. set_magic_quotes_runtime() raises an E_CORE_ERROR level error. The register_globals and register_long_arrays ini directives have been removed. Most php5 code should be compatible but there are many things specifically to this release that shouldn't be overlooked before proceeding with the upgrade.

Awesome! Glad you figured it out. Just don't forget to update your awstats configuration accordingly otherwise the data won't be reflected on your awstats page.

That was just the reference. Note that you probably have enable logs in your virtual hosts, the httpd.conf main file only logs when there are no other log defined within your installation as far as I can tell. Chances are, taking into account what you are telling me, that there are other logs in your installation as in the case of vhosts... You are probably trying to get more logged info for your awstats This is what you can do: Enable in your main httpd.conf file: CustomLog logs/referer.log referer CustomLog logs/agent.log agent Go to your httpd-vhost.conf and make sure that "your_vhost-access.log" file is configured to log "combined" so you get as much logs as it is declared in your main httpd.conf file e.g: ServerAdmin webmaster@yourdomain.com DocumentRoot X:/UniServer/vhosts/yoursite ServerName yoursite.com ServerAlias yoursite.com ErrorLog logs/yoursite.com-error.log CustomLog logs/yoursite.com-access.log common combined This is what I get from my logs: x.x.x.x - - [08/Mar/2012:06:29:31 -0500] "GET /wordpress/wp-content/plugins/pirobox-extended/css/style_3/blank.gif HTTP/1.1" 404 3595 "http://unlockforus.com/wordpress/wp-content/plugins/pirobox-extended/css/style_3/style.css?ver=3.3.1" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20100101 Firefox/10.0.2" Hope this help

Remove the installation, download again an unpack. That might fix the issue. As for the screenshot in previous post, if you pay close attention you may noticed that the font size or window border size has be manually increased. Please, either reduce border padding or restore windows' default size.

Look in your apache httpd.conf file You need to enable mod_logio.c to use %I and %O #LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio

We can go that route. Even though there are things to consider when implementing .htaccess to do this. 1- Inconvenience. In the case of vhosts, you do have more than one site running in your server, so it is painful to go update .htaccess rules for each one of them to block a certain IP that has been misbehaving. You never wait for that IP to hit any other of your sites so you want to block it from accessing your server, period. This is common practice in production environments. Otherwise you will have to work for script kiddies and bad bots 24/7. 2- Performance In general, you should never use .htaccess files unless you don't have access to the main server configuration file. htaccess can degrade your server's performance considerably. When AllowOverride is set to allow the use of .htaccess files, Apache will look in every directory for .htaccess files. Thus, permitting .htaccess files causes a performance hit, whether or not you actually even use them! So every time you create an .htaccess file on a directory remember that apache will be cycling over it over and over again. Let's say for example you have a structure as following: /.htaccess /www/.htaccess /www/site1/.htaccess /www/site1/example/.htaccess For each file access out of that directory (/www/site1/example/) apache actually cycles over 4 additional file-system accesses, even if none of those files are present. On the other hand, putting this configuration in your server configuration file will result in less of a performance hit, as the configuration is loaded once when Apache starts, rather than every time a file is requested. This is the reason why I'm requesting the DEV team to consider a simple way to add/block specific IPs by using the GUI to make it less of a hassle to add IPs to a config file. Also, I'm asking this because users can edit the server root config file from within UniServer's console but not the vhosts.conf file which is where many of your site's config will reside. Last but not least, I try to skip the www folder to host any site 99.99% of the time. Many people running UniServer open to the world leave much info available for the bad guys to do their job. Let me give you a concrete example to make it clearer. Admins use vhosts for convenience so in the case of UniServer a user browsing to http://unlockforus.com will hit a vhost, that's fine. What happens in the case of the bad guys? They completely ignore your domain name and istead they always focus in your server's IP. Pinging unlockforus.com resolves to 75.74.61.88. So if you browse to http://75.74.61.88 you will in fact hit the UniServer page of the UniServer installation and not unlockforus.com, providing the bad guy a lot of information you certainly do not want to make easy for them to figure out. Let me show you a live example http://rogerstuart.com/ --> This guy is running on Uniform Server 7.1.2-Orion, Apache 2.2.19, MySQL 5.5.14 , PHP 5.3.6. It was just a matter of browsing to it's IP address instead of the domain name... http://66.116.74.45/

Hi, I would like to see an option in UniServer to deny access to specific IP addresses. I believe this would be a useful feature, specially for those running more than a single website. Is it something that could be considered for any upcoming release?

Beautiful design. Too bad that as a server app you won't be interacting with it much... oh wait, actually you will. People use UniServer as their test environment server 99% of the time.

I'm on PHP 5.3.10 and it is working for me. Enjoy. php_suhosin_0.9.32.1_5.zip Note, to prevent issues with phpmyadmin and few others make sure you relax the config with the suhosin.ini file I included. There is also the default one in case you wanna mod it yourself Suhosin causes problems in scripts such as vBulletin, Invision Power Board, PHPMyAdmin, Roundcube Mail and others. This will help you improve Suhosin settings in order not to mess with scripts. I found this online somewhere. I take no credits for it but I don't have the link to give due credits. By the way, I run Invision Power Board, PHPMyAdmin, Roundcube Webmail in my server without issues with the config I uploaded in my first attachment. check.zip And last but not least, some complain that Suhosin makes things go slower. It is true to some extent but if you optimize your server as many do to get the most out of it you won't notice a difference (not under not heavy loads). Keep your server files and databases defragmented, contiguous and a good active cache and serving will be snappy enough with Uniserver. Happy serving

Glad you figured it out!

Thank you. I should've read the config file options.

It is still crashing... the process is been recycled by the OS after a crash so that's the reason why you see your Apache ON and OFF. The service is restarting after each crash. My recommendation is to use a different version until this problem is worked out.

Ok now I could use some help to make me understand and fix this for everyone else in the long run. If I run it on a test Uniserver (everything runs with Administrator privileges) it works. So my believe is that there is a permission issue in the production server...?

See this post here: http://forum.uniformserver.com/index.php?showtopic=2440 Securing Server Services guide: http://unlockforus.com/uniform-server/services-security Hope it helps

Hi Please take a look here

It worked for me without a hiccup. Thanks for this simple guide. I'm gonna add it to the guides Credits to you @ linked to this page unless you have a site that you would like me to link it to. p.s I used my server's local IP instead of localhost otherwise it will not display any images at all from another computer in my network or from outside. Perhaps it would be prudent to use DirIcons="http://server_ip/awstats/icon" instead of localhost e.x: DirIcons="http://10.1.1.11/awstats/icon" (this is the server's local IP address if you are behind a firewall/static NAT). Also, add an .htaccess by default (sorry, I'm always paranoid about unnecessary access unless explicitly allowed). In my opinion, security will always be loose if you leave it up to the end user. It is (as a recommendation) effective to always restrict access and have the end user relax it as needed (IF it is ever needed in the first place). #------------------------------HTACCESS------------------------------------ # Server folder \cgi-bin\awstats .htaccess # This file provides server security limiting access to the localhost only. # Comment next four lines to deactivate. (Allow external access) #------------------------------------------------------------------------------ Order Deny,Allow Deny from all Allow from 127.0.0.1 Allow from ::1 #------------------------------------------------------------------------------ # Allow access from local network (LAN) # Uncomment next line(s) to activate. (Allow local network access) # Add your own network/subnet if not in this range. #------------------------------------------------------------------------------ #Allow from 10.1.1.0/16 #Allow from 10.0.0.0/16 #Allow from 192.168.1.0/24 #Allow from 192.168.0.0/24 #Basics # /8 means you can connect from 192.x.x.x # /16 means 192.168.x.x # /24 means 192.168.1.x # /32 means 192.168.1.x where x=Exact match e.x=192.168.1.10 #------------------------------------------------------------------------------ # Hiding the folder contents can be pretty useful from security point of view # If not enabled in Uniserver Default Directives #------------------------------------------------------------------------------ Options -Indexes #-------------------------------------END------------------------------------

That's odd. Files shouldn't just dissapear. If you are not the Administrator of the server you should contact them and ask them to look at the file and set a rule for it. It seems like your host is removing the file for whatever reason. Perhaps their security check finds it as a vurnerability. You are hosted in a Windows Server. Wondering what could be causing IIS to do this? Weird and interesting. Would love to find out.

There are users reporting issues with the latest apache bundle. I think it would be wise to make an extraordinary package (mix of 8.0.0 apache with 8.2.0 php, openssl, mysql, etc.) I think this would give the stability users are looking for in UniServer. Just offer it as an alternative package or something like that. It does work well and I have had it up there for over a month without a crash yet... Would that make sense?

You can test the webmail here: http://webmail.unlockforus.com (Google Calendar now syncs beautifully) Demo account ---------------- Bob, check the site out. Nothing special to brag about it except the fact that it is fully "Uniserved" http://unlockforus.com Server Uptime and Server Load http://unlockforus.com/server Wondering why newer APC version was not included with the latest 8.2.0 release? Newer PHP + APC rocks! I'm testing eAccelerator in another server and it also seems to do wonders. Need to put it under real stress to see how it behaves.

Dow again... Wondering what happens with that wiki section?

Hi Bob, Thanks a lot for your help. Your good intention is honestly priceless. I was able to solve the issue by upgrading my openssl and php versions respectively. I used the 8.2.0 php and ssl after some testing on my 8.0.0 installation. It is all good now. I haven't seen any errors in my logs yet so the "upgrade" can be considered a success. I'm able to finally sync my personal calendar and google's... Thank you so much. I will look at other things within the package and upgrade them slowly after testing. I can't afford to break it at this point. If ain't broken ain't fix it. That's how I do it

Hi there, I'm unable to sync with Google's calendar from my webmail application... Doing some investigation this is what I get from cURL debug: error:14092073:SSL routines:SSL3_GET_SERVER_HELLO:bad packet length I believe PHP is throwing this error because OpenSSL is compiled with no-tlsext? I'm on Coral 8.0.0 and this is really an issue affecting my production system. Is it there a work around to fix this? Can I use apache binaries to allow my application to work? Any tip is appreciated. This is the first and only issue that I have really faced with UniServer Coral running in production I think I have hit a month or so of uptime and even when there isn't much traffic yet Uniserver seems rock solid. Please, give me some hints on how to resolve this issue...

Ermm... I can't seem to replicate this in Coral 8.0; perhaps I'm not looking at the right place? Table names are displayed correctly here on the left hand frame.