Passage sur Nextcloud

[Wed Mar 25 13:59:49.894464 2020] [mpm_event:notice] [pid 22743:tid 3069738368] AH00489: Apache/2.4.38 (Debian) configured -- resuming normal operations
[Wed Mar 25 13:59:49.894969 2020] [core:notice] [pid 22743:tid 3069738368] AH00094: Command line: '/usr/sbin/apache2'
[Wed Mar 25 14:06:31.258063 2020] [mpm_event:notice] [pid 22743:tid 3069738368] AH00491: caught SIGTERM, shutting down
[Wed Mar 25 14:06:31.363062 2020] [mpm_prefork:notice] [pid 1744] AH00163: Apache/2.4.38 (Debian) configured -- resuming normal operations
[Wed Mar 25 14:06:31.363471 2020] [core:notice] [pid 1744] AH00094: Command line: '/usr/sbin/apache2'
[Wed Mar 25 14:06:32.413004 2020] [mpm_prefork:notice] [pid 1744] AH00169: caught SIGTERM, shutting down
[Wed Mar 25 14:06:32.709178 2020] [mpm_prefork:notice] [pid 1800] AH00163: Apache/2.4.38 (Debian) configured -- resuming normal operations
[Wed Mar 25 14:06:32.709440 2020] [core:notice] [pid 1800] AH00094: Command line: '/usr/sbin/apache2'
[Wed Mar 25 21:43:55.560041 2020] [php7:error] [pid 1802] [client 192.168.1.50:61650] script '/var/www/html/index.php' not found or unable to stat, referer: http://192.168.1.93/
[Wed Mar 25 21:46:30.591467 2020] [php7:error] [pid 1803] [client 192.168.1.50:61653] script '/var/www/html/index.php' not found or unable to stat, referer: http://192.168.1.93/
[Wed Mar 25 21:46:35.400835 2020] [php7:error] [pid 1803] [client 192.168.1.50:61653] script '/var/www/html/index.php' not found or unable to stat, referer: http://192.168.1.93/
[Wed Mar 25 21:46:43.445935 2020] [php7:error] [pid 1804] [client 192.168.1.50:61654] script '/var/www/html/index.php' not found or unable to stat, referer: http://192.168.1.93/
[Wed Mar 25 22:01:24.678389 2020] [php7:error] [pid 1805] [client 192.168.1.50:61671] script '/var/www/html/index.php' not found or unable to stat, referer: http://192.168.1.93/
[Wed Mar 25 22:09:49.756692 2020] [php7:error] [pid 1806] [client 192.168.1.50:61701] script '/var/www/html/index.php' not found or unable to stat, referer: http://192.168.1.93/
[Wed Mar 25 22:10:04.672558 2020] [php7:error] [pid 9161] [client 192.168.1.50:61703] script '/var/www/html/index.php' not found or unable to stat, referer: http://piaa.ddnsfree.com/
[Wed Mar 25 22:34:27.319161 2020] [php7:error] [pid 1803] [client 192.168.1.50:61741] script '/var/www/html/index.php' not found or unable to stat, referer: http://192.168.1.93/
[Wed Mar 25 22:37:11.839354 2020] [php7:error] [pid 1804] [client 192.168.1.50:61744] script '/var/www/html/index.php' not found or unable to stat, referer: http://192.168.1.93/
[Wed Mar 25 22:37:13.905234 2020] [php7:error] [pid 1804] [client 192.168.1.50:61744] script '/var/www/html/index.php' not found or unable to stat, referer: http://192.168.1.93/
[Wed Mar 25 22:37:16.990181 2020] [php7:error] [pid 1804] [client 192.168.1.50:61744] script '/var/www/html/index.php' not found or unable to stat, referer: http://192.168.1.93/
[Wed Mar 25 22:37:42.851261 2020] [php7:error] [pid 1805] [client 192.168.1.50:61745] script '/var/www/html/index.php' not found or unable to stat, referer: http://192.168.1.93/
[Wed Mar 25 22:37:44.019063 2020] [php7:error] [pid 1805] [client 192.168.1.50:61745] script '/var/www/html/index.php' not found or unable to stat, referer: http://192.168.1.93/
[Wed Mar 25 22:37:52.375294 2020] [php7:error] [pid 1806] [client 192.168.1.50:61746] script '/var/www/html/index.php' not found or unable to stat, referer: http://192.168.1.93/
[Wed Mar 25 22:40:57.072533 2020] [php7:error] [pid 1802] [client 192.168.1.50:61761] script '/var/www/html/index.php' not found or unable to stat
[Wed Mar 25 22:41:06.843412 2020] [php7:error] [pid 9161] [client 192.168.1.50:61762] script '/var/www/html/index.php' not found or unable to stat
[Wed Mar 25 22:51:01.308646 2020] [php7:error] [pid 1803] [client 192.168.1.50:61770] script '/var/www/html/index.php' not found or unable to stat, referer: http://192.168.1.93/
[Wed Mar 25 22:51:28.390561 2020] [php7:error] [pid 1804] [client 192.168.1.50:61786] script '/var/www/html/index.php' not found or unable to stat, referer: http://piaa.ddnsfree.com/
[Wed Mar 25 22:54:13.219129 2020] [mpm_prefork:notice] [pid 1800] AH00171: Graceful restart requested, doing restart
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using ::1. Set the 'ServerName' directive globally to suppress this message
[Wed Mar 25 22:54:13.486611 2020] [mpm_prefork:notice] [pid 1800] AH00163: Apache/2.4.38 (Debian) configured -- resuming normal operations
[Wed Mar 25 22:54:13.486657 2020] [core:notice] [pid 1800] AH00094: Command line: '/usr/sbin/apache2'
[Wed Mar 25 22:54:29.211487 2020] [php7:error] [pid 9964] [client 192.168.1.50:61794] script '/var/www/html/index.php' not found or unable to stat
[Wed Mar 25 22:56:50.354408 2020] [mpm_prefork:notice] [pid 1800] AH00169: caught SIGTERM, shutting down
[Wed Mar 25 22:56:50.667925 2020] [mpm_prefork:notice] [pid 10004] AH00163: Apache/2.4.38 (Debian) configured -- resuming normal operations
[Wed Mar 25 22:56:50.668204 2020] [core:notice] [pid 10004] AH00094: Command line: '/usr/sbin/apache2'
[Wed Mar 25 22:59:43.646521 2020] [php7:error] [pid 10006] [client 192.168.1.50:61875] script '/var/www/html/index.php' not found or unable to stat, referer: http://192.168.1.93/
[Wed Mar 25 23:00:41.151538 2020] [php7:error] [pid 10047] [client 192.168.1.50:61887] script '/var/www/html/index.php' not found or unable to stat, referer: http://192.168.1.93/
[Wed Mar 25 23:10:22.571001 2020] [mpm_prefork:notice] [pid 10004] AH00169: caught SIGTERM, shutting down
[Wed Mar 25 23:10:22.879927 2020] [mpm_prefork:notice] [pid 10209] AH00163: Apache/2.4.38 (Debian) configured -- resuming normal operations
[Wed Mar 25 23:10:22.880198 2020] [core:notice] [pid 10209] AH00094: Command line: '/usr/sbin/apache2'
[Wed Mar 25 23:20:23.382296 2020] [mpm_prefork:notice] [pid 10209] AH00169: caught SIGTERM, shutting down
[Wed Mar 25 23:20:23.692329 2020] [mpm_prefork:notice] [pid 10564] AH00163: Apache/2.4.38 (Debian) configured -- resuming normal operations
[Wed Mar 25 23:20:23.692594 2020] [core:notice] [pid 10564] AH00094: Command line: '/usr/sbin/apache2'
[Wed Mar 25 23:53:19.566036 2020] [mpm_prefork:notice] [pid 10564] AH00169: caught SIGTERM, shutting down
[Wed Mar 25 23:53:19.956318 2020] [mpm_prefork:notice] [pid 11172] AH00163: Apache/2.4.38 (Debian) configured -- resuming normal operations
[Wed Mar 25 23:53:19.956577 2020] [core:notice] [pid 11172] AH00094: Command line: '/usr/sbin/apache2'
[Wed Mar 25 23:58:28.290496 2020] [mpm_prefork:notice] [pid 11172] AH00169: caught SIGTERM, shutting down
[Wed Mar 25 23:58:28.601514 2020] [mpm_prefork:notice] [pid 11397] AH00163: Apache/2.4.38 (Debian) configured -- resuming normal operations
[Wed Mar 25 23:58:28.601812 2020] [core:notice] [pid 11397] AH00094: Command line: '/usr/sbin/apache2'
[Thu Mar 26 00:01:46.326496 2020] [mpm_prefork:notice] [pid 11397] AH00169: caught SIGTERM, shutting down
[Thu Mar 26 00:01:46.637589 2020] [mpm_prefork:notice] [pid 11703] AH00163: Apache/2.4.38 (Debian) configured -- resuming normal operations
[Thu Mar 26 00:01:46.637887 2020] [core:notice] [pid 11703] AH00094: Command line: '/usr/sbin/apache2'
[Thu Mar 26 07:43:21.065426 2020] [mpm_prefork:notice] [pid 11703] AH00169: caught SIGTERM, shutting down
[Thu Mar 26 07:43:21.492725 2020] [mpm_prefork:notice] [pid 17183] AH00163: Apache/2.4.38 (Debian) OpenSSL/1.1.1d configured -- resuming normal operations
[Thu Mar 26 07:43:21.492982 2020] [core:notice] [pid 17183] AH00094: Command line: '/usr/sbin/apache2'
[Thu Mar 26 07:53:05.452637 2020] [mpm_prefork:notice] [pid 17183] AH00171: Graceful restart requested, doing restart
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using ::1. Set the 'ServerName' directive globally to suppress this message
[Thu Mar 26 07:53:05.721811 2020] [mpm_prefork:notice] [pid 17183] AH00163: Apache/2.4.38 (Debian) OpenSSL/1.1.1d configured -- resuming normal operations
[Thu Mar 26 07:53:05.721852 2020] [core:notice] [pid 17183] AH00094: Command line: '/usr/sbin/apache2'
[Thu Mar 26 07:53:47.298509 2020] [mpm_prefork:notice] [pid 17183] AH00169: caught SIGTERM, shutting down
[Thu Mar 26 07:53:47.614494 2020] [mpm_prefork:notice] [pid 17450] AH00163: Apache/2.4.38 (Debian) configured -- resuming normal operations
[Thu Mar 26 07:53:47.614754 2020] [core:notice] [pid 17450] AH00094: Command line: '/usr/sbin/apache2'
[Thu Mar 26 08:56:07.698500 2020] [mpm_prefork:notice] [pid 17450] AH00169: caught SIGTERM, shutting down
[Thu Mar 26 08:56:08.014377 2020] [mpm_prefork:notice] [pid 19322] AH00163: Apache/2.4.38 (Debian) configured -- resuming normal operations
[Thu Mar 26 08:56:08.014652 2020] [core:notice] [pid 19322] AH00094: Command line: '/usr/sbin/apache2'
[Thu Mar 26 08:57:15.611569 2020] [mpm_prefork:notice] [pid 19322] AH00171: Graceful restart requested, doing restart
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using ::1. Set the 'ServerName' directive globally to suppress this message
[Thu Mar 26 08:57:15.879808 2020] [ssl:emerg] [pid 19322] AH02572: Failed to configure at least one certificate and key for ::1:443
[Thu Mar 26 08:57:15.879887 2020] [ssl:emerg] [pid 19322] SSL Library Error: error:140A80B1:SSL routines:SSL_CTX_check_private_key:no certificate assigned
[Thu Mar 26 08:57:15.879917 2020] [ssl:emerg] [pid 19322] AH02311: Fatal error initialising mod_ssl, exiting. See /var/log/apache2/error.log for more information
[Thu Mar 26 08:57:15.879931 2020] [:emerg] [pid 19322] AH00020: Configuration Failed, exiting
[Thu Mar 26 08:58:47.498111 2020] [ssl:emerg] [pid 19384] AH02572: Failed to configure at least one certificate and key for ::1:443
[Thu Mar 26 08:58:47.498257 2020] [ssl:emerg] [pid 19384] SSL Library Error: error:140A80B1:SSL routines:SSL_CTX_check_private_key:no certificate assigned
[Thu Mar 26 08:58:47.498273 2020] [ssl:emerg] [pid 19384] AH02311: Fatal error initialising mod_ssl, exiting. See /var/log/apache2/error.log for more information
AH00016: Configuration Failed
[Thu Mar 26 09:02:21.475974 2020] [core:warn] [pid 19660] AH00098: pid file /var/run/apache2/apache2.pid overwritten -- Unclean shutdown of previous Apache run?
[Thu Mar 26 09:02:21.489522 2020] [mpm_prefork:notice] [pid 19660] AH00163: Apache/2.4.38 (Debian) configured -- resuming normal operations
[Thu Mar 26 09:02:21.489648 2020] [core:notice] [pid 19660] AH00094: Command line: '/usr/sbin/apache2'
[Thu Mar 26 09:02:41.854290 2020] [mpm_prefork:notice] [pid 19660] AH00169: caught SIGTERM, shutting down
[Thu Mar 26 09:26:02.010038 2020] [ssl:emerg] [pid 19986] AH02572: Failed to configure at least one certificate and key for ::1:443
[Thu Mar 26 09:26:02.010184 2020] [ssl:emerg] [pid 19986] SSL Library Error: error:140A80B1:SSL routines:SSL_CTX_check_private_key:no certificate assigned
[Thu Mar 26 09:26:02.010200 2020] [ssl:emerg] [pid 19986] AH02311: Fatal error initialising mod_ssl, exiting. See /var/log/apache2/error.log for more information
AH00016: Configuration Failed
[Thu Mar 26 10:25:37.475828 2020] [ssl:emerg] [pid 20618] AH02572: Failed to configure at least one certificate and key for ::1:443
[Thu Mar 26 10:25:37.475970 2020] [ssl:emerg] [pid 20618] SSL Library Error: error:140A80B1:SSL routines:SSL_CTX_check_private_key:no certificate assigned
[Thu Mar 26 10:25:37.475987 2020] [ssl:emerg] [pid 20618] AH02311: Fatal error initialising mod_ssl, exiting. See /var/log/apache2/error.log for more information
AH00016: Configuration Failed
Cliquez pour agrandir...

<VirtualHost 192.168.1.93:80>

DocumentRoot /mnt/md0/nextcloud
ServerName piaa.ddnsfree.com

Alias /nextcloud "/mnt/md0/nextcloud"

<Directory /mnt/md0/nextcloud>
Options +FollowSymlinks
AllowOverride All
Order allow,deny
Allow from all
<IfModule mod_dav.c>
Dav off
</IfModule>

SetEnv HOME /mnt/md0/nextcloud
SetEnv HTTP_HOME /mnt/md0/nextcloud
</Directory>

ErrorLog /var/log/apache2/nextcloud-error_log
CustomLog /var/log/apache2/nextcloud-access_log common

</VirtualHost>
Cliquez pour agrandir...

Si il y a des données sensibles, tu me dis quand tu as récupéré que j'efface :)
 
Le default-ssl.conf:

<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

</VirtualHost>
</IfModule>

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
Cliquez pour agrandir...
 
Et enfin le config.php de nextcloud:

<?php
$CONFIG = array (
'passwordsalt' => 'PmgqJz34/gkQtovOIfXnNP5vmz6cTW',
'secret' => 'IEBe8PMa0T0n+hLJJHiGpP2KIDxpCITioBLRLcOqcm4lNug5',
'trusted_domains' =>
array (
0 => 'localhost',
1 => '185.94.189.189',
),
'datadirectory' => '/mnt/md0/nextcloud/data',
'dbtype' => 'mysql',
'version' => '18.0.3.0',
'overwrite.cli.url' => 'http://localhost',
'dbname' => 'nextcloud',
'dbhost' => 'localhost',
'dbport' => '',
'dbtableprefix' => 'oc_',
'mysql.utf8mb4' => true,
'dbuser' => 'nextcloud_user',
'dbpassword' => 'xxxxxx',
'installed' => true,
'memcache.local' => '\\OC\\Memcache\\APCu',
'instanceid' => 'oc7zi0wwkeev',
);
Cliquez pour agrandir...
 
ouille ouille ouille...
alors une bonne pratique, avant de modifier un fichier de config, on en fait une copie
Code: 
sudo cp filename filename.bckp
cette commande copie le fichier "filename" vers "filename.bckp"
pour pouvoir faire un rollback rapide

Ensuite, pour ce qui fonctionne on fait de la documentation, ne fût ce que basique exemple ci-dessous la doc que j'avais faite quand j'ai créé ma VM template Debian 9
Code: 
1vcpu, 10go, 256mo
langue englsih, kb be
ssh server & standard util


install net-tools, htop, nano, snmpd, dfc, qemu-guest-agent, bash-completion

nano /etc/bash.bashrc Rechercher la ligne # enable bash completion in interactive shell et supprimer les dièses (#) sur la portion de code après cette ligne jusqu'au dernier fi. Ce qui doit donner au final :

Extrait de bash.bashrc

    # enable bash completion in interactive shells
    if ! shopt -oq posix; then
      if [ -f /usr/share/bash-completion/bash_completion ]; then
        . /usr/share/bash-completion/bash_completion
      elif [ -f /etc/bash_completion ]; then
        . /etc/bash_completion
      fi
    fi




systemctl enable qemu-guest-agent
systemctl start qemu-guest-agent

config apt-cacher
nano /etc/apt/apt.conf.d/01acng

Acquire::http {
Proxy "http://192.168.10.59:9999";
};


                                  config snmp
avec tout ça je sais assez facilement refaire mon template, je ne dis pas que tout y est mais j'ai une trace de tout

Revenons en à nos moutons !

d’abord
Code: 
<?php
$CONFIG = array (
'passwordsalt' => 'PmgqJz34/gkQtovOIfXnNP5vmz6cTW',
'secret' => 'IEBe8PMa0T0n+hLJJHiGpP2KIDxpCITioBLRLcOqcm4lNug5',
'trusted_domains' =>
array (
0 => 'localhost',
1 => '185.94.189.189',
),
met l'ip de ton réseau 192.168.1.* à la place du 185.94.189.189 ça permettra d'arriver à accèder à ton nextcloud depuis ton lan.

ensuite tu fais 2=>'http://piaa.ddnsfree.com/,

commence par ça puis reboot ton server, pour voir ce que ça dit


enfin ton ddns est mal configuré, au lieu de renvoyer ton ip wan (qui est j'imagine le 185.94.189.189, il renvoi une IP lan sur ton réseau (je ping piaa.ddnnsfree.com) ça répond 192.168.1.93
 
il manque l'un ou l'autre fichier restaurer, que donne le journalctl -xe?
tu as regardé avec la commande history, qui liste toutes les commandes tapées dans le shell, tous les fichiers modifiés?
 
Trop beaucoup trop.

De toute façon le problème ne doit pas être bien grave.

apache est correctement installé. Tout le reste avant aussi... (php, maria et cie...) nextcloud pareil, puisque j'ai pu y accéder.

Donc c'est juste un souci d'accès, de lancement de apache, on est d'accord ? Je ne vois pas de quel fichier restauré tu parles ? Enfin restauré je ne saisi pas bien...
 
ma conjugaison était mauvaise
je voulais dire : il reste l'un ou l'autre fichier à restaurer
donc y remettre sa config précédante.

Mon avis est qu'il faut fixer ce soucis d'apache avant de continuer, mais libre à toi de continuer en ayant ce soucis comme épée de Damocles
 
C'est à dire je n'ai pas le choix ^^

Le second fichier serait VirtualHost ?

Laisse tomber, je vais recommencer depuis le début. Trop le bordel. Et je prendrai bien des notes comme tu le suggérais mais voilà quoi, pour moi l'exemple que tu m'as mis de la VM debian, c'est du chinois...
 
non l'exemple c'est juste une doc que je me suis faite il y a quelques temps, ne te base pas dessus, mais inspire toi de ca, note ce que tu fais.
Pour mon boulot je suis amené à écrire de la doc très régulièrement, et elles sont bien plus complètes que celle la !
 
C'est bon, NC et apache semblent tourner comme il faut.

On va enfin pouvoir passer la partie partage extérieur ;)

Bonne nuit
 
alors ce qu'il faudrait tester maintenant c'est
- ton nextcloud via l'ip locale (de mémoire 192.168.1.50)
- ton nextcloud via l'ip externe (celle en XXX.189.189)
- ton nextcloud via le nom de domaine

faudra aussi passer par l'activation du HTTPS, mais allons y étape, par étape ;)
et note ce que tu fait, et backupe les fichiers de config avant de les changer ;)
 
Hello

encore merci de suivre mon install et d'être à mes côtés la dedans :) Ca fait plaisir des gens désintéressés comme toi :love:

Pour l'accès avec les différentes adresses, à priori ça a l'air de passer de ce que je constate.

En tout cas Nextcloud s'ouvre depuis mes 2 postes de travail (fixe et portable), faut que je teste en 4g, après est-ce que tu parles de l'accès via web browser ou bien de l'accès avec le desktop ?

J'ai bien pris quelques notes, mais c'est pas aussi structuré et expliqué que ton modèle.

Sinon je voulais savoir y'a moyen de "monter" ou "montrer" le nas dans Nextcloud ? Je ne vois que l'espace système de la carte SD...

Merci
 
je parle des tests via browser pour le moment
pour le stockage, c'est expliqué ici
https://help.nextcloud.com/t/howto-change-move-data-directory-after-installation/17170
en gros modifier le fichier config.php (pense à le sauver avant)
et lancer les commande occ décrites
encore merci de suivre mon install et d'être à mes côtés la dedans :) Ca fait plaisir des gens désintéressés comme toi :love:
Cliquez pour agrandir...
t'inquiète je compte mes heures, la facture suivra :giggle:
 
Comme j'ai réinstallé debian hier, je crois que j'ai perdu le montage de mon RAID...

Tu peux me confirmer ça:

root@helios4:~# lsblk -o NAME,SIZE,FSTYPE,TYPE,MOUNTPOINT
NAME SIZE FSTYPE TYPE MOUNTPOINT
sda 2.7T linux_raid_member disk
└─md127 8.2T ext4 raid5
sdb 2.7T linux_raid_member disk
└─md127 8.2T ext4 raid5
sdc 2.7T linux_raid_member disk
└─md127 8.2T ext4 raid5
sdd 2.7T linux_raid_member disk
└─md127 8.2T ext4 raid5
mmcblk0 14.7G disk
└─mmcblk0p1 14.5G ext4 part /
zram0 50M disk /var/log
zram1 1007.9M disk [SWAP]
Cliquez pour agrandir...

Le système de fichiers semble toujours là mais pas le point de montage ?

Je pars là dessus:

Create a mount point to attach the new filesystem:

sudo mkdir -p /mnt/md0
Cliquez pour agrandir...

You can mount the filesystem by typing:

sudo mount /dev/md0 /mnt/md0
Cliquez pour agrandir...

? En remplaçant md0 par 127 ?
 
Ca fait un peu peur le topic, ils disent tous, que c'est pas conseillé de changer le dossier de stockage après installation, qu'il faut le faire pendant, donc désinstaller NC et recommencer...
 
on repart de 0?
tceupa.gif


ici aussi ils en parlent
https://help.nextcloud.com/t/is-there-a-safe-and-reliable-way-to-move-data-directory-out-of-web-root/3642/4
comme tu n'as encore aucune données, il faut tenter le coup, je pense l'avoir fait une fois, je ne me souviens pas avoir eu de soucis
 
webmail a dit:
on repart de 0?
tceupa.gif
Cliquez pour agrandir...

Non merci, mais j'ai bien ri ^^

Bon 1 et 2 OK, pas de cron jobs (à ma connaissance, je n'ai rien programmé du moins) et apache stoppé.

Maintenant je ne capte pas, ils me disent de déplacer /data, si je regarde dans /var/www/html/nextcloud/data, j'ai plein de dossiers et fichiers ? C'est normal ? Je m'attendais à trouver un dossier data vide...
 
Vous devez vous connecter ou vous enregistrer pour répondre ici.
Haut Bas
Retour