DeveloperSide.NET Forums
December 16, 2019, 02:06:22 AM *
Welcome, Guest. Please login or register.

Login with username, password and session length
News:
 
  Home Help Search Login Register  
  Show Posts
Pages: 1 2 [3] 4 5 ... 216
31  DeveloperSide.NET / Web.Developer Server Suite Professional Edition,
Support Forum
/ Re: max_connections
on: April 26, 2010, 03:53:36 PM
http://dev.mysql.com/doc/refman/5.0/en/too-many-connections.html

You would edit my.ini and under the [mysqld] section, insert or modify line:
max_connections=100

100 is the default value.

Once this number is reached you get the mentioned message until that connection number goes down.

To handle the warning, you would have to code the php script to test for it and act appropriately (display a different message/page) (see user comments in the above link for examples).
32  DeveloperSide.NET / Web.Developer Server Suite Professional Edition,
Support Forum
/ Re: Howto: create SSL Sites and Virtual Hosts
on: April 04, 2010, 08:59:43 PM
To create a certificate signing request to be signed by one of the certificate authorities:

The first step is to use OpenSSL to create a private key and a certificate signing request. This will be done from the command line...
Run 'cmd.exe' to bring up the command line. Within, type in:
C:
cd \www\openssl\bin\
openssl req -new -nodes -keyout mydomain.key -out mydomain.csr
 
The last line will generate a file named mydomain.key [the private key] and mydomain.csr [the certificate signing request].
 
This is the info you will be prompted for...
 
Take note that the most important field is the 'Common Name' which is the exact web address of your domain that visitors see... If it's 'www.website.com', input it as that and not as 'website.com'.
Also take note that when asked for 'A challenge password' and 'An optional company name', just leave that blank... and press enter.
 
 
Quote
Generating a 1024 bit RSA private key
writing new private key to 'mydomain.key'
-----
You are about to be asked to enter information that will be incorporated into your certificate request.
...
-----
Country Name (2 letter code) [AU]:US
State or Province Name (full name) [Some-State]:Your State
Locality Name (eg, city) []:City Name
Organization Name (eg, company) [Internet Widgits Pty Ltd]:Company Name
Organizational Unit Name (eg, section) []:Company Name or Unit
Common Name (eg, YOUR name) []:www.website.com
Email Address []:admin@website.com
 
Please enter the following 'extra' attributes to be sent with your certificate request
A challenge password []:
An optional company name []:

Now you will need to send the contents of file C:\www\openssl\bin\mydomain.csr to whomever you are getting a certificate from. They will sign it and return the contents of what will become a file named mydomain.crt
 
Once you have received your certificate, we will need to place the key and crt files into the appropriate folders and update the configuration...
 
Enter folder C:\www\openssl\bin\ and move file mydomain.key out and into folder C:\www\Apache22\conf\
Ignore the two files that you have right now under sub-folders ssl.crt\ and ssl.key\ [the old Suite keys used by localhost -- keep them].
Place file mydomain.key into sub-folder ssl.key\
Create file mydomain.crt with the contents of the certificate you have received.
Place file mydomain.crt into sub-folder ssl.crt\
33  DeveloperSide.NET / Web.Developer Server Suite Professional Edition,
Support Forum
/ Re: Howto: create SSL Sites and Virtual Hosts
on: April 04, 2010, 08:31:00 PM
To create your own self-signed (unauthenticated) key-pair (public certificate, private key) for your host.domain.name, follow the instructions in this Guide:
http://www.devside.net/articles/ssl-key-pair
34  DeveloperSide.NET / Web.Developer Server Suite Professional Edition,
Support Forum
/ Howto: create SSL Sites and Virtual Hosts
on: April 04, 2010, 08:17:48 PM
Under Apache, an SSL site is a separate site from the regular (non-ssl) site and requires its own Virtual Host configuration (but it can share the DocumentRoot with the regular site).

To set up an SSL site (under our Suite), you'll need to create a "static" site container with a "static" virtual host configuration, and instead of using port 80 (http), you will use port 443 (https), plus a few extra directives in the VirtualHost block to set up the certificate handling.

Before we begin, there are two issues you have to understand:
A. SSL Virtual Hosts require you to have a dedicated IP address. This IP address cannot be shared with other SSL Virtual Hosts... With 1 IP address, you can run many non-ssl sites and (in addition) exactly 1 SSL site. Two IPs get you two SSL sites. And so on.

B. While you can use our "localhost" ssl certificates, or even create your own "self-signed" certificates for your host.domain.name, the browser will display a warning that you are entering a site with self-signed, and/or mismatched certificates. Your only solution to fix this is to purchase valid certificates.


1. Edit C:\www\Apache22\conf\extra\httpd-ssl.conf
 
Comment out line:
#<VirtualHost _default_:443>
 
And insert right after it:
<VirtualHost 127.0.0.1:443>
 
This way the "localhost" SSL VH will not pick up all the requests going to this system.
 
2. Create C:\www\Apache22\conf\extra\vhosts\_static\mydomain.com-ssl.conf

We will create an ssl Virtual Host for folder/site 'C:/www/vhosts/_static/mydomain.com' and bind it to the LAN IP of 192.168.1.100
 
Code:
<VirtualHost 192.168.1.100:443>
 
 DocumentRoot "C:/www/vhosts/_static/mydomain.com"
 ServerName mydomain.com:443
 ServerAlias www.mydomain.com:443
 
 ErrorLog logs/mydomain.com/error_ssl.log
 TransferLog logs/mydomain.com/access_ssl.log
 
 SSLEngine on
 SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
 SSLCertificateFile conf/ssl.crt/server.crt
 SSLCertificateKeyFile conf/ssl.key/server.key
 
 <Directory "C:\www\vhosts\_static\mydomain.com">
  Options All
  AllowOverride All
  order allow,deny
  Allow from all
 </Directory>
 
 <FilesMatch "\.(cgi|shtml|phtml|php)$">
     SSLOptions +StdEnvVars
 </FilesMatch>
 <Directory "C:/www/vhosts/_static/mydomain.com/cgi-bin">
     SSLOptions +StdEnvVars
 </Directory>
 
 BrowserMatch ".*MSIE.*" \
          nokeepalive ssl-unclean-shutdown \
          downgrade-1.0 force-response-1.0
 
</VirtualHost>

3.
a) Replace the 192.168.1.100 above with your system's public IP address, the LAN IP address (access will only work on the LAN), or any IP address the system has other than 127.0.0.1 (the localhost SSL VH is taking this one).
b) Make sure folder C:\www\Apache22\logs\mydomain.com\ exists. Apache will not create this log folder for you and will throw an error on startup.
c) Make sure mydomain.com and www.mydomain.com resolve to the public IP address of your router or directly to 192.168.1.100 (or the IP you are using).
 
4. Restart Apache.
 
Note that when you go to the https:// URLs, since you are using the default SSL certificates that come with the Suite, you'll get a browser warning about having bad certs.
This is because inside the VH block above, we are referencing ssl certs:  SSLCertificateFile conf/ssl.crt/server.crt and SSLCertificateKeyFile conf/ssl.key/server.key which are just test certs that come with the Suite for localhost and are self-signed.
35  DeveloperSide.NET / Web.Developer Server Suite Community Edition,
Public Support Forum
/ Re: ModSecurity Settings
on: March 30, 2010, 04:19:02 PM
You should edit file : C:\www\Apache22\conf\extra\suite-global\suite-mod_security2.conf

This file "includes" all the mod_sec rule files into the config.

Comment out the robots file in the above.
36  DeveloperSide.NET / Web.Developer Server Suite Community Edition,
Public Support Forum
/ Re: ModSecurity Settings
on: March 30, 2010, 01:12:34 AM
Quote
1.Were would i go to enable this?

C:\www\Apache22\conf\extra\mod_security2\rules\modsecurity_crs_10_config.conf
SecRuleEngine DetectionOnly

To: On

Quote
2.Will it affect any crawling for google/yahoo ect, by me enabling this without changing the rules?

Maybe. Depends on what's crawled and what rules are triggered.
37  DeveloperSide.NET / Web.Developer Server Suite Community Edition,
Public Support Forum
/ Re: ModSecurity Settings
on: March 30, 2010, 12:30:07 AM
The problem w/ mod_sec is that the general ruleset that comes with it will catch allot of false positives ... and if active, will prevent your site from working for visitors.

To use mod_sec properly you have to start from scratch and enter our own rules, or test the general rules and remove the ones causing false positives.

So you can turn it on, but do go through all your urls, file uploading, posting, etc and see what breaks. Then check the error log to see which rules came up and disable them.
38  DeveloperSide.NET / Web.Developer Server Suite Professional Edition,
Support Forum
/ Re: Updating Components of the Suite...
on: March 02, 2010, 05:34:13 PM
Quote
> I simply cannot rename the old Apache folder, it won't let me.

That would usually mean one of two things:
1. That the Apache2.2 Service has not been stopped and is still running.
2. You have a folder open under this path (in windows explorer), or a file open under this path in some editor.
 
Make sure that Apache2.2 is stopped, and check your open windows and files. If you still have trouble renaming this folder, set the Apache2.2 service to "manual" (or "demand") startup and reboot. Try again.
39  DeveloperSide.NET / Web.Developer Server Suite Community Edition,
Public Support Forum
/ Re: Strange errors in access.log
on: February 21, 2010, 05:11:03 PM
I'm not sure what would happen with 0.0.0.0. That usually specifies "all interfaces"/IPs.
40  DeveloperSide.NET / Web.Developer Server Suite Community Edition,
Public Support Forum
/ Re: Strange errors in access.log
on: February 21, 2010, 03:18:27 PM
Example: edit the Windows hosts file, add...
127.0.0.1 www.google.com

Save file. Go to the above URL. You should see it in your logs.
41  DeveloperSide.NET / Web.Developer Server Suite Community Edition,
Public Support Forum
/ Re: Strange errors in access.log
on: February 21, 2010, 02:50:35 PM
The Hosts file will cause the browser to resolve the specified domain names to the IP address of your system (127.0.0.1)...

If you are visiting a site and it has links (to ga.js, to ad servers, etc...) in it's source code that point to hosts that you are "127.0.0.1" in the Windows hosts file, those links will translate to access attempts to your local system / apache.
42  DeveloperSide.NET / Web.Developer Server Suite Community Edition,
Public Support Forum
/ Re: Strange errors in access.log
on: February 20, 2010, 10:22:48 PM
ga.js is the Google Analytics tracking script.

Quote
I wonder if it's because I blocked a load of adware via the HOSTS file as:

Could be... Anything of the form blocked-domain.tld\... in any webpage or ad display would go to 127.0.0.1
43  DeveloperSide.NET / Web.Developer Server Suite Community Edition,
Public Support Forum
/ Re: how to unblock google bot?! how to change access rules for server
on: February 10, 2010, 05:07:00 PM
You should try to access your-domain\robots.txt URL in your browser to see what you get. It might not even exist. If it does, it can block bots, but only directly, and not via any type of a metric (ex: by # of accesses), so take a look in it.

The only other configuration I can think of that could cause a problem is with mod_security rulesets but it's unlikely.
44  DeveloperSide.NET / Web.Developer Server Suite Community Edition,
Public Support Forum
/ Re: phpmyadmin accessable from external website address.
on: January 27, 2010, 10:24:34 PM
Try under C:\www\webapps\awstats\wwwroot\cgi-bin\

If that does not work, edit C:\www\Apache22\conf\extra\suite-global\suite-awstats.conf
And change the two instances of...

Order allow,deny
Allow from all

To

Order deny,allow
Deny from all
Allow from 127.0.0.1

Restart Apache.
45  DeveloperSide.NET / Web.Developer Server Suite Community Edition,
Public Support Forum
/ Re: phpmyadmin accessable from external website address.
on: January 27, 2010, 09:28:37 PM
1.
Create C:\www\webapps\phpmyadmin\.htaccess
(You might need to 1st create this file as htaccess.txt and rename it to .htaccess within notepad as Windows won't let you directly create a file that starts with a period.)
 
Within it place:
Deny from all
allow from 127.0.0.1

This will prevent access to phpmyadmin from evryone but the local system.

Quote
Will there be any problems later on by doing this? like installing wordpress?

No.

2.
Try creating the same .htaccess file under C:\www\webapps\awstats\, I'm about 95% sure it will work here, if not then should work under a deeper folder.
Pages: 1 2 [3] 4 5 ... 216
Powered by MySQL Powered by PHP Powered by SMF 1.1.9 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!