What is the present collection version.  And please send the screenshot of the Collection profile ( top and bottom) In deploying the  image  you would have created the cli admin password?  (java based shell authentication is not the same as the GUI) If so have you also created/activated  the users collectorlogin and root ? (real linux shell) If not do the following for the cli admin  shell admin# pwdreset root 90 And admin# pwdreset collectorlogin 90 it will activate those accounts and generate their passwords  ( keep them where you can refer to them in the future) after that Via SSH Login to collector as user collectorlogin and then use command below to connect as root (cannot connect directly) # su root and then send me by email the following commands outputs:   # df -k # free # service concsotgw restart # service cspc restart   # tail -100 /opt/ConcsoTgw/tail-end-gateway-decoupled/bin/CONN_TEG_LOGS/tail-end-gateway.log # openssl s_client -showcerts -connect concsoweb-prd.cisco.com:443 # tail -100 /opt/ConcsoTgw/tail-end-gateway-decoupled/bin/nohup.out # wget https://72.163.7.113/HeadEndWebAppServlet/ --no-check-certificate ... View more

  Please send me your cco id and what is the company name you have registered in private message please.. ... View more

    Por Favor tente https://services.cisco.com ... View more

    Send me in Private the screenshot ( full top and bottom ) of your collection profile and the following logs in private message PLEASE TO DO THE FOLLOWING: In deploying the  image  you would have created the cli admin password?  (java based shell) If so have you also created/activated  the users collectorlogin and root ? (real linux shell) If not do the following for the cli admin  shell admin# pwdreset root 90 And admin# pwdreset collectorlogin 90 it will activate those accounts and generate their passwords  ( keep them where you can refer to them in the future) after that Via SSH Login to collector as user collectorlogin and then use command below to connect as root (cannot connect directly) # su root and then the following commands :   # tail -100 /opt/ConcsoTgw/tail-end-gateway-decoupled/bin/CONN_TEG_LOGS/tail-end-gateway.log # openssl s_client -showcerts -connect concsoweb-prd.cisco.com:443 # tail -100 /opt/ConcsoTgw/tail-end-gateway-decoupled/bin/nohup.out # wget https://72.163.7.113/HeadEndWebAppServlet/ --no-check-certificate ... View more

    INTERNAL SERVER ERROR IS A GENERIC ERROR AND WE NEED TO FIND THE MORE SPECIFIC ERROR FOR SOLUTION PLEASE DO THE FOLLOWING PLEASE TO DO THE FOLLOWING: In deploying the  image  you would have created the cli admin password?  (java based shell) If so have you also created/activated  the users collectorlogin and root ? (real linux shell) If not do the following for the cli admin  shell admin# pwdreset root 90 And admin# pwdreset collectorlogin 90 it will activate those accounts and generate their passwords  ( keep them where you can refer to them in the future) after that Via SSH Login to collector as user collectorlogin and then use command below to connect as root (cannot connect directly) # su root and then the following commands and send to me in private message:   # tail -100 /opt/ConcsoTgw/tail-end-gateway-decoupled/bin/CONN_TEG_LOGS/tail-end-gateway.log # openssl s_client -showcerts -connect concsoweb-prd.cisco.com:443 # tail -100 /opt/ConcsoTgw/tail-end-gateway-decoupled/bin/nohup.out # wget https://72.163.7.113/HeadEndWebAppServlet/ --no-check-certificate ... View more

you are missing the bottom part of the profile.. Please follow the isntructions and get the bottom part as well ... View more

  :) you no longer that new Alexandre I already dealt with you a number of times.:)  what I need is the screen shots of the collection profile as I mentioned on the post above.  It shows where to click and what to get. particularly ---> Settings-- Manage Dta COLLECTION profile---> (CLICK ON THE PROFILE twice) --> profile details.get the whole screen likely you need to split it into two images. ... View more

not sure what you mean by ANSWERED?? ... View more

  PLEASE USE the instructions above. ... View more

    It is  not the IP or the dns of that IP that is causing the problem, ALL if there was any other would need to be allowed by your company.  Any other IP or DNS name for those servers if there were others would need to either be whitelisted sufficiently to directly go to its destination if you company intercept certificates or use a proxy that do allows it, ... View more