Can't access kmc and admin_console (web not responding)

Hello
i installed to success but can’t access web.
see this image.


my log

#katllog

==> /opt/kaltura/log/batch/dbcleanup-0-2019-02-16.err.log <==
PHP Fatal error:  Uncaught exception 'KalturaClientException' with message 'Failed connect to 192.168.1.32:80; Connection refused' in /opt/kaltura/app/batch/client/KalturaClientBase.php:362
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(1070): KalturaClientBase->doQueue()
--
==> /opt/kaltura/log/batch/jobsuspender-0-2019-02-16.err.log <==
PHP Fatal error:  Uncaught exception 'KalturaClientException' with message 'Failed connect to 192.168.1.32:80; Connection refused' in /opt/kaltura/app/batch/client/KalturaClientBase.php:362
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(1294): KalturaClientBase->doQueue()
--
==> /opt/kaltura/log/batch/mailer-0-2019-02-16.err.log <==
PHP Warning:  vsprintf(): Too few arguments in /opt/kaltura/app/batch/batches/Mailer/KAsyncMailer.class.php on line 237

--
==> /opt/kaltura/log/batch/partnerloadcleanup-0-2019-02-16.err.log <==
PHP Fatal error:  Uncaught exception 'KalturaClientException' with message 'Failed connect to 192.168.1.32:80; Connection refused' in /opt/kaltura/app/batch/client/KalturaClientBase.php:362
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(1380): KalturaClientBase->doQueue()
--
==> /opt/kaltura/log/batch/validatelivemediaservers-0-2019-02-16.err.log <==
PHP Fatal error:  Uncaught exception 'KalturaClientException' with message 'Failed connect to 192.168.1.32:80; Connection refused' in /opt/kaltura/app/batch/client/KalturaClientBase.php:362
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(2341): KalturaClientBase->doQueue()

/opt/kaltura/bin/kaltura-sanity.sh

[Space on /opt/kaltura] [PASSED, RC: 0] - [.005679189]
    [Space on /opt/kaltura/web] [PASSED, RC: 0] - [.003942095]


INFO: Downloading ready-made schema from: /opt/kaltura/web/content/clientlibs/KalturaClient.xml
INFO: Generating from api version: 14.13.0, generated at: 15-02-2019
INFO: Now generating: php5full using Php5ClientGenerator
INFO: Delete old files [/opt/kaltura/web/content/clientlibs/php5full, /opt/kaltura/app/clients/php5]
INFO: Generate client library [php5full]
INFO: set tests path /opt/kaltura/clients-generator/tests/ovp
INFO: Copy sources from [/opt/kaltura/clients-generator/sources/php5]
INFO: Copy tests from [/opt/kaltura/clients-generator/tests/ovp/php5]
INFO: Saving client library to [/opt/kaltura/web/content/clientlibs/php5full]
INFO: Trying to package
DEBUG: Changing dir to [/opt/kaltura/apps/clientlibs/php5full]
INFO: Executing: tar -czf "../php5full_15-02-2019.tar.gz" ../php5full
tar: Removing leading `../' from member names
INFO: Package created successfully: ../php5full_15-02-2019.tar.gz
DEBUG: Restoring dir to [/opt/kaltura/clients-generator]
INFO: php5full generated successfully
Redirecting to /bin/systemctl status httpd.service
[Check httpd daemon status] [PASSED, RC: 0] - [.029281235]
Redirecting to /bin/systemctl stop httpd.service
Redirecting to /bin/systemctl status httpd.service
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status httpd.service
Napping 2 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status httpd.service
Napping 3 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status httpd.service
Napping 4 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status httpd.service
Napping 5 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status httpd.service
Napping 6 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status httpd.service
Napping 7 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status httpd.service
Napping 8 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status httpd.service
Napping 9 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status httpd.service
Napping 10 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status httpd.service
[Check httpd daemon is started by Monit] [PASSED, RC: 0] - [11.359453195]
Note: Forwarding request to 'systemctl is-enabled httpd.service'.
enabled
[check daemon httpd init status] [PASSED, RC: 0] - [.005095707]
[Check kaltura-sphinx daemon status] [PASSED, RC: 0] - [.056039513]
[Check kaltura-sphinx daemon is started by Monit] [PASSED, RC: 0] - [10.604450521]
[check daemon kaltura-sphinx init status] [PASSED, RC: 0] - [.008062173]
[Check kaltura-batch daemon status] [PASSED, RC: 0] - [.035846315]
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 2 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 3 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 4 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 5 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 6 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 7 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 8 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 9 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 10 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] - [10.594847363]
[check daemon kaltura-batch init status] [PASSED, RC: 0] - [.007035674]
[Check kaltura-monit daemon status] [PASSED, RC: 0] - [.041764228]
Note: Forwarding request to 'systemctl is-enabled kaltura-monit.service'.
enabled
[check daemon kaltura-monit init status] [PASSED, RC: 0] - [.014717681]
Redirecting to /bin/systemctl status memcached.service
[Check memcached daemon status] [PASSED, RC: 0] - [.024428681]
Redirecting to /bin/systemctl stop memcached.service
Redirecting to /bin/systemctl status memcached.service
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status memcached.service
Napping 2 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status memcached.service
Napping 3 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status memcached.service
Napping 4 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status memcached.service
Napping 5 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status memcached.service
Napping 6 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status memcached.service
Napping 7 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status memcached.service
Napping 8 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status memcached.service
Napping 9 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status memcached.service
Napping 10 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status memcached.service
[Check memcached daemon is started by Monit] [PASSED, RC: 0] - [10.338269864]
Note: Forwarding request to 'systemctl is-enabled memcached.service'.
enabled
[check daemon memcached init status] [PASSED, RC: 0] - [.005233351]
[kaltura-html5lib ver in KMC config.ini] [PASSED, RC: 0] - [.048825977]
[kaltura-kdp3 ver in KDP3 config.ini] [PASSED, RC: 0] - [.028331360]
[kaltura-kmc ver in KMC config.ini] [PASSED, RC: 0] - [.032408018]
PHP Warning:  file_get_contents(192.168.1.32/kmc): failed to open stream: No such file or directory in /opt/kaltura/bin/get_kmc_swfs.php on line 11
[Get KMC SWFs] [FAILED, RC: 255] - [.073172733]
[check_start_page] [PASSED, RC: 0] - [.015144866]
[check_testme_page] [PASSED, RC: 0] - [.012726309]
[check_kmc_index_page] [PASSED, RC: 0] - [.050804697]
[check_kmcng_index_page] [PASSED, RC: 0] - [.029353715]
[check_admin_console_index_page] [PASSED, RC: 0] - [.138440069]
[check_studio_index_page] [PASSED, RC: 0] - [.013307078]
[check_clipapp_index_page] [PASSED, RC: 0] - [.498843670]
[Create Partner] [PASSED, RC: 0] - [1.514046278]
[Local dropfolder creation] [PASSED, RC: 0] - [.247107267]
[Create flavor param] [PASSED, RC: 0] - [.274478288]
[Delete flavor param] [PASSED, RC: 0] - [.123653758]
[HTTP notification: ID: 38, URL: http://localhost/1.php] [PASSED, RC: 0] - [.274478288]
] [PASSED, RC: 0] - [.274478288]ect: Your video is ready to be played!, Mail body: Hello world:)
[Upload content kaltura_logo_animated_blue.flv] [PASSED, RC: 0] - [.489185781]
Napping 10 seconds to allow entry 0_cdxpmggx to digest..
Napping 10 seconds to allow entry 0_cdxpmggx to digest..
Napping 10 seconds to allow entry 0_cdxpmggx to digest..
Napping 10 seconds to allow entry 0_cdxpmggx to digest..
Napping 10 seconds to allow entry 0_cdxpmggx to digest..
Napping 10 seconds to allow entry 0_cdxpmggx to digest..
Napping 10 seconds to allow entry 0_cdxpmggx to digest..
Napping 10 seconds to allow entry 0_cdxpmggx to digest..
[kaltura_logo_animated_blue.flv - 0_cdxpmggx status] [PASSED, RC: 0] - [81.049315687]
[Create thumb for 0_cdxpmggx] [PASSED, RC: 0] - [.244984243]
[Clipping 0_cdxpmggx] [PASSED, RC: 0] - [.330868616]
[Trimming 0_cdxpmggx] [PASSED, RC: 0] - [.313167593]
[Mock playback 0_cdxpmggx] [PASSED, RC: 0] - [.172353698]
[Adding captions to 0_cdxpmggx] [PASSED, RC: 0] - [.220247662]
[Searching for Example||Deja||Bold in 0_cdxpmggx metadata] [PASSED, RC: 0] - [.225003108]
[Entry reconversion of 0_cdxpmggx succeeded] [PASSED, RC: 0] - [.236151497]
Napping 30 seconds to allow mail to be sent out..
[Found an email sending entry for mb-fimplus@kaltura.com[PID is 106] in /var/log/maillog] [PASSED, RC: 0] - [30.015085305]
Testing analytics, be patient..

Please note: if you are running this test on a clustered ENV, it will fail but this does not mean there is an actual problem.
The tech information as to why is available here:
https://github.com/kaltura/platform-install-packages/issues/106#issuecomment-42837404

[DWH cycle] [FAILED, RC: 255] - [34.430164307]
[Upload content kaltura_logo_animated_green.flv] [PASSED, RC: 0] - [.590640557]
[Upload bulk using CSV] [PASSED, RC: 0] - [.277604871]
[Upload bulk using XML] [PASSED, RC: 0] - [.232518529]
[Create player] [PASSED, RC: 0] - [.148927635]
[Generate thumb] [PASSED, RC: 0] - [.197895336]
[Delete all entries] [PASSED, RC: 0] - [.245598577]
[Delete partner] [PASSED, RC: 0] - [.287177464]
[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


Thank you for running Kaltura! To keep Kaltura viable, stable and well tested, please join the community and help by contributing sanity tests that verify overall platform stability: http://bit.ly/kaltura-ci , and by contributing to the project roadmap by solving simple tasks and challenges: http://bit.ly/kaltura-tasks.

You have new mail in /var/spool/mail/root

Hi @tinhphaistc,

It looks as though you’re simply unable to reach 192.168.1.32, which is what you set as the Kaltura service URL [endpoint], from your machine. The output of your sanity check seems perfectly fine so I suggest you check whether there’s a FW in place, blocking traffic to the server [or another network related reason why it cannot be reached] from where you’re running the browser.