Hi,
I have a EC2 instance and did a fresh on premise install of 2.15. I recently ran 2.14 but while trying to run the upgrade github was down and so my existing yml files were overwritten with ‘500 server error’. So I decided to do a fresh install of 2.15.
I am able to access the dashboard but not my own docker application. The error I’m getting from NGINX is:
no resolver defined to resolve ocsp.int-x3.letsencrypt.org while requesting certificate status, responder: ocsp.int-x3.letsencrypt.org, certificate:
And then this eventually times out
*3 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 102.65.8.235, server:
Any ideas? From searching it appears that a resolver explicitly should be set in NGINX conf but this runs inside a container so no idea where to do this.
Help would be appreciated.
Hello you can change it using docker exec -it container-id /bash/
After that you will inside container bash and go /config / you will see default.confg file change it as you need. it will start working but you know docker will forget everything on stop.
So for that issue you can solve using this
After exit from docker container.
Use docker commit comand make new image with your changes.
And go docker-compose file change your docker image name. or use that environment configuration .
its up to you
Thanks
I’ve deployed CE 2.15.0 and letsencrypt is working correctly.
Maybe the problem is related with containers not restarting correctly after other nginx configuration. Please try to do this:
./openvidu stop && ./openvidu start
instead of ./openvidu restart
Thanks I’ve tried stop and start but it didn’t work. I think it’s something wrong with my app container as I re-installed and tested with the default call app and all works well. My app is a NodeJS app.
Docker Override
app:
image: hello-world
restart: on-failure
network_mode: host
environment:
- SERVER_PORT=5442
- OPENVIDU_URL=http://localhost:5443
- OPENVIDU_SECRET=${OPENVIDU_SECRET}
My dockerfile for hello-world
FROM node:14
WORKDIR /app
COPY package.json /app
RUN npm install
COPY . /app
CMD PORT=5442 NODE_ENV=live node --max-old-space-size=4096 app.js https://localhost:5443 “secret”
EXPOSE 5442
This worked in my previous version so I’m not sure why this doesn’t work now. It’s as if my app container can’t access the letsencrypt server ocsp.int-x3.letsencrypt.org to resolve the certificates.
Could it be a permissions issue with the certificates?
Ok after some digging looks like I made a hash of this reinstall. Disabled some crucial app logging which would’ve told me what was up. Turns out the Node app couldn’t connect to Redis and this is the reason why it failed.