• Benvenuti su RaspberryItaly!
Benvenuto ospite! Login Login con Facebook Registrati Login with Facebook


Valutazione discussione:
  • 0 voto(i) - 0 media
  • 1
  • 2
  • 3
  • 4
  • 5

[-]
Tags
a da https reindirizzamento http

Reindirizzamento da http a https
#11
(28/01/2019, 11:39)Tiger Ha scritto: modifica il file con queste direttive qui


Codice:
<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
       
       ServerName  murdock984.dlinkddns.com
       ServerAlias murdock984.dlinkddns.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
RewriteEngine on
RewriteCond %{SERVER_NAME} =Murdock984.dlinkddns.com

RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]
</VirtualHost>

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

Dovresti avere anche un altro file di configurazione per la https porta 443

Aggiornato il file, mentre quello per la configurazione per la https? Dove lo trovo?

Inviato dal mio BKL-L09 utilizzando Tapatalk
Risposta
#12
se tu avessi creato correttamente i certificati let's encrypt dovresti avere un file secondario vabbè mo te lo generò io il file secondario che va comunque abilitato con il comando a2ensite e nome del file scrivimi anche il nome del file attuale che c'hai che stai devi modificare
Risposta
#13
(28/01/2019, 11:55)Tiger Ha scritto: se tu avessi creato correttamente i certificati let's encrypt dovresti avere un file secondario vabbè mo te lo generò io il file secondario che va comunque abilitato con il comando a2ensite e nome del file scrivimi anche il nome del file attuale che c'hai che stai devi modificare
Se intendi il file all'interno della cartella etc/apache2/ssl si chiama Apache.crt e ne ho un'altro con estensione. key

Inviato dal mio BKL-L09 utilizzando Tapatalk
Risposta
#14
No sempre in Site avaiable, ma tu hai generato certificati con Lets encrypt?
Risposta
#15
(28/01/2019, 12:24)Tiger Ha scritto: No sempre in Site avaiable, ma tu hai generato certificati con Lets encrypt?
No adesso la procedura non la ricordo ho seguito una guida su pimylifeup su come installare nextcloud... E alla fine spiegava come configurare i certificati. Cmq ho solo due file 000-default.conf e default-ssl.conf

Inviato dal mio BKL-L09 utilizzando Tapatalk
Risposta
#16
(28/01/2019, 12:37)Murdock84 Ha scritto:
(28/01/2019, 12:24)Tiger Ha scritto: No sempre in Site avaiable, ma tu hai generato certificati con Lets encrypt?
No adesso la procedura non la ricordo ho seguito una guida su pimylifeup su come installare nextcloud... E alla fine spiegava come configurare i certificati. Cmq ho solo due file 000-default.conf e default-ssl.conf

Inviato dal mio BKL-L09 utilizzando Tapatalk

ho fatto una guida apposita qui per installare apache e db con nextcloud se l'avresti seguita casomai non ti perdevi per la via, comunque se nel file:

000-default.conf


hai inserito le voci che ti ho detto eliminado le tue nel secondo inserisci queste voci, presupponendo che almeno i certificati lets encrypts sia stati scaricati correttamente con il tuo dominio ddns


modifica file default-ssl.conf

Codice:
<IfModule mod_ssl.c>
<VirtualHost _default_:443>

ServerName  [color=#363636][size=small]murdock984.dlinkddns.com[/size][/color]
                ServerAlias [color=#363636][size=small]murdock984.dlinkddns.com[/size][/color]
                ServerAdmin webmail@com

DocumentRoot /var/www/html/

<IfModule mod_headers.c>
  Header always set Referrer-Policy "no-referrer"
  Header always set Strict-Transport-Security "max-age=15552000; includeSubDomains"
</IfModule>


# 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
SSLCertificateFile /etc/letsencrypt/live/[color=#363636][size=small]murdock984.dlinkddns.com[/size][/color]/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/[color=#363636][size=small]murdock984.dlinkddns.com[/size][/color]/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf

</VirtualHost>
</IfModule>

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

poi dai il comando

sudo a2ensite default-ssl.conf

e

sudo a2ensite 000-default.conf

ciao
Risposta
#17
(28/01/2019, 13:01)Tiger Ha scritto:
(28/01/2019, 12:37)Murdock84 Ha scritto:
(28/01/2019, 12:24)Tiger Ha scritto: No sempre in Site avaiable, ma tu hai generato certificati con Lets encrypt?
No adesso la procedura non la ricordo ho seguito una guida su pimylifeup su come installare nextcloud... E alla fine spiegava come configurare i certificati. Cmq ho solo due file 000-default.conf e default-ssl.conf

Inviato dal mio BKL-L09 utilizzando Tapatalk

ho fatto una guida apposita qui per installare apache e db con nextcloud se l'avresti seguita casomai non ti perdevi per la via, comunque se nel file:

000-default.conf


hai inserito le voci che ti ho detto eliminado le tue nel secondo inserisci queste voci, presupponendo che almeno i certificati lets encrypts sia stati scaricati correttamente con il tuo dominio ddns


modifica file default-ssl.conf

Codice:
<IfModule mod_ssl.c>
<VirtualHost _default_:443>

ServerName  [color=#363636][size=small]murdock984.dlinkddns.com[/size][/color]
                ServerAlias [color=#363636][size=small]murdock984.dlinkddns.com[/size][/color]
                ServerAdmin webmail@com

DocumentRoot /var/www/html/

<IfModule mod_headers.c>
  Header always set Referrer-Policy "no-referrer"
  Header always set Strict-Transport-Security "max-age=15552000; includeSubDomains"
</IfModule>


# 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
SSLCertificateFile /etc/letsencrypt/live/[color=#363636][size=small]murdock984.dlinkddns.com[/size][/color]/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/[color=#363636][size=small]murdock984.dlinkddns.com[/size][/color]/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf

</VirtualHost>
</IfModule>

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

poi dai il comando

sudo a2ensite default-ssl.conf

e

sudo a2ensite 000-default.conf

ciao
Ho sostituito il testo del file ma non cambia nulla

Inviato dal mio BKL-L09 utilizzando Tapatalk
Risposta
#18
Purtroppo ho necessità di controllare via SSH e capire dove hai commesso errori

In Pvt se vuoi trascriviamo i dati per accesso. Ciao

Spero il post sia scritto correttamente se c'è qlc errore nella richiesta modificatelo.

Prova anche a riavviare apache2

sudo systemctl restart apache2
Risposta
  


Vai al forum:


Navigazione: 1 Ospite(i)
Forum con nuovi Post
Forum senza nuovi post
Forum bloccato
Forum Redirect