Quantcast
Channel: Kaltura - Latest posts
Viewing all articles
Browse latest Browse all 7410

Best way to change kaltura 11.2.0 using http to use https

$
0
0

apachectl -t -DDUMP_VHOSTS

AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
VirtualHost configuration:
127.0.1.1:443          streaming.example.fr (/etc/apache2/sites-enabled/zzzkaltura.ssl.conf:22)

configuration :

<IfModule !ssl_module>
        LoadModule ssl_module modules/mod_ssl.so
</IfModule>


SSLPassPhraseDialog  builtin
SSLSessionCache         shmcb:/var/cache/mod_ssl/scache(512000)
SSLSessionCacheTimeout  300
SSLRandomSeed startup file:/dev/urandom  256
SSLRandomSeed connect builtin
<IfVersion < 2.4>
        SSLMutex default
</IfVersion>
<IfVersion >= 2.4>
        Mutex sysvsem default
</IfVersion>
SSLCryptoDevice builtin

SSLCertificateFile /etc/ssl/mexamplecerts/exampleWild-Cert.pem
SSLCertificateKeyFile /etc/ssl/mexampleprivate/exampleWild-key.pem
SSLCertificateChainFile /etc/ssl/mexamplecerts/exampleWild-ChaineCertif.pem
<VirtualHost streaming.example.fr:443>
        SSLEngine on
        SSLProtocol all -SSLv2
        SSLCipherSuite ALL:!ADH:!EXPORT:!SSLv2:RC4+RSA:+HIGH:+MEDIUM:+LOW

        ErrorLog "/opt/kaltura/log/kaltura_apache_errors_ssl.log"
        CustomLog /opt/kaltura/log/kaltura_apache_access_ssl.log vhost_kalt

        Include "/opt/kaltura/app/configurations/apache/conf.d/enabled.*.conf"
</VirtualHost>

curl:

curl -I -v https://streaming.example.fr/api_v3
* Hostname was NOT found in DNS cache
*   Trying 127.0.1.1...
* Connected to streaming.example.fr (127.0.1.1) port 443 (#0)
* successfully set certificate verify locations:
*   CAfile: none
  CApath: /etc/ssl/certs
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server key exchange (12):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using ECDHE-RSA-AES256-GCM-SHA384
* Server certificate:
*        subject: C=FR; postalCode=76037; ST=Seine-Maritime; L=example; street=2 PLACE DU GENERAL DE GAULLE; O=COMMUNE DE example; OU=0002 217605401; CN=*.example.fr
*        start date: 2016-04-22 00:00:00 GMT
*        expire date: 2017-04-22 23:59:59 GMT
*        subjectAltName: streaming.example.fr matched
*        issuer: C=GB; ST=Greater Manchester; L=Salford; O=COMODO CA Limited; CN=COMODO RSA Organization Validation Secure Server CA
*        SSL certificate verify ok.
> HEAD /api_v3 HTTP/1.1
> User-Agent: curl/7.35.0
> Host: streaming.example.fr
> Accept: */*
>
< HTTP/1.1 301 Moved Permanently
HTTP/1.1 301 Moved Permanently
< Date: Thu, 19 Jan 2017 15:32:19 GMT
Date: Thu, 19 Jan 2017 15:32:19 GMT
* Server Apache/2.4.7 (Ubuntu) is not blacklisted
< Server: Apache/2.4.7 (Ubuntu)
Server: Apache/2.4.7 (Ubuntu)
< Location: https://streaming.example.fr/api_v3/
Location: https://streaming.example.fr/api_v3/
< Content-Type: text/html; charset=iso-8859-1
Content-Type: text/html; charset=iso-8859-1

<
* Connection #0 to host streaming.example.fr left intact

Viewing all articles
Browse latest Browse all 7410

Trending Articles