Hi, Jay. Please check whether IDP service runs inside container (`# service idp status`) and start it if it doesn't.

Hi Aliaksandr, As per your suggestion, I first ran the service idp status and then service idp start, below are the outputs. It shows jetty service is running but still idp metadata not accessible. This is our host metadata URL: https://dev-sso.taoconnect.org/idp/shibboleth ``` root@dev-sso:~# **service idp status** Jetty running pid=3547 START_INI = /opt/gluu/jetty/idp/start.ini START_D = /opt/gluu/jetty/idp/start.d JETTY_HOME = /opt/jetty JETTY_BASE = /opt/gluu/jetty/idp JETTY_CONF = /opt/jetty/etc/jetty.conf JETTY_PID = /var/run/idp.pid JETTY_START = /opt/jetty/start.jar JETTY_LOGS = /opt/gluu/jetty/idp/logs JETTY_STATE = /opt/gluu/jetty/idp/idp.state CLASSPATH = JAVA = /opt/jre/bin/java JAVA_OPTIONS = -server -Xms256m -Xmx716m -XX:MaxMetaspaceSize=308m -XX:+DisableExplicitGC -Dgluu.base=/etc/gluu -Dserver.base=/opt/gluu/jetty/idp -Djetty.logging.dir=/opt/gluu/jetty/idp/logs -Djetty.home=/opt/jetty -Djetty.base=/opt/gluu/jetty/idp -Djava.io.tmpdir=/opt/jetty-9.3/temp JETTY_ARGS = jetty.http.host=localhost jetty.http.port=8086 jetty.state=/opt/gluu/jetty/idp/idp.state jetty-logging.xml jetty-started.xml RUN_CMD = /opt/jre/bin/java -server -Xms256m -Xmx716m -XX:MaxMetaspaceSize=308m -XX:+DisableExplicitGC -Dgluu.base=/etc/gluu -Dserver.base=/opt/gluu/jetty/idp -Djetty.logging.dir=/opt/gluu/jetty/idp/logs -Djetty.home=/opt/jetty -Djetty.base=/opt/gluu/jetty/idp -Djava.io.tmpdir=/opt/jetty-9.3/temp -jar /opt/jetty/start.jar jetty.http.host=localhost jetty.http.port=8086 jetty.state=/opt/gluu/jetty/idp/idp.state jetty-logging.xml jetty-started.xml root@dev-sso:~# **service idp start** Starting Jetty: process already running. OK Tue Dec 26 12:58:46 UTC 2017 ```..

Hello again Aliaksandr! Can you please suggest what might be the other reason for the aforementioned issue we are facing? Thanks, Jay Kumar

Please do the next: 1. `# mv /opt/shibboleth-idp/logs/idp-process.log /opt/shibboleth-idp/logs/idp-process.log.bak` 2. `# service idp restart` If after the restart the issue still will be there, take recreated `/opt/shibboleth-idp/logs/idp-process.log` file and share it with us.

Thank you very much Aliaksandr! It is working now.

You may need to check service start up order inside container. It's possible `idp` service may start before `solserver` and unable to connect to it because of this. In such case it will happen each time the container is restarted again, until startup order is fixed.