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

Nginx Setup Help

$
0
0

curl https://server/api_v3 returns this:

<?xml version="1.0" encoding="utf-8"?><xml><result><error><code>SERVICE_NOT_SPECIFIED</code><message>Service name was not specified, please specify one</message><objectType>KalturaAPIException</objectType><args></args></error></result><executionTime>0.024806976318359</executionTime></xml>

When I hit play, I can see in the browser console that my sample video is requesting: https://server.ca:8443/hls/p/100/sp/10000/serveFlavor/entryId/0_um16sz7y/v/12/flavorId/0_w9x78t15/name/a.mp4/index.m3u8

Is that what you meant? or did you want a log from the server? The browser console also gives the note about the Access-Control-Allow-Origin header missing.

Hitting that with curl -v gives:

 About to connect() to server.ca port 8443 (#0)
   Trying XXX.XXX.XXX.XXX...
 Connected to server.ca (XXX.XXX.XXX.XXX) port 8443 (#0)
 Initializing NSS with certpath: sql:/etc/pki/nssdb
   CAfile: /etc/pki/tls/certs/ca-bundle.crt
 CApath: none
 SSL connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 Server certificate:
       subject: CN=server.ca,O=,L=,ST=,C=CA
       start date:  GMT
       expire date:  GMT
       common name: server.ca
       issuer: CN=GlobalSign Organization Validation CA - SHA256 - G2,O=GlobalSign nv-sa,C=BE
 GET /hls/p/100/sp/10000/serveFlavor/entryId/0_um16sz7y/v/12/flavorId/0_w9x78t15/name/a.mp4/index.m3u8 HTTP/1.1
 User-Agent: curl/7.29.0
 Host: server.ca:8443
 Accept: */*

 HTTP/1.1 404 Not Found
 Server: nginx/1.13.12
 Date: Thu, 07 Jun 2018 20:24:43 GMT
 Content-Type: text/html
 Content-Length: 170
 Connection: keep-alive

html>
head><title>404 Not Found</title></head>
body bgcolor="white">
center><h1>404 Not Found</h1></center>
hr><center>nginx/1.13.12</center>
/body>
/html>
 Connection #0 to host server.ca left intact

I did, however, discover why the server.ca directive in my virtual host wasn’t working. A long, long time ago, you used to have to add an entry to the hosts file on the server that looked like: 127.0.0.1 fqdn, which I must have added out of habit. Now that I’ve removed it, the virtual host is fine with the fqdn listed.

If you’d like more info for further testing (like the servername to try and an actual embed), please let me know and I can always email that to you.


Viewing all articles
Browse latest Browse all 7410

Trending Articles