eigener server

cookie

also ich habe von einem freund einen alten pc abgestaubt und jetzt habe ich mir gedacht das ist zwar ne uralte kiste mit 800 megaherz aber für einen server für php seiten müsste es doch eigentlich reichen (erste frage: tut es das? ) und wenn ich ihn als server bentutzen will welches betriebssystem wäre da angebracht? jawohl bestimmt net windows sondern eher linux aber welches? wohl eher auch da kein suse linux... und ist das überhaupt so einfach möglich wie ich mir das vorstelle?
mfg cookkie

Andy

800 mhz? cool den kannst du mir schenken (habe nur einen 300er als ersatz)

zu deinem thema:

das kannst du gleich vergessen! nicht etwa wegen deines rechners, sondern wegen deiner anbindung ans internet.
da kommst du nichtmal mit dsl 6000 arg weit.

außerdem: ist das von deinem internetabieter, provider, überhaupt erlaubt?

gelöschter User

ich würd sagen es reicht wenn er es nur im lan benutzen will

Gruß crAzywuLf

cookie

richtig ist mir erstmal egal wo ich ihn benutze... aber ich hätte gerne einen server ob das dann ein fileserver oder ein scriptserver wird ist mir egal... aber trozdem würde ich gerne wissen welches linux sich dafür eignet...
mfg cookie

GreenRover

naja meienr meinung nach rennt da debian am besten. Aber mit ein bischen RAM, rennt das selbst mit WINFOOFS.

Für anfänger tuht es auch ein Suse Server.
Also ich habe das spielchen auch shcon mit einem P3@800Mhz und 512MB ram gemacht.

Unter debian, ist bei eine Ansturm von 1000 und mehr anfragen in der Minute doch mehr die NEtzwerkkarte dicht gewesen, als der Server in die kniee gegangen ist :-p

cookie

also ist es auch mit ganz normalem suse linux (ich glaube 10.0 ist das aktuelle ) möglich einen server zu machen? weil das suse habe ich auch auf dem rechner von dem ich gerade schreibe installiert da kenne ich mich zwar auch net aus aber ich denke das wäre noch eher möglich da es auch grafisch usw ist... aber muss ich dann irgendwie noch was in linux an apache rumschrauben? das die scripte per internet erreichbar sind?

GreenRover

PS, auch debian hat eine gui. Aber es geht auch mittels Suse, das sit bane wie pflaume.

Ist halt bloß ein unterschied bei dne packet zusammen setzungen.

Der Apache läuft so wenn du ihn installiert hast, aber änderungen sind da teilweise schon sinvoll.

Und eine GUI brauch wesentlich mehr Leistung als ein Webserver.

cookie

kannst du mir vielleicht mal sagen wie das genau funktioniert mit dem apache das man die scripte dann auch aus dem internet benutzen kann? weil wenn ich nicht weis wie das geht dann bringt mir das alles nichts...
oder kennst du ein tutorial oder sowas?
mfg cookie

GreenRover

naja du installierst dne apachen per yast.

packst dann deine Datein noch in /srv/www/htdocs oder /srv/www/htdocs/html ich weis nicht gneau wie es bei suse ist.

Und schon geht es.
Falls du PHP benötigt haust du es auch noch mittels Yast rauf und das meiste konfiguriert denn suse von alleine.

PS, habe nur Tutorials, wo man sich dann apache und alels selbst konpiliert und baut, das dürfte aber viel viel zu weit führen.

cookie

ok vielen dank erstmal wenn ich linux installliert habe und nicht weiter weis melde ich mich hier nochmal

GreenRover

kk

cookie

so jetzt stehe ich auch wieder hier... und es kommt immer sobald ich auf meinen apache connecten will (egal ob von server aus oder von außen):

Code

Forbidden


You don't have permission to access / on this server.


Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.
Apache/2.0.54 (Linux/SUSE) Server at 192.168.1.16 Port 80

httpd.conf:

Code

#
# /etc/apache2/httpd.conf 
#
# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs-2.0/> for detailed information about
# the directives.


# Based upon the default apache configuration file that ships with apache,
# which is based upon the NCSA server configuration files originally by Rob
# McCool. This file was knocked together by Peter Poeml <poeml+apache@suse.de>.


# If possible, avoid changes to this file. It does mainly contain Include
# statements and global settings that can/should be overridden in the
# configuration of your virtual hosts.




# Overview of include files, chronologically:
#
# httpd.conf
#  | 
#  |-- uid.conf  . . . . . . . . . . . . . .  UserID/GroupID to run under
#  |-- server-tuning.conf  . . . . . . . . .  sizing of the server (how many processes to start, ...)
#  |-- sysconfig.d/loadmodule.conf . . . . .  [*] load these modules
#  |-- listen.conf . . . . . . . . . . . . .  IP adresses / ports to listen on
#  |-- mod_log_config.conf . . . . . . . . .  define logging formats
#  |-- sysconfig.d/global.conf . . . . . . .  [*] server-wide general settings
#  |-- mod_status.conf . . . . . . . . . . .  restrict access to mod_status (server monitoring)
#  |-- mod_info.conf . . . . . . . . . . . .  restrict access to mod_info
#  |-- mod_usertrack.conf  . . . . . . . . .  defaults for cookie-based user tracking
#  |-- mod_autoindex-defaults.conf . . . . .  defaults for displaying of server-generated directory listings
#  |-- mod_mime-defaults.conf  . . . . . . .  defaults for mod_mime configuration
#  |-- errors.conf . . . . . . . . . . . . .  customize error responses
#  |-- ssl-global.conf . . . . . . . . . . .  SSL conf that applies to default server _and all_ virtual hosts
#  |
#  |-- default-server.conf . . . . . . . . .  set up the default server that replies to non-virtual-host requests
#  |    |--mod_userdir.conf  . . . . . . . .  enable UserDir (if mod_userdir is loaded)
#  |    `--conf.d/apache2-manual?conf  . . .  add the docs ('?' = if installed)
#  |
#  |-- sysconfig.d/include.conf  . . . . . .  [*] your include files 
#  |                                             (for each file to be included here, put its name 
#  |                                              into APACHE_INCLUDE_* in /etc/sysconfig/apache2)
#  |
#  `-- vhosts.d/ . . . . . . . . . . . . . .  for each virtual host, place one file here
#       `-- *.conf . . . . . . . . . . . . .     (*.conf is automatically included)
#
#
# Files marked [*] are created from sysconfig upon server restart: instead of
# these files, you edit /etc/sysconfig/apache2






#  Filesystem layout:
#
# /etc/apache2/
#  |-- conf.d/
#  |   |-- apache2-manual.conf . . . . . . .  conf that comes with apache2-doc
#  |   |-- mod_php4.conf . . . . . . . . . .  (example) conf that comes with apache2-mod_php4
#  |   `-- ... . . . . . . . . . . . . . . .  other configuration added by packages
#  |-- default-server.conf
#  |-- errors.conf
#  |-- httpd.conf  . . . . . . . . . . . . .  top level configuration file
#  |-- listen.conf
#  |-- magic
#  |-- mime.types -> ../mime.types
#  |-- mod_autoindex-defaults.conf
#  |-- mod_info.conf
#  |-- mod_log_config.conf
#  |-- mod_mime-defaults.conf
#  |-- mod_perl-startup.pl
#  |-- mod_status.conf
#  |-- mod_userdir.conf
#  |-- mod_usertrack.conf
#  |-- server-tuning.conf
#  |-- ssl-global.conf
#  |-- ssl.crl/  . . . . . . . . . . . . . .  PEM-encoded X.509 Certificate Revocation Lists (CRL)
#  |-- ssl.crt/  . . . . . . . . . . . . . .  PEM-encoded X.509 Certificates
#  |-- ssl.csr/  . . . . . . . . . . . . . .  PEM-encoded X.509 Certificate Signing Requests
#  |-- ssl.key/  . . . . . . . . . . . . . .  PEM-encoded RSA Private Keys
#  |-- ssl.prm/  . . . . . . . . . . . . . .  public DSA Parameter Files
#  |-- sysconfig.d/  . . . . . . . . . . . .  files that are created from /etc/sysconfig/apache2
#  |   |-- global.conf
#  |   |-- include.conf
#  |   `-- loadmodule.conf
#  |-- uid.conf
#  `-- vhosts.d/ . . . . . . . . . . . . . .  put your virtual host configuration (*.conf) here
#      |-- vhost-ssl.template
#      `-- vhost.template






### Global Environment ######################################################
#
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests.


# run under this user/group id
Include /etc/apache2/uid.conf


# - how many server processes to start (server pool regulation)
# - usage of KeepAlive
Include /etc/apache2/server-tuning.conf


# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
ErrorLog /var/log/apache2/error_log


# generated from APACHE_MODULES in /etc/sysconfig/apache2
Include /etc/apache2/sysconfig.d/loadmodule.conf


# IP addresses / ports to listen on
Include /etc/apache2/listen.conf


# predefined logging formats
Include /etc/apache2/mod_log_config.conf


# generated from global settings in /etc/sysconfig/apache2
Include /etc/apache2/sysconfig.d/global.conf


# optional mod_status, mod_info
Include /etc/apache2/mod_status.conf
Include /etc/apache2/mod_info.conf


# optional cookie-based user tracking
# read the documentation before using it!!
Include /etc/apache2/mod_usertrack.conf


# configuration of server-generated directory listings
Include /etc/apache2/mod_autoindex-defaults.conf


# associate MIME types with filename extensions
TypesConfig /etc/apache2/mime.types
DefaultType text/plain
Include /etc/apache2/mod_mime-defaults.conf


# set up (customizable) error responses
Include /etc/apache2/errors.conf


# global (server-wide) SSL configuration, that is not specific to 
# any virtual host
Include /etc/apache2/ssl-global.conf


# forbid access to the entire filesystem by default
<Directory />
    Options None
    AllowOverride None
    Order deny,allow
    Deny from all
</Directory>


# use .htaccess files for overriding,
AccessFileName .htaccess
# and never show them
<Files ~ "^\.ht">
    Order allow,deny
    Deny from all
</Files>


# List of resources to look for when the client requests a directory
DirectoryIndex index.html index.html.var


### 'Main' server configuration #############################################
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition.  These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#
Include /etc/apache2/default-server.conf




# Another way to include your own files
#
# The file below is generated from /etc/sysconfig/apache2,
# include arbitrary files as named in APACHE_CONF_INCLUDE_FILES and
# APACHE_CONF_INCLUDE_DIRS
Include /etc/apache2/sysconfig.d/include.conf




### Virtual server configuration ############################################
#
# VirtualHost: If you want to maintain multiple domains/hostnames on your
# machine you can setup VirtualHost containers for them. Most configurations
# use only name-based virtual hosts so the server doesn't need to worry about
# IP addresses. This is indicated by the asterisks in the directives below.
#
# Please see the documentation at
# <URL:http://httpd.apache.org/docs-2.0/vhosts/>
# for further details before you try to setup virtual hosts.
#
# You may use the command line option '-S' to verify your virtual host
# configuration.
#
Include /etc/apache2/vhosts.d/*.conf




# Note: instead of adding your own configuration here, consider 
#       adding it in your own file (/etc/apache2/httpd.conf.local)
#       putting its name into APACHE_CONF_INCLUDE_FILES in 
#       /etc/sysconfig/apache2 -- this will make system updates 
#       easier :)

Alles anzeigen

meine apache error_log schaut so aus:

Code

[Fri Feb 10 14:55:03 2006] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Fri Feb 10 14:55:03 2006] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec2)
[Fri Feb 10 14:55:10 2006] [notice] Apache/2.0.54 (Linux/SUSE) configured -- resuming normal operations
[Fri Feb 10 14:57:17 2006] [error] [client 192.168.1.10] File does not exist: /srv/www/htdocs/kw
[Fri Feb 10 14:57:21 2006] [error] [client 192.168.1.10] File does not exist: /srv/www/htdocs/lan
[Fri Feb 10 15:09:48 2006] [notice] caught SIGTERM, shutting down
[Tue Mar 28 16:39:39 2006] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Tue Mar 28 16:39:39 2006] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec2)
[Tue Mar 28 16:39:44 2006] [notice] Apache/2.0.54 (Linux/SUSE) configured -- resuming normal operations
[Tue Mar 28 16:41:33 2006] [notice] caught SIGTERM, shutting down
[Wed Mar 29 11:48:01 2006] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Wed Mar 29 11:48:01 2006] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec2)
[Wed Mar 29 11:48:14 2006] [notice] Apache/2.0.54 (Linux/SUSE) configured -- resuming normal operations
[Wed Mar 29 12:18:12 2006] [error] [client 127.0.0.1] File does not exist: /srv/www/htdocs/kw
[Wed Mar 29 12:18:27 2006] [error] [client 127.0.0.1] File does not exist: /srv/www/htdocs/kw
[Wed Mar 29 12:19:40 2006] [error] [client 127.0.0.1] File does not exist: /srv/www/htdocs/phpmyadmin
[Wed Mar 29 13:15:39 2006] [notice] caught SIGTERM, shutting down
[Wed Mar 29 17:31:11 2006] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Wed Mar 29 17:31:11 2006] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec2)
[Wed Mar 29 17:31:20 2006] [notice] Apache/2.0.54 (Linux/SUSE) configured -- resuming normal operations
[Wed Mar 29 18:48:07 2006] [notice] caught SIGTERM, shutting down
[Thu Mar 30 11:48:17 2006] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Thu Mar 30 11:48:18 2006] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec2)
[Thu Mar 30 11:48:28 2006] [notice] Apache/2.0.54 (Linux/SUSE) configured -- resuming normal operations
[Thu Mar 30 12:58:31 2006] [notice] caught SIGTERM, shutting down
[Thu Mar 30 13:09:19 2006] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Thu Mar 30 13:09:19 2006] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec2)
[Thu Mar 30 13:09:22 2006] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Thu Mar 30 13:09:22 2006] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec2)
[Thu Mar 30 13:09:23 2006] [notice] Apache/2.0.54 (Linux/SUSE) configured -- resuming normal operations
[Thu Mar 30 13:11:19 2006] [notice] caught SIGTERM, shutting down
[Thu Mar 30 13:13:40 2006] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Thu Mar 30 13:13:41 2006] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec2)
[Thu Mar 30 13:13:53 2006] [notice] Apache/2.0.54 (Linux/SUSE) configured -- resuming normal operations
[Thu Mar 30 14:00:37 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /index.html denied
[Thu Mar 30 14:00:37 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /index.html.var denied
[Thu Mar 30 14:00:37 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /index.php denied
[Thu Mar 30 14:00:37 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /index.php3 denied
[Thu Mar 30 14:00:37 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /index.php4 denied
[Thu Mar 30 14:00:37 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /favicon.ico denied
[Thu Mar 30 14:00:41 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /favicon.ico denied
[Thu Mar 30 14:00:43 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /index.html denied
[Thu Mar 30 14:00:43 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /index.html.var denied
[Thu Mar 30 14:00:43 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /index.php denied
[Thu Mar 30 14:00:43 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /index.php3 denied
[Thu Mar 30 14:00:43 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /index.php4 denied
[Thu Mar 30 14:00:56 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /kwn/index.php denied
[Thu Mar 30 15:20:48 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /index.html denied
[Thu Mar 30 15:20:48 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /index.html.var denied
[Thu Mar 30 15:20:48 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /index.php denied
[Thu Mar 30 15:20:48 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /index.php3 denied
[Thu Mar 30 15:20:48 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /index.php4 denied
[Thu Mar 30 15:22:38 2006] [error] [client ::1] (13)Permission denied: access to /index.html denied
[Thu Mar 30 15:22:38 2006] [error] [client ::1] (13)Permission denied: access to /index.html.var denied
[Thu Mar 30 15:22:38 2006] [error] [client ::1] (13)Permission denied: access to /index.php denied
[Thu Mar 30 15:22:38 2006] [error] [client ::1] (13)Permission denied: access to /index.php3 denied
[Thu Mar 30 15:22:38 2006] [error] [client ::1] (13)Permission denied: access to /index.php4 denied
[Thu Mar 30 15:22:40 2006] [error] [client ::1] (13)Permission denied: access to /favicon.ico denied
[Thu Mar 30 15:22:48 2006] [error] [client 127.0.0.1] (13)Permission denied: access to /index.html denied
[Thu Mar 30 15:22:48 2006] [error] [client 127.0.0.1] (13)Permission denied: access to /index.html.var denied
[Thu Mar 30 15:22:48 2006] [error] [client 127.0.0.1] (13)Permission denied: access to /index.php denied
[Thu Mar 30 15:22:48 2006] [error] [client 127.0.0.1] (13)Permission denied: access to /index.php3 denied
[Thu Mar 30 15:22:48 2006] [error] [client 127.0.0.1] (13)Permission denied: access to /index.php4 denied
[Thu Mar 30 15:22:48 2006] [error] [client 127.0.0.1] (13)Permission denied: access to /favicon.ico denied
[Thu Mar 30 15:23:03 2006] [error] [client 127.0.0.1] (13)Permission denied: access to /kwn/index.php denied
[Thu Mar 30 15:32:25 2006] [notice] caught SIGTERM, shutting down
[Thu Mar 30 15:32:26 2006] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Thu Mar 30 15:32:26 2006] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec2)
[Thu Mar 30 15:32:28 2006] [notice] Apache/2.0.54 (Linux/SUSE) configured -- resuming normal operations
[Thu Mar 30 15:32:41 2006] [error] [client 192.168.1.13] (13)Permission denied: access to / denied
[Thu Mar 30 15:32:41 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /favicon.ico denied
[Thu Mar 30 15:32:41 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /favicon.ico denied
[Thu Mar 30 15:33:31 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /favicon.ico denied
[Thu Mar 30 15:33:32 2006] [error] [client 192.168.1.13] (13)Permission denied: access to / denied
[Thu Mar 30 15:33:39 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /kwn/index.php denied
[Thu Mar 30 15:33:43 2006] [notice] caught SIGTERM, shutting down
[Thu Mar 30 15:33:44 2006] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Thu Mar 30 15:33:44 2006] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec2)
[Thu Mar 30 15:33:45 2006] [notice] Apache/2.0.54 (Linux/SUSE) configured -- resuming normal operations
[Thu Mar 30 15:33:48 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /kwn/index.php denied
[Thu Mar 30 15:33:53 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /kwn/index.php denied
[Thu Mar 30 15:34:19 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /kwn/index.php denied
[Thu Mar 30 15:34:22 2006] [notice] caught SIGTERM, shutting down
[Thu Mar 30 15:34:23 2006] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Thu Mar 30 15:34:23 2006] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec2)
[Thu Mar 30 15:34:24 2006] [notice] Apache/2.0.54 (Linux/SUSE) configured -- resuming normal operations
[Thu Mar 30 15:34:27 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /kwn/index.php denied
[Thu Mar 30 15:34:56 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /kwn/index.php denied
[Thu Mar 30 15:35:00 2006] [notice] caught SIGTERM, shutting down
[Thu Mar 30 15:35:01 2006] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Thu Mar 30 15:35:01 2006] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec2)
[Thu Mar 30 15:35:01 2006] [notice] Apache/2.0.54 (Linux/SUSE) configured -- resuming normal operations
[Thu Mar 30 15:35:05 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /kwn/index.php denied
[Thu Mar 30 15:35:09 2006] [error] [client 192.168.1.13] (13)Permission denied: access to / denied
[Thu Mar 30 15:35:41 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /apache_pb.gif denied
[Thu Mar 30 15:37:04 2006] [notice] caught SIGTERM, shutting down
[Thu Mar 30 15:37:05 2006] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Thu Mar 30 15:37:05 2006] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec2)
[Thu Mar 30 15:37:07 2006] [notice] Apache/2.0.54 (Linux/SUSE) configured -- resuming normal operations
[Thu Mar 30 15:37:09 2006] [error] [client 192.168.1.13] (13)Permission denied: access to /apache_pb.gif denied
[Thu Mar 30 15:37:17 2006] [error] [client 127.0.0.1] (13)Permission denied: access to /kwn/index.php denied
[Thu Mar 30 15:37:22 2006] [error] [client 127.0.0.1] (13)Permission denied: access to / denied
[Thu Mar 30 15:37:36 2006] [error] [client 127.0.0.1] (13)Permission denied: access to /index.html denied
[Thu Mar 30 15:37:43 2006] [error] [client ::1] (13)Permission denied: access to /kwn/index.php denied

Alles anzeigen

muss ich da noch irgendwo einen hebel umsetzen das das geht? (chmod habe ich zwar nur auf 750 aber selbst wenn ich auf 755 gehe oder 777 erhöhe geht es nicht... (chmod erhöhe ich per ftp))

GreenRover

poste mal
/etc/apache2/default-server.conf

und wenn sich was im vhost.d befindet auch noch die datein.

cookie

hier die default-server.conf:

Code

#
# Global configuration that will be applicable for all virtual hosts, unless
# deleted here, or overriden elswhere.
# 


DocumentRoot "/srv/www/htdocs"


#
# Configure the DocumentRoot
#
<Directory "/srv/www/htdocs">
	# Possible values for the Options directive are "None", "All",
	# or any combination of:
	#   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
	#
	# Note that "MultiViews" must be named *explicitly* --- "Options All"
	# doesn't give it to you.
	#
	# The Options directive is both complicated and important.  Please see
	# http://httpd.apache.org/docs-2.0/mod/core.html#options
	# for more information.
	Options None
	# AllowOverride controls what directives may be placed in .htaccess files.
	# It can be "All", "None", or any combination of the keywords:
	#   Options FileInfo AuthConfig Limit
	AllowOverride None
	# Controls who can get stuff from this server.
	Order allow,deny
	Allow from all
</Directory>


# Aliases: aliases can be added as needed (with no limit). The format is 
# Alias fakename realname
#
# Note that if you include a trailing / on fakename then the server will
# require it to be present in the URL.  So "/icons" isn't aliased in this
# example, only "/icons/".  If the fakename is slash-terminated, then the 
# realname must also be slash terminated, and if the fakename omits the 
# trailing slash, the realname must also omit it.
#
# We include the /icons/ alias for FancyIndexed directory listings.  If you
# do not use FancyIndexing, you may comment this out.
#
Alias /icons/ "/usr/share/apache2/icons/"


<Directory "/usr/share/apache2/icons">
	Options Indexes MultiViews
	AllowOverride None
	Order allow,deny
	Allow from all
</Directory>


# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the realname directory are treated as applications and
# run by the server when requested rather than as documents sent to the client.
# The same rules about trailing "/" apply to ScriptAlias directives as to
# Alias.
#
ScriptAlias /cgi-bin/ "/srv/www/cgi-bin/"


# "/srv/www/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "/srv/www/cgi-bin">
	AllowOverride None
	Options +ExecCGI -Includes
	Order allow,deny
	Allow from all
</Directory>


# UserDir: The name of the directory that is appended onto a user's home
# directory if a ~user request is received.
#
# To disable it, simply remove userdir from the list of modules in APACHE_MODULES 
# in /etc/sysconfig/apache2.
#
<IfModule mod_userdir.c>
	# Note that the name of the user directory ("public_html") cannot simply be
	# changed here, since it is a compile time setting. The apache package
	# would have to be rebuilt. You could work around by deleting
	# /usr/sbin/suexec, but then all scripts from the directories would be
	# executed with the UID of the webserver.
	UserDir public_html
	# The actual configuration of the directory is in
	# /etc/apache2/mod_userdir.conf.
	Include /etc/apache2/mod_userdir.conf
	# You can, however, change the ~ if you find it awkward, by mapping e.g.
	# http://www.example.com/users/karl-heinz/ --> /home/karl-heinz/public_html/ 
	#AliasMatch ^/users/([a-zA-Z0-9-_.]*)/?(.*) /home/$1/public_html/$2
</IfModule>




# Include all *.conf files from /etc/apache2/conf.d/.
#
# This is mostly meant as a place for other RPM packages to drop in their
# configuration snippet.
#
# You can comment this out here if you want those bits include only in a
# certain virtual host, but not here.
#
Include /etc/apache2/conf.d/*.conf


# The manual... if it is installed ('?' means it won't complain)
Include /etc/apache2/conf.d/apache2-manual?conf

Alles anzeigen

und im ordner vhost.d
vhost.template

Code

#
# VirtualHost template
# Note: to use the template, rename it to /etc/apache2/vhost.d/yourvhost.conf. 
# Files must have the .conf suffix to be loaded.
#
# See /usr/share/doc/packages/apache2/README.QUICKSTART for further hints 
# about virtual hosts.
#
# Almost any Apache directive may go into a VirtualHost container.
# The first VirtualHost section is used for requests without a known
# server name.
#
<VirtualHost *:80>
    ServerAdmin [email]webmaster@dummy-host.example.com[/email]
    ServerName dummy-host.example.com


    # DocumentRoot: The directory out of which you will serve your
    # documents. By default, all requests are taken from this directory, but
    # symbolic links and aliases may be used to point to other locations.
    DocumentRoot /srv/www/vhosts/dummy-host.example.com


    # if not specified, the global error log is used
    ErrorLog /var/log/apache2/dummy-host.example.com-error_log
    CustomLog /var/log/apache2/dummy-host.example.com-access_log combined


    # don't loose time with IP address lookups
    HostnameLookups Off


    # needed for named virtual hosts
    UseCanonicalName Off


    # configures the footer on server-generated documents
    ServerSignature On




    # Optionally, include *.conf files from /etc/apache2/conf.d/
    #
    # For example, to allow execution of PHP scripts:
    #
    # Include /etc/apache2/conf.d/mod_php4.conf
    #
    # or, to include all configuration snippets added by packages:
    # Include /etc/apache2/conf.d/*.conf




    # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the realname directory are treated as applications and
    # run by the server when requested rather than as documents sent to the client.
    # The same rules about trailing "/" apply to ScriptAlias directives as to
    # Alias.
    #
    ScriptAlias /cgi-bin/ "/srv/www/vhosts/dummy-host.example.com/cgi-bin/"


    # "/srv/www/cgi-bin" should be changed to whatever your ScriptAliased
    # CGI directory exists, if you have one, and where ScriptAlias points to.
    #
    <Directory "/srv/www/vhosts/dummy-host.example.com/cgi-bin">
	AllowOverride None
	Options +ExecCGI -Includes
	Order allow,deny
	Allow from all
    </Directory>




    # UserDir: The name of the directory that is appended onto a user's home
    # directory if a ~user request is received.
    #
    # To disable it, simply remove userdir from the list of modules in APACHE_MODULES
    # in /etc/sysconfig/apache2.
    #
    <IfModule mod_userdir.c>
	# Note that the name of the user directory ("public_html") cannot simply be
	# changed here, since it is a compile time setting. The apache package
	# would have to be rebuilt. You could work around by deleting
	# /usr/sbin/suexec, but then all scripts from the directories would be
	# executed with the UID of the webserver.
	UserDir public_html
	# The actual configuration of the directory is in
	# /etc/apache2/mod_userdir.conf.
	Include /etc/apache2/mod_userdir.conf
	# You can, however, change the ~ if you find it awkward, by mapping e.g.
	# http://www.example.com/users/karl-heinz/ --> /home/karl-heinz/public_html/
	#AliasMatch ^/users/([a-zA-Z0-9-_.]*)/?(.*) /home/$1/public_html/$2
    </IfModule>




    #
    # This should be changed to whatever you set DocumentRoot to.
    #
    <Directory "/srv/www/vhosts/dummy-host.example.com">

	#
	# Possible values for the Options directive are "None", "All",
	# or any combination of:
	#   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
	#
	# Note that "MultiViews" must be named *explicitly* --- "Options All"
	# doesn't give it to you.
	#
	# The Options directive is both complicated and important.  Please see
	# http://httpd.apache.org/docs-2.0/mod/core.html#options
	# for more information.
	#
	Options Indexes FollowSymLinks

	#
	# AllowOverride controls what directives may be placed in .htaccess files.
	# It can be "All", "None", or any combination of the keywords:
	#   Options FileInfo AuthConfig Limit
	#
	AllowOverride None

	#
	# Controls who can get stuff from this server.
	#
	Order allow,deny
	Allow from all

    </Directory>


</VirtualHost>

Alles anzeigen

und da ist noch eine drinen die vhost-ssl.template:

Code

# Template for a VirtualHost with SSL
# Note: to use the template, rename it to /etc/apache2/vhost.d/yourvhost.conf.
# Files must have the .conf suffix to be loaded.
#
# See /usr/share/doc/packages/apache2/README.QUICKSTART for further hints
# about virtual hosts.


#
# 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>
#
#   For the moment, see <URL:http://www.modssl.org/docs/> for this info. 
#   The documents are still being prepared from material donated by the
#   modssl project.
# 
# 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.  
#


#   Until documentation is completed, please check http://www.modssl.org/
#   for additional config examples and module docmentation.  Directives
#   and features of mod_ssl are largely unchanged from the mod_ssl project
#   for Apache 1.3.


<IfDefine SSL>
<IfDefine !NOSSL>


##
## SSL Virtual Host Context
##


<VirtualHost _default_:443>


	#  General setup for the virtual host
	DocumentRoot "/srv/www/htdocs"
	#ServerName [url]www.example.com:443[/url]
	#ServerAdmin [email]webmaster@example.com[/email]
	ErrorLog /var/log/apache2/error_log
	TransferLog /var/log/apache2/access_log


	#   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 "/srv/www/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 /var/log/apache2/ssl_request_log   ssl_combined


</VirtualHost>                                  


</IfDefine>
</IfDefine>

Alles anzeigen

kensworld

Also was ich empfehlen kann, ist die easygate distribution.

Die installation ist sehr schlank gehalten und bietet einige vorkonfigurierte Server, wie exchange4linux Server (Mailserver), webserver, ftp server, webserver, etc.
Die Installation ist gerade mal um die 350MB gross. Die Konfiguration erfolgt komplett über ein Webinterface.

Alternativ, um Deine derzeitige Distri zu konfigurieren, kannst Du auch das Tool "webmin" verwenden. http://www.webmin.com/
Das macht das konfigurieren unter Linux sehr viel einfacher.

Die nächste Frage ist, weshal sollte Dein Provider etwas gegen einen Server haben. Mit eine dyndns Dienst und einer URL wie von http://www.nic.de.vu kannst Du auf den Server ein Portforewarding machen und hast somit einen öffentlichen Server. Nur wird die Anbindung halt nicht sehr schnell sein, aber das interessiert den Provider recht wenig.

Gruss
Ken

cookie

danke für den tipp mit dem webmi tipp...

mein provider hat da nix dagegen zu haben ... (ist mir relativ egal) und das ist auch alles kein problem... bin nur gerade beim einrichten.

GreenRover

kensworld dr ist aber bewust das den webmin jeder der sich etwas mit linux auskennt hacken kann
?! und damit root rechte erlangen ?!

kensworld

Das mag schon sein, aber auf der anderen Seite, erleichtert es einem die Konfiguration erheblich.

Gruss
Ken

GreenRover

ja das stimmt und es giebt mom leider auch nichts vergleichbares was sciher ist. ich würde aber dennoch vdavon abraten. aber no risk no fun oder wie sacht man so schön.. :-p

kensworld

es ist schon eine Weile her, dass ich webmin verwendet habe, aber wenn ich mich recht entsinne, kommt man auf die webmin gui nur über einen bestimmten Netzwerkport. Solange dieser nicht geöffnet wird, kann doch keiner von aussen auf das Interface zugreifen.

Gruss
Ken

eigener server

Tags

Benutzer online in diesem Thema