An error occurred (error code: API:-1) when logging in to admin panel

1

Results of sanity check

[root@emlnx-media1 opt]# /opt/kaltura/bin/kaltura-sanity.sh
[Space on /] [PASSED, RC: 0] - [.006298485]
[Space on /opt/kaltura/web] [PASSED, RC: 0] - [.006245597]
[Check httpd daemon status] [PASSED, RC: 0] - [.056101782]
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
[Check httpd daemon is started by Monit] [PASSED, RC: 0] - [7.630149438]
[check daemon httpd init status] [PASSED, RC: 0] - [.008659890]
[Check kaltura-sphinx daemon status] [PASSED, RC: 0] - [.057304736]
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
[Check kaltura-sphinx daemon is started by Monit] [PASSED, RC: 0] - [6.062098121]
[check daemon kaltura-sphinx init status] [PASSED, RC: 0] - [.008825758]
[Check kaltura-batch daemon status] [PASSED, RC: 0] - [.059974283]
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
[Check kaltura-batch daemon is started by Monit] [PASSED, RC: 0] - [5.390668611]
[check daemon kaltura-batch init status] [PASSED, RC: 0] - [.004517058]
[Check kaltura-monit daemon status] [PASSED, RC: 0] - [.053379562]
[check daemon kaltura-monit init status] [PASSED, RC: 0] - [.008246079]
[Check memcached daemon status] [PASSED, RC: 0] - [.051863578]
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it..
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it..
[Check memcached daemon is started by Monit] [PASSED, RC: 0] - [4.428014508]
[check daemon memcached init status] [PASSED, RC: 0] - [.009881940]
[kaltura-html5lib ver in KMC config.ini] [PASSED, RC: 0] - [.205242687]
[kaltura-kdp3 ver in KDP3 config.ini] [PASSED, RC: 0] - [.098520849]
[kaltura-kmc ver in KMC config.ini] [PASSED, RC: 0] - [.094168758]
[Get KMC SWFs] [PASSED, RC: 0] - [2.139711232]
[check_testme_page] [PASSED, RC: 0] - [15.602902063]
[check_kmc_index_page] [PASSED, RC: 0] - [.233748773]
[check_admin_console_index_page] [PASSED, RC: 0] - [.656305892]
[check_studio_index_page] [PASSED, RC: 0] - [1.320023851]
[check_clipapp_index_page] [PASSED, RC: 0] - [1.446030208]
[Create Partner] [FAILED, RC: 255] - [.397360284]
Partner creation failed. I will skip all tests that require it.
[Red5 file upload] [SKIPPED as OflaDemo isn't configured]
see: https://github.com/kaltura/platform-install-packages/blob/master/doc/install-kaltura-redhat-based.md#configure-red5-server


Results of kaltlog
    2016-08-04 10:03:29 [409431079] [Kaltura_Client_ClientBase->doCurl] DEBUG: curl: https://emlnx-media1.domain.org/api_v3/index.php?service=user&action=loginByLoginId&apiVersion=3.1.6&format=2&clientTag=Kaltura-admin&ignoreNull=1&loginId=rpelletier%40domain.org&password=3xc%40l%21bur&partnerId=-2&privileges=disableentitlement&kalsig=8216e16655cdfc987fac6468b282b809
    2016-08-04 10:03:29 [409431079] [ErrorController->errorAction] ERR: exception 'Kaltura_Client_ClientException' with message 'Peer certificate cannot be authenticated with known CA certificates. RC : 0' in /opt/kaltura/app/admin_console/lib/Kaltura/Client/ClientBase.php:239
    Stack trace:
    #0 /opt/kaltura/app/admin_console/lib/Kaltura/Client/UserService.php(177): Kaltura_Client_ClientBase->doQueue()

==> /opt/kaltura/log/kaltura_apache_errors_ssl.log <==
[Thu Aug 04 10:03:29 2016] [error] [client 10.40.4.138] File does not exist: /opt/kaltura/app/alpha/web/opt, referer: https://emlnx-media1.domain.org/admin_console/index.php/user/login

--
==> /opt/kaltura/log/batch/deletefile-0-2016-08-04.err.log <==
PHP Fatal error:  Class 'KalturaScheduledTaskProfileService' not found in /opt/kaltura/app/batch/client/KalturaPlugins/KalturaScheduledTaskClientPlugin.php on line 227

--
==> /opt/kaltura/log/batch/movecategoryentries-0-2016-08-04.err.log <==
PHP Fatal error:  Class 'KalturaScheduledTaskProfileService' not found in /opt/kaltura/app/batch/client/KalturaPlugins/KalturaScheduledTaskClientPlugin.php on line 227

‘’’

2

It never fails, as soon as I post something in the forum, I finally find the answer.

/opt/kaltura/app/configurations/admin.ini, by removing the ; comment on this line :;settings.clientConfig.verifySSL = false

the above fixed it. I do not think Kaltura likes my wildcard certificate.

3

Hi,

You should edit /opt/kaltura/app/configurations/apache/kaltura.ssl.conf and set:
SSLCertificateFile @SSL_CERTIFICATE_FILE@
SSLCertificateKeyFile @SSL_CERTIFICATE_KEY_FILE@
SSLCACertificateFile @SSL_CERTIFICATE_CHAIN_FILE@

Kaltura has no problem working with wildcard certs. It uses curl to make the HTTP requests, you need to add the CA and then test with:
$ curl -I -v https://emlnx-media1.domain.org/api_v3/index.php?service=ping
I don’t know if emlnx-media1.domain.org is your actual domain or not, if it is, then for it, I am getting:

  • Server certificate:
  •    subject: OU=Domain Control Validated; OU=COMODO SSL Wildcard; CN=*.domain.com

  •    start date: 2016-05-10 00:00:00 GMT

  •    expire date: 2019-06-12 23:59:59 GMT

  •    subjectAltName does not match emlnx-media1.domain.org
  • SSL: no alternative certificate subject name matches target host name ‘emlnx-media1.domain.org’
  • Closing connection 0
  • SSLv3, TLS alert, Client hello (1):
    curl: (51) SSL: no alternative certificate subject name matches target host name ‘emlnx-media1.domain.org’

So, seems the wildcard cert is for *.domain.com not *.domain.org, hence the cert mismatch and the problem.
You will see the same when trying to make the request on the browser.

4

Hi,

You can edit:
/opt/kaltura/web/content/clientlibs/php5/KalturaClientBase.php
and instead of:

                // Set SSL verification
                if(!$this->getConfig()->verifySSL)
                {
                        curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
                        curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, 2);
                }
                elseif($this->getConfig()->sslCertificatePath)
                {
                        curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, true);
                        curl_setopt($ch, CURLOPT_CAINFO, $this->getConfig()->sslCertificatePath);
                }

just have:

                        curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
                        curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, 2);

Also, need to set:
settings.clientConfig.verifySSL = false
in /opt/kaltura/app/configurations/admin.ini

But I would highly recommend using a valid cert. You can easily generate them for free using https://letsencrypt.org/

5

@jess

I am getting this error after installing the new update and running reconfiguration from scratch to attempt to resolve my admin user authentication issue. However, I reran the install as non-secure to see if I could login and I got an authentication error again. So it does not matter if I install the platform as secure or unsecure I still can’t login.

--
==> /opt/kaltura/log/kaltura_admin.log <==
2016-11-21 21:51:21 [0.026524] [973174675] [26] [%context%] [ErrorController->errorAction] ERR: exception 'Kaltura_Client_ClientException' with message '. RC : 0' in /opt/kaltura/app/admin_console/lib/Kaltura/Client/ClientBase.php:919
Stack trace:
#0 /opt/kaltura/app/admin_console/lib/Kaltura/Client/ClientBase.php(249): Kaltura_Client_ClientBase->getKalturaClientException('. RC : 0', -1)
--
==> /opt/kaltura/log/kaltura_apache_errors_ssl.log <==
[Mon Nov 21 21:51:21 2016] [error] [client 24.49.36.237] File does not exist: /opt/kaltura/app/alpha/web/opt, referer: https://cdn.hiphopservers.com/admin_console/index.php/user/login

--

My wildcard SSL is valid and loading without an issue.

6

I was able to resolve this issue by updating the URL in the following files to the valid SSL URL then my error stopped.

This SERVICE_URL is your API endpoint and is used in multiple places, including:
/opt/kaltura/app/configurations/batch/batch.ini
/opt/kaltura/app/configurations/admin.ini
/opt/kaltura/app/configurations/local.ini

7

@jess

I am getting this error again and kaltlog reports:

--
2017-07-23 14:02:00 [0.000088] [931250229] [7] [%context%] [Kaltura_Client_ClientBase->doCurl] DEBUG: post: {"format":"2","ignoreNull":true,"clientTag":"Kaltura-admin","apiVersion":"3.3.0","loginId":"user@mydomain.com","password":"PRIVATE","partnerId":"-2","privileges":"disableentitlement","otp":"","kalsig":"6bbea92a1f1ed03bda29cdbd31816361"}
2017-07-23 14:02:00 [0.116575] [931250229] [8] [%context%] [ErrorController->errorAction] ERR: exception 'Kaltura_Client_ClientException' with message '. RC : 0' in /opt/kaltura/app/admin_console/lib/Kaltura/Client/ClientBase.php:919
Stack trace:
#0 /opt/kaltura/app/admin_console/lib/Kaltura/Client/ClientBase.php(249): Kaltura_Client_ClientBase->getKalturaClientException('. RC : 0', -1)

However, when I test my cert I get the following results:

https://www.sslshopper.com/ssl-checker.html?host=cdn.hiphopservers.com#hostname=cdn.hiphopservers.com

# curl -I -v https://cdn.hiphopservers.com/api_v3/index.php?service=ping

  • About to connect() to cdn.hiphopservers.com port 443 (#0)
    * Trying 64.187.229.43…
    * Connected to cdn.hiphopservers.com (64.187.229.43) port 443 (#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=*.hiphopservers.com,OU=Domain Control Validated
    * start date: Feb 21 00:28:50 2017 GMT
    * expire date: Apr 12 06:29:57 2020 GMT
    * common name: *.hiphopservers.com
    * issuer: CN=AlphaSSL CA - SHA256 - G2,O=GlobalSign nv-sa,C=BE
    HEAD /api_v3/index.php?service=ping HTTP/1.1
    User-Agent: curl/7.29.0
    Host: cdn.hiphopservers.com
    Accept: / 
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Date: Sun, 23 Jul 2017 18:07:18 GMT
Date: Sun, 23 Jul 2017 18:07:18 GMT
< Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips PHP/5.4.16
Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips PHP/5.4.16
< X-Powered-By: PHP/5.4.16
X-Powered-By: PHP/5.4.16
< Access-Control-Expose-Headers: Server, Content-Length, Content-Range, Date, X-Kaltura, X-Kaltura-Session, X-Me
Access-Control-Expose-Headers: Server, Content-Length, Content-Range, Date, X-Kaltura, X-Kaltura-Session, X-Me
< Access-Control-Allow-Origin: *
Access-Control-Allow-Origin: *
< Expires: Sun, 19 Nov 2000 08:52:00 GMT
Expires: Sun, 19 Nov 2000 08:52:00 GMT
< Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
< Pragma: no-cache
Pragma: no-cache
< X-Kaltura: cache-key,cache_v3-20479ed86bf0fe783738ded70cb04101
X-Kaltura: cache-key,cache_v3-20479ed86bf0fe783738ded70cb04101
< X-Me: cdn.hiphopservers.com
X-Me: cdn.hiphopservers.com
< Content-Type: text/xml
Content-Type: text/xml
<
* Connection #0 to host cdn.hiphopservers.com left intact

Can you help identify what I am missing? All the caption settings to disable the check are applied by default. I am not sure why the results I am getting different on this installation other than I am running CentOS 7.3.1 with Kaltura CE v12.19.0 so I can migrate my previous CentOS 6.5.9 installation to the new host before upgrading to the latest version.

::: UPDATE ::::

My ISP suggested that the issue is actually with the version of CURL I am running on the host. As they ran the same CURL command from a different host with the latest version of CURL and got no errors. So my SSL is actually setup correctly but the version of CURL installed by Kaltura CE for CentOS 7.3.1 is not returning proper results.

I tried to disable this check of the SSL by the script but with no success.

8

After making the changes mention:

I change the current line in this file from:

; settings.clientConfig.verifySSL = false

to

settings.clientConfig.verifySSL = false

Specifically, removing the “;” from the the front of the line which was the equivalent of commenting out the line and this fixed the issue. As I mention this issue in my instance was not cause by the SSL being invalid but because the version of curl for CentOS 7.3.1 installed and compiled with PHP curl is not the latest version which cause this error.

9

Hi @hiphopservers,

When running the below snippet from a machine with:

# cat /etc/redhat-release 
CentOS Linux release 7.3.1611 (Core)

# rpm -qf /usr/lib64/php/modules/curl.so 
php-common-5.4.16-42.el7.x86_64

<?php
        $url = 'https://cdn.hiphopservers.com/api_v3/index.php?service=ping';
        $session = curl_init();
        curl_setopt($session, CURLOPT_URL, $url);
        curl_setopt($session, CURLOPT_HTTPGET, 1);
        curl_setopt($session, CURLOPT_HEADER, true);
        curl_setopt($session, CURLOPT_RETURNTRANSFER, true);
        curl_setopt($session, CURLOPT_VERBOSE, 1);
        curl_setopt($session, CURLOPT_SSL_VERIFYPEER, true);
        $response = curl_exec($session);
        $httpcode = curl_getinfo($session, CURLINFO_HTTP_CODE);
        curl_close($session);
        return $httpcode;

I get a proper HTTP 200 response. What are you getting from yours? While setting:

curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);

Is not the end of the world, it is best to avoid. Better understand the root cause and correct it.

10

@jess

I am not sure I understand your question because I follow the instructions to disable the check and the errors stopped with just the caption setting:

My review of my original install shows I disable this check as described but this time I didn’t change the setting in properly.

After making this change everything worked as expected. Now, as to why it is not working well as I said my ISP investigated using a different version of CURL (newer version) from another host and no error was return with the verification enabled.

11

Hi @hiphopservers,

What’s the cURL version with which it is failing?
If the snippet above works with some curl versions and fails with yours, obviously the issue is not in the Kaltura SSL configuration but I would still advise that you look into that since it’s best not to disable the certificate verification.

12

@jess

My version of CentOS and CURL are:

# cat /etc/redhat-release 
CentOS Linux release 7.3.1611 (Core)

# rpm -qf /usr/lib64/php/modules/curl.so 
php-common-5.4.16-42.el7.x86_64

I have even tried a fresh installation of the OS to resolve this issue and reinstalled a fresh copy of Kaltura CE.

13

Hi @hiphopservers,

So the problem is not the cURL PHP extension since I have the exact same one and the snippet I attached above results in the output below.

It could be that you have a different version of the curl lib itself… what’s the output for:

# ldd /usr/lib64/php/modules/curl.so |grep curl
        libcurl.so.4 => /lib64/libcurl.so.4 (0x00007fe102a5d000)

# rpm -qf /lib64/libcurl.so.4
libcurl-7.29.0-35.el7.x86_64
  • About to connect() to cdn.hiphopservers.com port 443 (#0)
  • Trying 64.187.229.43…
  • Connected to cdn.hiphopservers.com (64.187.229.43) port 443 (#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=*.hiphopservers.com,OU=Domain Control Validated

  •   start date: Feb 21 00:28:50 2017 GMT

  •   expire date: Apr 12 06:29:57 2020 GMT

  •   common name: *.hiphopservers.com

  •   issuer: CN=AlphaSSL CA - SHA256 - G2,O=GlobalSign nv-sa,C=BE

GET /api_v3/index.php?service=ping HTTP/1.1
Host: cdn.hiphopservers.com
Accept: /

< HTTP/1.1 200 OK
< Date: Tue, 25 Jul 2017 10:32:19 GMT
< Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips PHP/5.4.16
< X-Powered-By: PHP/5.4.16
< Access-Control-Expose-Headers: Server, Content-Length, Content-Range, Date, X-Kaltura, X-Kaltura-Session, X-Me
< X-Kaltura: cached-dispatcher,cache_v3-20479ed86bf0fe783738ded70cb04101,0.00012397766113281
< Access-Control-Allow-Origin: *
< Expires: Sun, 19 Nov 2000 08:52:00 GMT
< Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
< Pragma: no-cache
< X-Me: cdn.hiphopservers.com
< Content-Length: 381
< Content-Type: text/xml
<

Which is perfectly valid. What does it return in your case?

14

@jess

My output is a bit different.

# ldd /usr/lib64/php/modules/curl.so |grep curl
        libcurl.so.4 => /lib64/libcurl.so.4 (0x00007f7453bbe000)

# rpm -qf /lib64/libcurl.so.4
libcurl-7.29.0-35.el7.centos.x86_64

This command returns the following results:

curl -I -v https://cdn.hiphopservers.com/api_v3/index.php?service=ping

  • About to connect() to cdn.hiphopservers.com port 443 (#0)
  • Trying 64.187.229.43…
  • Connected to cdn.hiphopservers.com (64.187.229.43) port 443 (#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=*.hiphopservers.com,OU=Domain Control Validated

  •   start date: Feb 21 00:28:50 2017 GMT

  •   expire date: Apr 12 06:29:57 2020 GMT

  •   common name: *.hiphopservers.com

  •   issuer: CN=AlphaSSL CA - SHA256 - G2,O=GlobalSign nv-sa,C=BE

HEAD /api_v3/index.php?service=ping HTTP/1.1
User-Agent: curl/7.29.0
Host: cdn.hiphopservers.com
Accept: /

< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Date: Tue, 25 Jul 2017 10:47:32 GMT
Date: Tue, 25 Jul 2017 10:47:32 GMT
< Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips PHP/5.4.16
Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips PHP/5.4.16
< X-Powered-By: PHP/5.4.16
X-Powered-By: PHP/5.4.16
< Access-Control-Expose-Headers: Server, Content-Length, Content-Range, Date, X-Kaltura, X-Kaltura-Session, X-Me
Access-Control-Expose-Headers: Server, Content-Length, Content-Range, Date, X-Kaltura, X-Kaltura-Session, X-Me
< Access-Control-Allow-Origin: *
Access-Control-Allow-Origin: *
< Expires: Sun, 19 Nov 2000 08:52:00 GMT
Expires: Sun, 19 Nov 2000 08:52:00 GMT
< Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
< Pragma: no-cache
Pragma: no-cache
< X-Kaltura-Session: 940682654
X-Kaltura-Session: 940682654
< X-Kaltura: cache-key,cache_v3-20479ed86bf0fe783738ded70cb04101
X-Kaltura: cache-key,cache_v3-20479ed86bf0fe783738ded70cb04101
< X-Me: cdn.hiphopservers.com
X-Me: cdn.hiphopservers.com
< Content-Type: text/xml
Content-Type: text/xml

<

15

Hi @hiphopservers,

Your output seems perfectly valid as well.
I suggest you re-enable SSL verification, try to login and check the full error in /opt/kaltura/log/kaltura_admin.log and we can take it from there.

16

Okay, one moment I will update you shortly.

17

Also, just making sure here, does cdn.hiphopservers.com point to your Apache [where Kaltura Server is running] or is it an LB that does SSL offloading to the Kaltura Server’s Apache? From your output, seems like it’s the actual Apache where Kaltura is set up… if so, did you also set SSLCACertificateFile to point to your CA cert in /opt/kaltura//app/configurations/apache/kaltura.ssl.conf?

18

Hello @jess

Shows the following output.

2017-07-25 07:05:15 [0.000000] [1564188649] [1] [%context%] [FeedDropFolderPlugin::getTranslations] INFO: Loading file [/opt/kaltura/app/plugins/bulk_upload/drop_folder_xml/plugins/config/lang/en.php]
2017-07-25 07:05:15 [0.000413] [1564188649] [2] [%context%] [FeedDropFolderPlugin::getTranslations] INFO: Loading file [/opt/kaltura/app/plugins/bulk_upload/drop_folder_xml/plugins/config/lang/en.php]
2017-07-25 07:05:15 [0.000332] [1564188649] [3] [%context%] [FeedDropFolderPlugin::getTranslations] INFO: Loading file [/opt/kaltura/app/plugins/bulk_upload/drop_folder_xml/plugins/config/lang/en.php]
2017-07-25 07:05:15 [0.000338] [1564188649] [4] [%context%] [FeedDropFolderPlugin::getTranslations] INFO: Loading file [/opt/kaltura/app/plugins/bulk_upload/drop_folder_xml/plugins/config/lang/he.php]
2017-07-25 07:05:15 [0.004090] [1564188649] [5] [%context%] [Kaltura_Client_ClientBase->doQueue] DEBUG: service url: [https://cdn.hiphopservers.com]
2017-07-25 07:05:15 [0.000087] [1564188649] [6] [%context%] [Kaltura_Client_ClientBase->doCurl] DEBUG: curl: https://cdn.hiphopservers.com/api_v3/index.php/service/systempartner_systempartner/action/getPackages
2017-07-25 07:05:15 [0.000037] [1564188649] [7] [%context%] [Kaltura_Client_ClientBase->doCurl] DEBUG: post: {"format":"2","ignoreNull":true,"clientTag":"Kaltura-admin","apiVersion":"3.3.0","ks":"YjYyNmQxYzcyNDZiNmQ0MWJhYmFjYjRmNGM0N2RkM2EzMzY5ODcyN3wtMjstMjsxNTAxMDU1NDY2OzI7MTUwMDk2OTA2Ni4wMDM5O2FkbWluQGhpcGhvcHNlcnZlcnMuY29$
2017-07-25 07:05:15 [0.005155] [1564188649] [8] [%context%] [ErrorController->errorAction] ERR: exception 'Kaltura_Client_ClientException' with message '. RC : 0' in /opt/kaltura/app/admin_console/lib/Kaltura/Client/ClientBase.php:919
Stack trace:
#0 /opt/kaltura/app/admin_console/lib/Kaltura/Client/ClientBase.php(249): Kaltura_Client_ClientBase->getKalturaClientException('. RC : 0', -1)
#1 /opt/kaltura/app/admin_console/lib/Kaltura/Client/SystemPartner/SystemPartnerService.php(93): Kaltura_Client_ClientBase->doQueue()
#2 /opt/kaltura/app/admin_console/controllers/PartnerController.php(123): Kaltura_Client_SystemPartner_SystemPartnerService->getPackages()
#3 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Controller/Action.php(513): PartnerController->listAction()
#4 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Controller/Dispatcher/Standard.php(289): Zend_Controller_Action->dispatch('listAction')
#5 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Controller/Front.php(946): Zend_Controller_Dispatcher_Standard->dispatch(Object(Zend_Controller_Request_Http), Object(Zend_Controller_Response_Http))
#6 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Application/Bootstrap/Bootstrap.php(77): Zend_Controller_Front->dispatch()
#7 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Application.php(358): Zend_Application_Bootstrap_Bootstrap->run()
#8 /opt/kaltura/app/admin_console/web/index.php(38): Zend_Application->run()
#9 {main}

As for the configuration I have the sub domain pointing directly to the IP that running the Kaltura Server. The specific IP is an additional IP on the host and is NOT the system primary IP but my configuration files for NGINX listen specifically on that IP address. Apache Listens on all IPs on the host by default. My CA cert is defined and I did test it already to make sure it was setup correctly.

19

We need to understand why this request:

is failing.

from /opt/kaltura/log/kaltura_admin.log, copy the full JSON being sent and, from a shell on the Kaltura Server, run:

$ curl -X POST https://cdn.hiphopservers.com/api_v3/index.php/service/systempartner_systempartner/action/getPackages -H 'Content-Type: application/json'  -d 'FULL_JSON_FROM_LOG'

To clarify, here is an example from my machine:

$ curl -X POST https://jessex/api_v3/index.php/service/systempartner_systempartner/action/getPackages -H 'Content-Type: application/json'  -d '{"format":"2","ignoreNull":true,"clientTag":"Kaltura-admin","apiVersion":"3.3.0","filter":{"objectType":"KalturaPartnerFilter","statusIn":"1,2","orderBy":"-id"},"pager":{"objectType":"KalturaFilterPager","pageSize":"10","pageIndex":"1"},"ks":"mEuY29tO2Rpc2FibGVlbnRpdGxlbWVudDs7","kalsig":"e30ede99962200f3299e37008f02b5ec"}'

IMPORTANT NOTE:
Never post your full KS here since that can be used to access privileged services.

20

@jess

Here is the full log.

2017-07-25 07:43:29 [0.069849] [643290171] [8] [%context%] [ErrorController->errorAction] ERR: exception 'Kaltura_Client_ClientException' with message '. RC : 0' in /opt/kaltura/app/admin_console/lib/Kaltura/Client/ClientBase.php:919
Stack trace:
#0 /opt/kaltura/app/admin_console/lib/Kaltura/Client/ClientBase.php(249): Kaltura_Client_ClientBase->getKalturaClientException('. RC : 0', -1)
#1 /opt/kaltura/app/admin_console/lib/Kaltura/Client/SystemPartner/SystemPartnerService.php(93): Kaltura_Client_ClientBase->doQueue()
#2 /opt/kaltura/app/admin_console/controllers/PartnerController.php(123): Kaltura_Client_SystemPartner_SystemPartnerService->getPackages()
#3 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Controller/Action.php(513): PartnerController->listAction()
#4 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Controller/Dispatcher/Standard.php(289): Zend_Controller_Action->dispatch('listAction')
#5 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Controller/Front.php(946): Zend_Controller_Dispatcher_Standard->dispatch(Object(Zend_Controller_Request_Http), Object(Zend_Controller_Response_Http))
#6 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Application/Bootstrap/Bootstrap.php(77): Zend_Controller_Front->dispatch()
#7 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Application.php(358): Zend_Application_Bootstrap_Bootstrap->run()
#8 /opt/kaltura/app/admin_console/web/index.php(38): Zend_Application->run()
#9 {main}
2017-07-25 07:43:30 [0.000000] [973553104] [1] [%context%] [FeedDropFolderPlugin::getTranslations] INFO: Loading file [/opt/kaltura/app/plugins/bulk_upload/drop_folder_xml/plugins/config/lang/en.php]
2017-07-25 07:43:30 [0.000389] [973553104] [2] [%context%] [FeedDropFolderPlugin::getTranslations] INFO: Loading file [/opt/kaltura/app/plugins/bulk_upload/drop_folder_xml/plugins/config/lang/en.php]
2017-07-25 07:43:30 [0.000354] [973553104] [3] [%context%] [FeedDropFolderPlugin::getTranslations] INFO: Loading file [/opt/kaltura/app/plugins/bulk_upload/drop_folder_xml/plugins/config/lang/en.php]
2017-07-25 07:43:30 [0.000374] [973553104] [4] [%context%] [FeedDropFolderPlugin::getTranslations] INFO: Loading file [/opt/kaltura/app/plugins/bulk_upload/drop_folder_xml/plugins/config/lang/he.php]
2017-07-25 07:43:30 [0.005371] [973553104] [5] [%context%] [Kaltura_Client_ClientBase->doQueue] DEBUG: service url: [https://cdn.hiphopservers.com]
2017-07-25 07:43:30 [0.000100] [973553104] [6] [%context%] [Kaltura_Client_ClientBase->doCurl] DEBUG: curl: https://cdn.hiphopservers.com/api_v3/index.php/service/systempartner_systempartner/action/getPackages
2017-07-25 07:43:30 [0.000042] [973553104] [7] [%context%] [Kaltura_Client_ClientBase->doCurl] DEBUG: post: {"format":"2","ignoreNull":true,"clientTag":"Kaltura-admin","apiVersion":"3.3.0","ks":"YjYyNmQxYzcyNDZi{PRIVAT_KEY]2O","kalsig":"f775643{PRIVATE]370193d80e2"}
2017-07-25 07:43:30 [0.054077] [973553104] [8] [%context%] [ErrorController->errorAction] ERR: exception 'Kaltura_Client_ClientException' with message '. RC : 0' in /opt/kaltura/app/admin_console/lib/Kaltura/Client/ClientBase.php:919
Stack trace:
#0 /opt/kaltura/app/admin_console/lib/Kaltura/Client/ClientBase.php(249): Kaltura_Client_ClientBase->getKalturaClientException('. RC : 0', -1)
#1 /opt/kaltura/app/admin_console/lib/Kaltura/Client/SystemPartner/SystemPartnerService.php(93): Kaltura_Client_ClientBase->doQueue()
#2 /opt/kaltura/app/admin_console/controllers/PartnerController.php(123): Kaltura_Client_SystemPartner_SystemPartnerService->getPackages()
#3 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Controller/Action.php(513): PartnerController->listAction()
#4 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Controller/Dispatcher/Standard.php(289): Zend_Controller_Action->dispatch('listAction')
#5 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Controller/Front.php(946): Zend_Controller_Dispatcher_Standard->dispatch(Object(Zend_Controller_Request_Http), Object(Zend_Controller_Response_Http))
#6 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Application/Bootstrap/Bootstrap.php(77): Zend_Controller_Front->dispatch()
#7 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Application.php(358): Zend_Application_Bootstrap_Bootstrap->run()
#8 /opt/kaltura/app/admin_console/web/index.php(38): Zend_Application->run()
#9 {main}

Returns the following:

<?xml version="1.0" encoding="utf-8"?><xml><result><error><code>SERVICE_FORBIDDEN</code><message>The access to service [systempartner_systempartner-&gt;getPackages] is forbidden</message><objectType>KalturaAPIException</objectType><args><item><objectType>KalturaApiExceptionArg</objectType><name>SERVICE</name><value>systempartner_systempartner-&gt;getPackages</value></item></args></error></result><executionTime>0.014321088790894</executionTime></xml>