Jump to content
The Uniform Server Community


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

About babyewok

  • Rank
    Junior Member

Previous Fields

  • Main OS
    Windows XP
  1. I have Uniform Server Zero XII and I have a virtual host set up (mysite.localhost). I want to use ssl for the whole site. I am a little confused about the process of setting up SSL in uniserver for a virtual host (even after looking at the docs) - could someone talk me through it please? I generated a certificate and then duplicated the default Virtual Hosts in UniServerZ\core\apache2\conf\extra\httpd-ssl.conf adding in my site directory as you do for settign up a non-ssl virtual host: <VirtualHost *:${AP_SSL_PORT}> # General setup for the virtual host DocumentRoot "${US_ROOTF_SSL}/ssl/mysite.localhost" ServerName "mysite.localhost" ServerAdmin "email@email.com" ErrorLog "${US_ROOTF}/core/apache2/logs/mysite.localhost-error_ssl.log" TransferLog "${US_ROOTF}/core/apache2/logs/mysite.localhost-access_ssl.log" # SSL Engine Switch: # Enable/Disable SSL for this virtual host. SSLEngine on # Server Certificate: # Point SSLCertificateFile at a PEM encoded certificate. If # the certificate is encrypted, then you will be prompted for a # pass phrase. Note that a kill -HUP will prompt again. Keep # in mind that if you have both an RSA and a DSA certificate you # can configure both in parallel (to also allow the use of DSA # ciphers, etc.) # Some ECC cipher suites (http://www.ietf.org/rfc/rfc4492.txt) # require an ECC certificate which can also be configured in # parallel. #== Server Certificate: SSLCertificateFile "${US_ROOTF}/core/apache2/server_certs/server.crt" # Server Private Key: # If the key is not combined with the certificate, use this # directive to point at the key file. Keep in mind that if # you've both a RSA and a DSA private key you can configure # both in parallel (to also allow the use of DSA ciphers, etc.) # ECC keys, when in use, can also be configured in parallel #== Server Private Key: SSLCertificateKeyFile "${US_ROOTF}/core/apache2/server_certs/server.key" # Server Certificate Chain: # Point SSLCertificateChainFile at a file containing the # concatenation of PEM encoded CA certificates which form the # certificate chain for the server certificate. Alternatively # the referenced file can be the same as SSLCertificateFile # when the CA certificates are directly appended to the server # certificate for convenience. #== StartSSL certificate chain for class 1 certificates # Disable when using a self-signed certificate # Enable remove # disable add # #SSLCertificateChainFile ${US_ROOTF}/core/apache2/server_certs/sub.class1.server.ca.pem #SSLCACertificateFile ${US_ROOTF}/core/apache2/server_certs/ca.pem # Certificate Revocation Lists (CRL): # Set the CA revocation path where to find CA CRLs for client # authentication or alternatively one huge file containing all # of them (file must be PEM encoded). # The CRL checking mode needs to be configured explicitly # through SSLCARevocationCheck (defaults to "none" otherwise). # Note: Inside SSLCARevocationPath you need hash symlinks # to point to the certificate files. Use the provided # Makefile to update the hash symlinks after changes. #SSLCARevocationPath "c:/Apache24/conf/ssl.crl" #SSLCARevocationFile "c:/Apache24/conf/ssl.crl/ca-bundle.crl" #SSLCARevocationCheck chain # Client Authentication (Type): # Client certificate verification type and depth. Types are # none, optional, require and optional_no_ca. Depth is a # number which specifies how deeply to verify the certificate # issuer chain before deciding the certificate is not valid. #SSLVerifyClient require #SSLVerifyDepth 10 SSLVerifyClient none SSLProxyEngine off # TLS-SRP mutual authentication: # Enable TLS-SRP and set the path to the OpenSSL SRP verifier # file (containing login information for SRP user accounts). # Requires OpenSSL 1.0.1 or newer. See the mod_ssl FAQ for # detailed instructions on creating this file. Example: # "openssl srp -srpvfile c:/Apache24/conf/passwd.srpv -add username" #SSLSRPVerifierFile "c:/Apache24/conf/passwd.srpv" # Access Control: # With SSLRequire you can do per-directory access control based # on arbitrary complex boolean expressions containing server # variable checks and other lookup directives. The syntax is a # mixture between C and Perl. See the mod_ssl documentation # for more details. #<Location /> #SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \ # and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \ # and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \ # and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \ # and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \ # or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/ #</Location> #== Server Root folder: <Directory "${US_ROOTF_SSL}/ssl/mysite.localhost"> AllowOverride All Require all granted SSLRequireSSL </Directory> # SSL Engine Options: # Set various options for the SSL engine. # o FakeBasicAuth: # Translate the client X.509 into a Basic Authorisation. This means that # the standard Auth/DBMAuth methods can be used for access control. The # user name is the `one line' version of the client's X.509 certificate. # Note that no password is obtained from the user. Every entry in the user # file needs this password: `xxj31ZMTZzkVA'. # o ExportCertData: # This exports two additional environment variables: SSL_CLIENT_CERT and # SSL_SERVER_CERT. These contain the PEM-encoded certificates of the # server (always existing) and the client (only existing when client # authentication is used). This can be used to import the certificates # into CGI scripts. # o StdEnvVars: # This exports the standard SSL/TLS related `SSL_*' environment variables. # Per default this exportation is switched off for performance reasons, # because the extraction step is an expensive operation and is usually # useless for serving static content. So one usually enables the # exportation for CGI and SSI requests only. # o StrictRequire: # This denies access when "SSLRequireSSL" or "SSLRequire" applied even # under a "Satisfy any" situation, i.e. when it applies access is denied # and no other module can change it. # o OptRenegotiate: # This enables optimized SSL connection renegotiation handling when SSL # directives are used in per-directory context. #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire <FilesMatch "\.(cgi|shtml|phtml|php)$"> SSLOptions +StdEnvVars </FilesMatch> <Directory "${US_ROOTF}/cgi-bin/"> SSLOptions +StdEnvVars </Directory> # SSL Protocol Adjustments: # The safe and default but still SSL/TLS standard compliant shutdown # approach is that mod_ssl sends the close notify alert but doesn't wait for # the close notify alert from client. When you need a different shutdown # approach you can use one of the following variables: # o ssl-unclean-shutdown: # This forces an unclean shutdown when the connection is closed, i.e. no # SSL close notify alert is sent or allowed to be received. This violates # the SSL/TLS standard but is needed for some brain-dead browsers. Use # this when you receive I/O errors because of the standard approach where # mod_ssl sends the close notify alert. # o ssl-accurate-shutdown: # This forces an accurate shutdown when the connection is closed, i.e. a # SSL close notify alert is send and mod_ssl waits for the close notify # alert of the client. This is 100% SSL/TLS standard compliant, but in # practice often causes hanging connections with brain-dead browsers. Use # this only for browsers where you know that their SSL implementation # works correctly. # Notice: Most problems of broken clients are also related to the HTTP # keep-alive facility, so you usually additionally want to disable # keep-alive for those clients, too. Use variable "nokeepalive" for this. # Similarly, one has to force some clients to use HTTP/1.0 to workaround # their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and # "force-response-1.0" for this. BrowserMatch "MSIE [2-5]" \ nokeepalive ssl-unclean-shutdown \ downgrade-1.0 force-response-1.0 # Per-Server Logging: # The home of a custom SSL log file. Use this when you want a # compact non-error SSL logfile on a virtual host basis. #CustomLog "c:/Apache24/logs/ssl_request.log" \ # "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b" </VirtualHost> I also copied the site across from www/ to ssl/ (does it really have to be physically moved there, can't it just stay in www?). Now I get a 403 error when I try to visit https://mysite.localhost - have I missed something?
  2. I am using an aging Nano 5.6.16 version of uniform server and want to update, but it seems that the latest versions have a problme with Zone Alarm. I have the very latest version of Zone Alarm Internet Security Suite, but still get a message when I launch unicontroller warnign me about the blue screen of death and that updating to the latest version of zone alarm will solve the issue. The controller then doesn't seem to open, but the process is running Now, does the controller actually detect the version of zone alarm? In other words, is it just saying, "unless you have the latest version of ZA, you'll have trouble - if you have the latest version, you're fine." or is it saying "your detected version of zonealarm will cause trouble"? Also, if I disable zone alarm before running the controller, it all opens up just fine. It's not very practical to have to keep enabling/disabling zone alarm all the time!
  3. Bump - seriously? Does no one that uses Zone alarm use uniserver anymore? The info on this issue is very vague
  4. OK, So I have Windows 7 Pro and the latest version of Uniform Server: Uniform Server_12_0_0_ZeroXII. I also have the latest version of Zone Alarm Internet Security Suite ( However, if I try to launch the UniController, I get told that I am running Zone Alarm and that I may get the blue screen of death, etc ....or upgrade to the latest version of Zone Alarm....which I already have. So what gives? Why is it telling me I don't have the latest version? I am not faffing about with stopping zone alarm everytime I stop apache! Can I not use this version of uniform server then? If not, what one CAN I use? Such a shame, I have loved my ageing version of Uniform server on my old PC
  5. This still keeps happening intermittently and I could really do with some help as it is a complete pain in the backside as it screws up my CMS and I have to keep replacing the MYSQL data files from my backup!
  6. I am thinking of upgrading my dear old computer form XP (didn't much fancy Vista at the time of building!) to Windows 7. I have been using Uniform Server for a while now and as a web designer it is utterly essential to me! I am running 5.5a-Nano (old I know but I have had not reason to upgrade and made so many custom settings and what not I can't rememebr what I've done!) - will this run OK on Windows 7? Is there any reason why it wouldn't? If all is OK and I upgrade, will changes I made to the to the hosts file be erased? I have set up a subdomain (cms.localhost) and don't want to lose that.
  7. Just found this in the MYSQL error log - everytime it has crashed, it seems to be when trying to optimise the same table: thd: 0x11da3a8 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... 7C919AF2 ntdll.dll!RtlpWaitForCriticalSection() 7C901046 ntdll.dll!RtlEnterCriticalSection() Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 01227AB0=OPTIMIZE TABLE perch2_content_index thd->thread_id=89 thd->killed=NOT_KILLED The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130204 13:22:42 [Note] Plugin 'FEDERATED' is disabled. 130204 13:22:42 [Note] Plugin 'InnoDB' is disabled. 130204 13:22:42 [Note] Event Scheduler: Loaded 0 events 130204 13:22:42 [Note] C:/UniServer5_5a/UniServer/usr/local/mysql/bin/mysqld-opt.exe: ready for connections. Version: '5.1.41-community' socket: '' port: 3306 MySQL Community Server (GPL) 130204 14:17:46 [Note] C:/UniServer5_5a/UniServer/usr/local/mysql/bin/mysqld-opt.exe: Normal shutdown 130204 14:17:46 [Note] Event Scheduler: Purging the queue. 0 events 130204 14:17:46 [Note] C:/UniServer5_5a/UniServer/usr/local/mysql/bin/mysqld-opt.exe: Shutdown complete 130204 14:17:53 [Note] Plugin 'FEDERATED' is disabled. 130204 14:17:53 [Note] Plugin 'InnoDB' is disabled. 130204 14:17:54 [Note] Event Scheduler: Loaded 0 events 130204 14:17:54 [Note] C:/UniServer5_5a/UniServer/usr/local/mysql/bin/mysqld-opt.exe: ready for connections. Version: '5.1.41-community' socket: '' port: 3306 MySQL Community Server (GPL) 130204 17:22:48 [Warning] Warning: Optimize table got errno 5 on my_cms.perch2_content_index, retrying 130204 18:06:41 [Note] C:/UniServer5_5a/UniServer/usr/local/mysql/bin/mysqld-opt.exe: Normal shutdown 130204 18:06:42 [Note] Event Scheduler: Purging the queue. 0 events 130204 18:06:43 [Note] C:/UniServer5_5a/UniServer/usr/local/mysql/bin/mysqld-opt.exe: Shutdown complete
  8. Does no one have any suggestions? This is driving me mad!!
  9. I have been using uniform server for quite a wile now with no issues. I recently updated the version of a CMS I am testing on my Windows configuration and I keep getting this error: mysqld-opt.exe encountered a problem and needs to close. In the XP event viewer I see this: Faulting application mysqld-opt.exe, version, faulting module ntdll.dll, version 5.1.2600.6055, fault address 0x00019af2. There is nothing in the uniform server error logs The CMS developers say it's an issue with MYSQL and Windows and it has nothing to do with their CMS althoguh if that's the case I really don't understand why it has only recently started happening. It happens at the point where I click save in the CMS - in other words hwen it is communicating with the database. Does anyone have even the slightest clue as to what is going on? It seems to have adverse effects on the database as info seems to be lost (although I can see it in the CMS back office, it doesn't show on the website and the relevant info in the databse seems blank!) the only way I can restore the info is to restore the database from a previous back up. Please help!!
  10. babyewok

    Apache crashing?

    Oh please help! I'm still having this issue. The developers of the CMS say it is a php/windows/apache thing and happens when trying to run certain php scripts or large if statements. Is there anythign I can do? I tried upgrading php to 5.2.13 but no joy. I want to keep php at 5.2.9 or above as that is was my reseller hostign serevrs have and so I want to be able to test in a similar environment (albeit on windows rather tan linux). There must be a solution to this problem
  11. babyewok

    Apache crashing?

    This still happens every now and then - does anyone have any other solutions
  12. babyewok

    Apache crashing?

    Hmm, disabling the cache made no difference. If I turn on the debugging for eaccellerator I get this: - EACCELERATOR: Open for write failed for "/tmp/eaccelerator/d/5//eaccelerator-d5ddda828dd5c414cb678e03f5cf35bd": No such file or directory - EACCELERATOR cached: "C:\UniServer5_5a\UniServer\home\admin\www\index.php" for a whole load of different files
  • Create New...