Page 4 sur 7

Re: Installation serveur LAMP

Posté : ven. 7 févr. 2025 19:19
par Pingouindumint

Dernier message de la page précédente :

J'avance lentement mais j'ai réussi à installer wordpress.

Par contre, je cherche à restaurer mais le logiciel de sauvegarde updraft cherche à se connecter au site en FTP. !

Il mouline. Je vais patienter : je verrai bien.

Encore merci à cyrille pour sa patience et son dévouement pour essayer de me dépanner de LAMP. :)

Re: Installation serveur LAMP

Posté : ven. 7 févr. 2025 19:54
par Pingouindumint
Je reviens sur l'install wordpress en local.
J'essaie de restaurer la version en ligne.

Il me m'affiche un message d'erreur concernant apache :

Code : Tout sélectionner

You are using the Apache webserver, but do not seem to have the mod_rewrite module loaded. You should enable mod_rewrite to make any pretty permalinks (e.g. http://example.com/my-page/) work
Comment activer le module mod_rewrite dans la config d'apache ?

Re: Installation serveur LAMP

Posté : ven. 7 févr. 2025 20:05
par Pingouindumint
Je viens de trouver ceci concernant mod_rewrite.
https://doc.ubuntu-fr.org/apache2#mod_rewrite

Mais où ajouter ces lignes : dans .htaccess ou dans un fichier de conf de apache ?

Re: Installation serveur LAMP

Posté : ven. 7 févr. 2025 21:49
par Pingouindumint
Tu dis :
comme quoi utiliser le wordpress des dépôts aurait sans doute configuré tout cela par défaut
.

Je ne savais pas qu'il existait un dépôt.

J'ai regardé dans synaptic. wordpress apparaît mais il n'y a rien de coché ni même les dépendances. On peut encore l'installer.
Tu crois que l'on peut l'installer en plus par synaptic ou bien cela va me mettre le bazar ?

Re: Installation serveur LAMP

Posté : sam. 8 févr. 2025 13:18
par Pingouindumint
Bonjour à tous,

Pour finir, j'ai décidé de me remettre au tuto de cyrille viewtopic.php?f=12&t=13032#3 et je reprends donc les virtuals hosts et après, je reprendrai aussi Editer et configurer le fichier /etc/hosts.

Je suis arrivé à l'étape après :

Code : Tout sélectionner

sudo a2ensite peplocal.fr
Enabling site peplocal.fr.
Il me répond en erreur :

Code : Tout sélectionner

sudo systemctl reload apache2
Job for apache2.service failed.
See "systemctl status apache2.service" and "journalctl -xeu apache2.service" for details.

Re: Installation serveur LAMP

Posté : sam. 8 févr. 2025 13:54
par Aunisien
et alors que disent les logs ?

Concernant des installations d'Apache, php et MariaDb sur le net il y a beaucoup de tutos, il faudrait peut être commencé par là et sur comment ça fonctionne.
Lorsque tu parles d'un site en Prod j'imagine qu'il sera accessible depuis internet, il vaut mieux que tu comprennes comment ça marche pour la sécurité de ton site et de tes données.

Re: Installation serveur LAMP

Posté : sam. 8 févr. 2025 14:52
par Pingouindumint
J'attends surtout une réponse qui pourrait m'aider : cela fait 7 jours que je suis sur ce problème. En tout cas, merci cyrille. ;)
Des tutos, il y en a plein, c'est certain. Passer ses journées à lire des tutos et à la fin, on ne sait toujours pas quoi faire. :(

Que dois-je taper comme commande pour avancer ?
Merci.

Re: Installation serveur LAMP

Posté : sam. 8 févr. 2025 17:36
par Pingouindumint
Réponse :

Code : Tout sélectionner

systemctl status apache2.service
● apache2.service - The Apache HTTP Server
     Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled; preset: enabled)
     Active: active (running) since Sat 2025-02-08 09:44:38 CET; 7h ago
       Docs: https://httpd.apache.org/docs/2.4/
    Process: 1547 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS)
    Process: 6921 ExecReload=/usr/sbin/apachectl graceful (code=exited, status=1/FAILURE)
   Main PID: 1614 (apache2)
      Tasks: 6 (limit: 19004)
     Memory: 51.1M (peak: 56.0M)
        CPU: 1.213s
     CGroup: /system.slice/apache2.service
             ├─1614 /usr/sbin/apache2 -k start
             ├─1635 /usr/sbin/apache2 -k start
             ├─1637 /usr/sbin/apache2 -k start
             ├─1641 /usr/sbin/apache2 -k start
             ├─1643 /usr/sbin/apache2 -k start
             └─1644 /usr/sbin/apache2 -k start

févr. 08 11:26:04 toto-lemien systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
févr. 08 11:26:04 toto-lemien systemd[1]: Reload failed for apache2.service - The Apache HTTP Server.
févr. 08 11:26:32 toto-lemien systemd[1]: Reloading apache2.service - The Apache HTTP Server...
févr. 08 11:26:32 toto-lemien apachectl[6873]: apache2: Syntax error on line 225 of /etc/apache2/apache2.conf: Syntax error on line 1 o>
févr. 08 11:26:32 toto-lemien systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
lines 1-23

Ensuite, la conf du Virtaul Hosts que je n'ai pas terminée :
Le fichier peplocal.fr.conf :

Code : Tout sélectionner

<VirtualHost *:80>
    ServerName peplocal.fr
    ServerAlias www.peplocal.fr
    ServerAdmin webmaster@peplocal.fr
    DocumentRoot /var/www/peplocal.fr/public_html

    <Directory /var/www/peplocal.fr/public_html>
        Options -Indexes +FollowSymLinks
        AllowOverride All
    </Directory>

Re: Installation serveur LAMP

Posté : sam. 8 févr. 2025 17:50
par Pingouindumint
Créé dans :
/etc/apache2/sites-available

Re: Installation serveur LAMP

Posté : sam. 8 févr. 2025 17:54
par Pingouindumint
Voici le fichier apache2.conf :

Code : Tout sélectionner

# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.4/ for detailed information about
# the directives and /usr/share/doc/apache2/README.Debian about Debian specific
# hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream's suggested way to configure the web server. This is because Debian's
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.

# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
#
#	/etc/apache2/
#	|-- apache2.conf
#	|	`--  ports.conf
#	|-- mods-enabled
#	|	|-- *.load
#	|	`-- *.conf
#	|-- conf-enabled
#	|	`-- *.conf
# 	`-- sites-enabled
#	 	`-- *.conf
#
#
# * apache2.conf is the main configuration file (this file). It puts the pieces
#   together by including all remaining configuration files when starting up the
#   web server.
#
# * ports.conf is always included from the main configuration file. It is
#   supposed to determine listening ports for incoming connections which can be
#   customized anytime.
#
# * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/
#   directories contain particular configuration snippets which manage modules,
#   global configuration fragments, or virtual host configurations,
#   respectively.
#
#   They are activated by symlinking available configuration files from their
#   respective *-available/ counterparts. These should be managed by using our
#   helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See
#   their respective man pages for detailed information.
#
# * The binary is called apache2. Due to the use of environment variables, in
#   the default configuration, apache2 needs to be started/stopped with
#   /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
#   work with the default configuration.


# Global configuration
#

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE!  If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the Mutex documentation (available
# at <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
#ServerRoot "/etc/apache2"

#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
#Mutex file:${APACHE_LOCK_DIR} default

#
# The directory where shm and other runtime files will be stored.
#

DefaultRuntimeDir ${APACHE_RUN_DIR}

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 5


# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

# 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 ${APACHE_LOG_DIR}/error.log

#
# LogLevel: Control the severity of messages logged to the error_log.
# Available values: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the log level for particular modules, e.g.
# "LogLevel info ssl:warn"
#
LogLevel warn

# Include module configuration:
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf

# Include list of ports to listen on
Include ports.conf


# Sets the default security model of the Apache2 HTTPD server. It does
# not allow access to the root filesystem outside of /usr/share and /var/www.
# The former is used by web applications packaged in Debian,
# the latter may be used for local directories served by the web server. If
# your system is serving content from a sub-directory in /srv you must allow
# access here, or in any related virtual host.
<Directory />
	Options FollowSymLinks
	AllowOverride None
	Require all denied
</Directory>

<Directory /usr/share>
	AllowOverride None
	Require all granted
</Directory>

<Directory /var/www/>
	Options Indexes FollowSymLinks
	AllowOverride None
	Require all granted
</Directory>

#<Directory /srv/>
#	Options Indexes FollowSymLinks
#	AllowOverride None
#	Require all granted
#</Directory>




# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives.  See also the AllowOverride
# directive.
#
AccessFileName .htaccess

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
	Require all denied
</FilesMatch>


#
# The following directives define some format nicknames for use with
# a CustomLog directive.
#
# These deviate from the Common Log Format definitions in that they use %O
# (the actual bytes sent including headers) instead of %b (the size of the
# requested file), because the latter makes it impossible to detect partial
# requests.
#
# Note that the use of %{X-Forwarded-For}i instead of %h is not recommended.
# Use mod_remoteip instead.
#
LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %O" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.

# Include generic snippets of statements
IncludeOptional conf-enabled/*.conf

# Include the virtual host configurations:
IncludeOptional sites-enabled/*.conf

Re: Installation serveur LAMP

Posté : sam. 8 févr. 2025 18:22
par Pingouindumint
Réponse de la commande :

Code : Tout sélectionner

ls -lR /etc/apache2/sites-enabled/
/etc/apache2/sites-enabled/:
total 0
lrwxrwxrwx 1 root root 35 sept. 16 21:59 000-default.conf -> ../sites-available/000-default.conf
lrwxrwxrwx 1 root root 35 févr.  8 11:25 peplocal.fr.conf -> ../sites-available/peplocal.fr.conf
lrwxrwxrwx 1 root root 37 sept. 17 21:19 peplocal.test.conf -> ../sites-available/peplocal.test.conf