suse 9.0 extra vhosts lassen sich nicht anlegen :(

[blnsnoopy26]

Hi,

Also ich habe jetzt stunden alles Probiert, aber nichts scheint zu funktionieren.

Zu meinem Problem.... Ich bin jetzt auf Suse 9.0 umgestiegen und wollte wie bei suse 8.1 meine Custon vhots wieder anlegen. Wenn ich den vhost anlege und Apache restarte dann verläuft alles normal - keine error Meldungen, aber sobald ich dann auf die seite zugreifen möchte, dann bekomme ich Zugriff verweigert :(

Mein vhost habe ich so konfiguriert

Code: Select all

<VirtualHost 217.160.xxx.x:80>
  ServerName meinedomain.de
  ServerAlias www.phpadmin.meinedomain.de phpadmin.meinedomain.de
  DocumentRoot /home/htdocs/web1/sqladmin
  SuexecUserGroup web1 ftponly
  ScriptAlias /cgi-bin/ /srv/www/htdocs/web1/html/cgi-bin/
  php_admin_value upload_tmp_dir /srv/www/htdocs/web1/phptmp/
</VirtualHost>

der ordner und die dateien darin haben rechte web1:ftponly
in den logs taucht folgendes auf:

Code: Select all

[Sun Jul 25 00:54:16 2004] [error] [client 217.231.xxx.xxx] client denied by server configuration: /home/htdocs/web1/sqladmin/
[Sun Jul 25 00:54:17 2004] [error] [client 217.231.xxx.xxx] client denied by server configuration: /home/htdocs/web1/sqladmin/

Die Serverkonfiguration ist Standard auslieferungszustand (Suse 9.0/Apache 2) Kann mir einer sagen, warum das nicht geht? Bei Suse 8.1 habe ich einfach ein Ordner und ein vhost angelegt und es funktionierte auf anhieb ohne irgendwelche rechte problme.

Auf dem Server läuft noch confixx 3.0.0
Wenn ich den selben vhost in /srv/www/htdocs anlege, dann geht es ohne Probleme, aber auf der Partition sind nur 512 MB frei also kein Platz für meine Webs und Standard Konfiguration wo meine webs liegen ist /home/htdocs.

Das verwunderliche ist das meine webs die ich via confixx anlege alle ohne weiteres funktionieren nur halt nicht, wenn ich via mkdir ein Ordner anlege und die rechte setze und den vhost in meine httpd.conf eintrage.

Ich habe am sys soweit noch nix geändert sondern kämpfe die ganze zeit, damit meine custom vhosts funktionieren und ich hoffe, dass mir jemand helfen kann, denn ich weiss einfach nicht mehr weiter.


Falls noch jemand wissen möchte wie alles gemounted ist hier die infos:

fdisk -l

Code: Select all

Disk /dev/hda: 41.1 GB, 41174138880 bytes
255 heads, 63 sectors/track, 5005 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1             1        66    530113+  83  Linux
/dev/hda2            67       321   2048287+  82  Linux swap
/dev/hda4           322      5005  37624230    5  Extended
/dev/hda5           322       959   5124703+  83  Linux
/dev/hda6           960      1597   5124703+  83  Linux
/dev/hda7          1598      5005  27374728+  83  Linux

mount

Code: Select all

/dev/hda1 on / type ext3 (rw)
proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/hda5 on /usr type xfs (rw)
/dev/hda6 on /var type xfs (rw,usrquota)
/dev/hda7 on /home type xfs (rw,usrquota)
tmpfs on /tmp type tmpfs (rw)
tmpfs on /dev/shm type tmpfs (rw,size=20M)

[ag]

Hey

Du kannst nur Document Roots in den Verzeichnis anlegen welches als Server Root in der Main Server Konfiguration , in der httpd.conf drinsteht.
Du hast einmal /home/htdocs (dein Dokument Root) und einmal /srv/www/htdocs (der der automatisch durch Confixx angelegt wird)
Das könnte der Fehler sein.

By AG

[blnsnoopy26]

Hi,

Nach langen suchen nochmals probieren habe ich es hinbekommen.
Da lag eine datei mod_userdir.conf im Verzeichnis die habe ich abgeändert und dann ging es ohne Probleme.

Aber habe noch ein anderes Problem und zwar lässt sich das SSL nicht aktivieren und ich weiss nicht warum :(

hier meine configs:

ssl.conf

Code: Select all

#
# This is the Apache server configuration file providing SSL support.
# It contains the configuration directives to instruct the server how to
# serve pages over an https connection. For detailing information about these
# directives see <URL:http://httpd.apache.org/docs-2.0/mod/mod_ssl.html>
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned.
#

#
# Pseudo Random Number Generator (PRNG):
# Configure one or more sources to seed the PRNG of the SSL library.
# The seed data should be of good random quality.
# WARNING! On some platforms /dev/random blocks if not enough entropy
# is available. This means you then cannot use the /dev/random device
# because it would lead to very long connection times (as long as
# it requires to make more entropy available). But usually those
# platforms additionally provide a /dev/urandom device which doesn't
# block. So, if available, use this one instead. Read the mod_ssl User
# Manual for more details.
#
# Note: This must come before the <IfDefine SSL> container to support
#       starting without SSL on platforms with no /dev/random equivalent
#       but a statically compiled-in mod_ssl.
#
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
#SSLRandomSeed startup file:/dev/random  512
#SSLRandomSeed startup file:/dev/urandom 512
#SSLRandomSeed connect file:/dev/random  512
#SSLRandomSeed connect file:/dev/urandom 512

<IfDefine SSL>
#
# When we also provide SSL we have to listen to the
# standard HTTP port (see above) and to the HTTPS port
#
# Note: Configurations that use IPv6 but not IPv4-mapped addresses need two
#       Listen directives: "Listen [::]:443" and "Listen 0.0.0.0:443"
#

Listen 443
##
##  SSL Global Context
##
##  All SSL configuration in this context applies both to
##  the main server and all SSL-enabled virtual hosts.
##

#
#   Some MIME-types for downloading Certificates and CRLs
#
AddType application/x-x509-ca-cert .crt
AddType application/x-pkcs7-crl    .crl

#   Pass Phrase Dialog:
#   Configure the pass phrase gathering process.
#   The filtering dialog program (`builtin' is a internal
#   terminal dialog) has to provide the pass phrase on stdout.
SSLPassPhraseDialog  builtin

#   Inter-Process Session Cache:
#   Configure the SSL Session Cache: First the mechanism
#   to use and second the expiring timeout (in seconds).
#SSLSessionCache        none
#SSLSessionCache        shmht:/home/logs/ssl_scache(512000)
#SSLSessionCache        shmcb:/home/logs/ssl_scache(512000)
SSLSessionCache         dbm:/home/logs/ssl_scache
SSLSessionCacheTimeout  300

#   Semaphore:
#   Configure the path to the mutual exclusion semaphore the
#   SSL engine uses internally for inter-process synchronization.
SSLMutex  file:/home/logs/ssl_mutex

##
## SSL Virtual Host Context
##
NameVirtualHost 217.160.xxx.xxx:443
<VirtualHost 217.160.xxx.xxx:443>
  ServerName confixx.pxxxxx.pureserver.info
  #User confixx
  #Group users
  DocumentRoot /srv/www/confixx/html
  php_admin_value safe_mode_exec_dir /srv/www/confixx/bin
  php_admin_value upload_tmp_dir /srv/www/confixx/tmp
  php_admin_value include_path ".:/srv/www/confixx/html/include:/home/www/confixx/html"
  ScriptAlias /cgi-bin/ /srv/www/confixx/html/cgi-bin/
  CustomLog /var/log/apache2/p15103699.pureserver.info_access.log "%h %l %u %t "%r" %s %b "%{Referer}i" "%{User-agent}i""

#   General setup for the virtual host


#   SSL Engine Switch:
#   Enable/Disable SSL for this virtual host.
SSLEngine on

#   SSL Cipher Suite:
#   List the ciphers that the client is permitted to negotiate.
#   See the mod_ssl documentation for a complete list.
SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL

#   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.)
SSLCertificateFile /etc/apache2/ssl.crt/server.crt
#SSLCertificateFile /etc/apache2/ssl.crt/server-dsa.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.)
SSLCertificateKeyFile /etc/apache2/ssl.key/server.key
#SSLCertificateKeyFile /etc/apache2/ssl.key/server-dsa.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 convinience.
#SSLCertificateChainFile /etc/apache2/ssl.crt/ca.crt

#   Certificate Authority (CA):
#   Set the CA certificate verification path where to find CA
#   certificates for client authentication or alternatively one
#   huge file containing all of them (file must be PEM encoded)
#   Note: Inside SSLCACertificatePath you need hash symlinks
#         to point to the certificate files. Use the provided
#         Makefile to update the hash symlinks after changes.
#SSLCACertificatePath /etc/apache2/ssl.crt
#SSLCACertificateFile /etc/apache2/ssl.crt/ca-bundle.crt

#   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)
#   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 /etc/apache2/ssl.crl
#SSLCARevocationFile /etc/apache2/ssl.crl/ca-bundle.crl

#   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

#   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>

#   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 CompatEnvVars:
#     This exports obsolete environment variables for backward compatibility
#     to Apache-SSL 1.x, mod_ssl 2.0.x, Sioux 1.0 and Stronghold 2.x. Use this
#     to provide compatibility to existing CGI scripts.
#   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 +CompatEnvVars +StrictRequire
<Files ~ ".(cgi|shtml|phtml|php3?)$">
    SSLOptions +StdEnvVars
</Files>
<Directory "/home/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 send or allowed to 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.
SetEnvIf User-Agent ".*MSIE.*" 
         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 /home/logs/ssl_request_log 
          "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x "%r" %b"

</VirtualHost>

</IfDefine>

listen.conf

Code: Select all

# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports. See also the <VirtualHost> directive.
#
# http://httpd.apache.org/docs-2.0/mod/mpm_common.html#listen
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
#
# When we also provide SSL we have to listen to the
# standard HTTP port (see above) and to the HTTPS port
#
# Note: Configurations that use IPv6 but not IPv4-mapped addresses need two
#       Listen directives: "Listen [::]:443" and "Listen 0.0.0.0:443"
#
#Listen 12.34.56.78:80
#Listen 80
#Listen 443

Listen 80


<IfDefine SSL>
    <IfDefine !NOSSL>
	<IfModule mod_ssl.c>

	    Listen 443

	</IfModule>
    </IfDefine>
</IfDefine>


# Use name-based virtual hosting
#
# - on a specified address / port:
#
#NameVirtualHost 12.34.56.78:80
#
# - name-based virtual hosting:
#
#NameVirtualHost *:80
#
# - on all addresses and ports. This is your best bet when you are on
#   dynamically assigned IP addresses:
#
#NameVirtualHost *

confixx_mhost.conf

Code: Select all

## CONFIXX


<Directory "/srv/www/confixx/html">

  AllowOverride all

  <IfModule mod_access.c>
        Allow from all
  </IfModule>

  <IfModule mod_rewrite.c>

    RewriteEngine On
    Options +FollowSymlinks

    RewriteRule ^reseller/res[0-9]+/(.*)$ reseller/$1 [L]

    RewriteRule ^user/[a-zA-Z][-a-zA-Z0-9_]{0,4}[0-9]+/(.*)$ user/$1 [L]

    RewriteRule ^ftplogin/[a-zA-Z][-a-zA-Z0-9_]{0,4}[0-9]+/(.*)$ ftplogin/$1 [L]
    RewriteRule ^ftplogin/[a-zA-Z][-a-zA-Z0-9_]{0,4}[0-9]+f[0-9]+/(.*)$ ftplogin/$1 [L]

    RewriteRule ^poplogin/[a-zA-Z][-a-zA-Z0-9_]{0,4}[0-9]+p[0-9]+/(.*)$ poplogin/$1 [L]

  </IfModule>

  AddDefaultCharset off

</Directory>

NameVirtualHost 217.160.xxx.xxx:80

<VirtualHost 217.160.xxx.xxx:80>

        ServerName confixx.pxxxxx.pureserver.info

        #User confixx
        #Group confixx
        DocumentRoot /srv/www/confixx/html
        Options FollowSymLinks

        php_admin_flag safe_mode Off
        php_admin_flag file_uploads On
        php_admin_flag track_vars On
        php_admin_flag magic_quotes_runtime Off
        php_admin_flag magic_quotes_gpc Off
        php_admin_value upload_tmp_dir /srv/www/confixx/tmp
        php_admin_value include_path ".:/srv/www/confixx/html/include:/srv/www/confixx/html"
        php_admin_value default_charset none
        php_admin_value open_basedir /srv/www/confixx

		php_admin_value session.cookie_path /
		php_admin_value session.auto_start 0
		php_admin_value session.gc_maxlifetime 1800
		php_admin_value session.use_cookies 1
		php_admin_value session.cookie_lifetime 0
		php_admin_value session.cookie_secure Off
		php_admin_value session.use_trans_sid 0

        ScriptAlias /cgi-bin/ /srv/www/confixx/html/cgi-bin/

	<IfModule mod_dir.c>
	    DirectoryIndex index.html index.htm index.shtml index.cgi index.php
	</IfModule>

        CustomLog /var/log/apache2/pxxxxx.pureserver.info_access.log "%h %l %u %t "%r" %s %b "%{Referer}i" "%{User-agent}i""
        ErrorLog /var/log/apache2/pxxxx.pureserver.info_error.log

</VirtualHost>

#Include /etc/apache2/confixx_vhost.conf
# ^- Dieser Eintrag sollte unbedingt am Ende der Datei bleiben
## /CONFIXX

Module werden auch alle geladen, daher verstehe ich das nicht :(
Ich hoffe das mir da einer helfen kann.