localhost[RESOLU]

gycath · Le 21/04/2014, à 18:53

Bonjour
Suite au passage de ubuntu 13 10 vers ubuntu 14 04 LTS (par une mise à niveau), lorsque je me connecte à loalhost via Mozilla j'arrive sur la page Index of/ . Mais sur cette page n’apparaît plus les dossiers public et private ni le dossier que j'avais créé!!!
Est ce quelqu'un peut m'aider à résoudre ce problème?
Merci d'avance

Dernière modification par gycath (Le 22/04/2014, à 00:19)

richardgilbert · Le 21/04/2014, à 20:04

Je suppose que tu devras retoucher les droits dans les dossiers public et private.

jplemoine · Le 21/04/2014, à 20:18

je pense que c'est que tu as le même problème que j'ai eu :
le répertoire par défaut n'est plus /var/www mais /var/www/html.

Donc, si ton site est dans /var/ww. L'installation d'Apache crée un index.html dans /var/www/html
et c'est ce dernier qui est lu.

gycath · Le 21/04/2014, à 21:23

Merci pour vos réponses:
@jplemoine: mon site est dans /var/ww et je suis allé voir dans /var/www/html qui lui est vide et il n'y a pas index.html
comment as -tu résolu ton pb?
Bien cordialement

jplemoine · Le 21/04/2014, à 21:29

comme dans le virtualhost par défaut, il y avais /var/www/html, j'ai modifié mon site pour tout mettre dans /var/www/html.
(il y avait des chemins en dur).

gycath · Le 21/04/2014, à 21:37

tu peux m'indiquer le processus car je ne maîtrise pas!!

jplemoine · Le 21/04/2014, à 21:44

il faut que tu regardes dans /etc/apache2/sites-available/, il doit y avoir un fichier avec default dans le nom.
tu regardes la valeur de DocumentRoot et tu postes le résultat.

Oni_Shadow · Le 21/04/2014, à 21:52

ce qu'il veut dire, c'est de mettre tes fichiers dans /var/www/html et plus dans /var/www simplement
et si tu avais des chemins complet et non relatif dans ton code ben... va falloir adapter

jplemoine · Le 21/04/2014, à 22:31

pour moi, oui. Mais pour toi, je ne sais pas : il faut que tu me donnes le retour de ce que je t'ai demandé.

gycath · Le 21/04/2014, à 23:12

J'ai 2 dossiers dans /etc/apache2/sites-available/:
-----> l'un 00-default.conf qui contient ceci:
<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 www.example.com

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

------> et un autre default-ssl.conf avec ceci:

<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

jplemoine · Le 21/04/2014, à 23:19

gycath a écrit :

DocumentRoot /var/www/html

Donc, il faut que tu utilises /var/html/html et non /var/www

gycath · Le 21/04/2014, à 23:36

Donc en clair je passe mes public et private dans /var/www/html sachant que /var/www/ contient
---> un dossier nommé HTML vide
----> un raccourci private qui en clic dessus l'ouvre
----> un raccourci public qui en clic dessus l'ouvre

et je dois utiliser des lignes de commande?

jplemoine · Le 21/04/2014, à 23:42

oui.ça doit être un truc du genre :

sudo mv /var/www/private /var/www/html/
sudo mv /var/www/public /var/www/html/

gycath · Le 22/04/2014, à 00:03

je suis passé sur un autre ordi, car du coup en tapant les lignes précédentes je n'ai plus de connection internet!!!!

gycath · Le 22/04/2014, à 00:18

Erreur de ma part!!!! tout fonctionne comme avant
Je te remercie pour ton aide très précieuse
Bonne soirée

Ubuntu-fr

Navigation

Liens de recherche

Annonce

#1 Le 21/04/2014, à 18:53

localhost[RESOLU]

#2 Le 21/04/2014, à 20:04

Re : localhost[RESOLU]

#3 Le 21/04/2014, à 20:18

Re : localhost[RESOLU]

#4 Le 21/04/2014, à 21:23

Re : localhost[RESOLU]

#5 Le 21/04/2014, à 21:29

Re : localhost[RESOLU]

#6 Le 21/04/2014, à 21:37

Re : localhost[RESOLU]

#7 Le 21/04/2014, à 21:44

Re : localhost[RESOLU]

#8 Le 21/04/2014, à 21:52

Re : localhost[RESOLU]

#9 Le 21/04/2014, à 22:31

Re : localhost[RESOLU]

#10 Le 21/04/2014, à 23:12

Re : localhost[RESOLU]

#11 Le 21/04/2014, à 23:19

Re : localhost[RESOLU]

#12 Le 21/04/2014, à 23:36

Re : localhost[RESOLU]

#13 Le 21/04/2014, à 23:42

Re : localhost[RESOLU]

#14 Le 22/04/2014, à 00:03

Re : localhost[RESOLU]

#15 Le 22/04/2014, à 00:18

Re : localhost[RESOLU]

Pied de page des forums