It was still the 199 ip instead of 92. I did rerun the /opt/kaltura/bin/kaltura-base-config.sh before my last post and things were still like that. I'll rerun again.
Regarding logs, I have been going through them but it's really difficult for me to know what to do in some circumstances, I am not sure what to refer to in an instance like this:
0 /opt/kaltura/app/alpha/apps/kaltura/lib/KExternalErrors.class.php(128): KalturaLog::err('exiting on erro...')
--
2016-07-06 20:07:23 [0.000487] [920341412] [33] [BATCH]
[KJobHandlerWorker::setCurrentJob] DEBUG: Start job[3206] type[10]
sub-type[0] object[1] object-id[0_kt4zr3hj] partner-id[108] dc[0]
parent-id[] root-id[3206]
2016-07-06 20:07:23 [0.000491] [920341412]
[34] [BATCH] [KJobHandlerWorker->closeJob] ERR: exception 'Exception'
with message 'Timed out' in
/opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
Like yes, that to me says that the KJobHandlerWorker is closing because it timed out on object 0_kt4zr3hj, but I'm not sure what to do with that information. Anyway, I'll rerun the config.