Sponsor-Board.de
Thema geschlossen  Thema schreiben 

Apache 2 Fehler

Verfasser Nachricht

Beiträge: 31
Registriert seit: Nov 2016
Status: offline


Beitrag: #1
Apache 2 Fehler

Hallo,

wollte gerade etwas auf meiner Webseite installieren aber es kommt immer 404 Not Found

Not Found

The requested URL / was not found on this server.

Apache/2.4.7 (Ubuntu) Server at [Link: Registrierung erforderlich] Port 80

Kann mir da jemand bitte behilflich sein oder hat jemad ne schriftliche Lösung für mich auf deutsch?


Mit freundlichen Grüßen
SkinsBoss.com

04.12.2016 00:48
 
Alle Beiträge dieses Benutzers finden

Beiträge: 159
Bewertung: 22
Registriert seit: Nov 2016
Status: offline


Beitrag: #2
RE: Apache 2 Fehler

Wenn keine Index Datei in /var/www ist, kann er auch nichts finden. Sicher dass alles in den korrekten Sub Ordnern angelegt ist?

Ohne die Struktur deiner Ordner / eingestellten Configs zu kennen, kann man nicht helfen.

04.12.2016 01:01
 
Webseite des Benutzers besuchen Alle Beiträge dieses Benutzers finden

Beiträge: 31
Registriert seit: Nov 2016
Status: offline


Beitrag: #3
RE: Apache 2 Fehler

ja ist eine index.php vorhanden und in /var/www/forum sind die sachen von wbb


Mit freundlichen Grüßen
SkinsBoss.com

04.12.2016 01:05
 
Alle Beiträge dieses Benutzers finden

Beiträge: 358
Bewertung: 44
Registriert seit: Jan 2015
Status: offline


Beitrag: #4
RE: Apache 2 Fehler

Nist-Photography schrieb:
Wenn keine Index Datei in /var/www ist, kann er auch nichts finden.


Wenn keine index vorhanden ist, wird idr. ein "403 Forbidden" ausgegeben.
Ich vermute, dass der entsprechende vHost auf ein Verzeichnis zeigt, welches nicht existiert.

Edit: Poste bitte mal den Inhalt des entsprechenden vHosts

Grüße

Dieser Beitrag wurde zuletzt bearbeitet: 04.12.2016 01:07 von v3ng.

04.12.2016 01:06
 
Webseite des Benutzers besuchen Alle Beiträge dieses Benutzers finden

Beiträge: 31
Registriert seit: Nov 2016
Status: offline


Beitrag: #5
RE: Apache 2 Fehler

000-default.conf

Zitat:
<VirtualHost *:80>
# The ServerName directive sets the request scheme, hostname and port that
# the server uses to identify itself. This is used when creating
# redirection URLs. In the context of virtual hosts, the ServerName
# specifies what hostname must appear in the request's Host: header to
# match this virtual host. For the default virtual host (this file) this
# value is not decisive as it is used as a last resort host regardless.
# However, you must set it for any further virtual host explicitly.
#ServerName [Link: Registrierung erforderlich]

ServerAdmin webmaster@localhost
DocumentRoot /var/www/html

# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the loglevel for particular
# modules, e.g.
#LogLevel info ssl:warn

ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined

# For most configuration files from conf-available/, which are
# enabled or disabled at a global level, it is possible to
# include a line for only one particular virtual host. For example the
# following line enables the CGI configuration for this host only
# after it has been globally disabled with "a2disconf".
#Include conf-available/serve-cgi-bin.conf
</VirtualHost>

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet


default-ssl.conf

Zitat:
<IfModule mod_ssl.c>
<VirtualHost _default_:443>
ServerAdmin webmaster@localhost

DocumentRoot /var/www/html

# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the loglevel for particular
# modules, e.g.
#LogLevel info ssl:warn

ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined

# For most configuration files from conf-available/, which are
# enabled or disabled at a global level, it is possible to
# include a line for only one particular virtual host. For example the
# following line enables the CGI configuration for this host only
# after it has been globally disabled with "a2disconf".
#Include conf-available/serve-cgi-bin.conf

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

# A self-signed (snakeoil) certificate can be created by installing
# the ssl-cert package. See
# /usr/share/doc/apache2/README.Debian.gz for more info.
# If both key and certificate are stored in the same file, only the
# SSLCertificateFile directive is needed.
SSLCertificateFile /etc/ssl/certs/ssl-cert-snakeoil.pem
SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.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/server-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/ssl/certs/
#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

# 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 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 /usr/lib/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.
BrowserMatch "MSIE [2-6]" \
nokeepalive ssl-unclean-shutdown \
downgrade-1.0 force-response-1.0
# MSIE 7 and newer should be able to use keepalive
BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown

</VirtualHost>
</IfModule>

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet


Mit freundlichen Grüßen
SkinsBoss.com

04.12.2016 01:12
 
Alle Beiträge dieses Benutzers finden

Beiträge: 159
Bewertung: 22
Registriert seit: Nov 2016
Status: offline


Beitrag: #6
RE: Apache 2 Fehler

Wenn du dein Forum unter /var/www/forum erreichbar machen möchtest, musst du auch einen entsprechenden Vhost dafür anlegen.

Laut deinen default Vhost, müssen Index Dateien in /var/www/html liegen.

Zitat:
DocumentRoot /var/www/html

04.12.2016 01:18
 
Webseite des Benutzers besuchen Alle Beiträge dieses Benutzers finden

Beiträge: 31
Registriert seit: Nov 2016
Status: offline


Beitrag: #7
RE: Apache 2 Fehler

Danke an alle für die schnelle Hilfe.


Mit freundlichen Grüßen
SkinsBoss.com

04.12.2016 01:21
 
Alle Beiträge dieses Benutzers finden
Thema geschlossen  Thema schreiben 

Möglicherweise verwandte Themen...
Thema: Verfasser Antworten: Ansichten: Letzter Beitrag
  Apache plötzlich kaputt? Dyroxplays 14 2.874 11.02.2017 14:38
Letzter Beitrag: Dyroxplays
  Froxlor Fehler HardwareNow 10 2.941 03.06.2016 21:42
Letzter Beitrag: HardwareNow
  Apache 2 Virtueller Host Emptyx 2 1.735 01.06.2016 16:20
Letzter Beitrag: Emptyx
  CF Image Host - Fehler Jerr0w 5 1.750 24.04.2016 22:23
Letzter Beitrag: [NG] FreakyLike
  [WBB] PHP Fehler DJ_Drio 4 1.519 19.04.2016 13:16
Letzter Beitrag: DJ_Drio

 Druckversion anzeigen
 Thema einem Freund senden
 Thema abonnieren
 Thema zu den Favoriten hinzufügen

Sponsor-Board.de

Community
Über uns
Partner
Powered by Mybb: Copyright 2002-2024 by MyBB Group - Deutsche-Übersetzung von Mybb.de
 
© 2007-2024 Sponsor-Board.de - Hosted by OVH

Willkommen auf SB!   Sie benötigen ein Sponsoring?   1. Anmelden   2. Sponsoring-Anfrage erstellen   3. Nachrichten von Sponsoren erhalten   Kostenlos!   Jetzt registrieren