AWS deploy error - This combination of host and port requires TLS

OpenVidu v2 Issues with deployment
1

Hi, I am student and I am learning about developing videocall applications. I have tried official examples from openvidu github locally, and I also tried deploying openvidu call on AWS, however I bumped into this issue:

I am working with this example openvidu-recording-java - OpenVidu Docs , worked correctly locally, so I created docker image and loaded it into my AWS instance. I was following the instructions on deploying openvidu based apps, however after modyfing docker-compose.override.yml to docker image of this example, I am receiving error after starting openvidu and trying to load the page
“Bad Request
This combination of host and port requires TLS.”

Below is my docker-compose.override.yml, and if necessary I can attach openvidu starting logs (I could not attach them directly due to links/media limitations as this is my first post here), however I inspected them and I did not find any difference with starting logs during openvidu-call deployment, which works fine for me. Can you please advise me what can be root of this issue? - if another information/logs are necessary, please let me know.

docker-compose.override.yml

services:
app:
image: openvidu/openvidu-call:2.29.0
restart: on-failure
network_mode: host
environment:
- SERVER_PORT=5442
- OPENVIDU_URL=http://localhost:5443
- OPENVIDU_SECRET=${OPENVIDU_SECRET}
- CALL_OPENVIDU_CERTTYPE=${CERTIFICATE_TYPE}
- CALL_PRIVATE_ACCESS=${CALL_PRIVATE_ACCESS:-}
- CALL_USER=${CALL_USER:-}
- CALL_SECRET=${CALL_SECRET:-}
- CALL_ADMIN_SECRET=${CALL_ADMIN_SECRET:-}
- CALL_RECORDING=${CALL_RECORDING:-}
logging:
options:
max-size: “${DOCKER_LOGS_MAX_SIZE:-100M}”

2

Hello @Jozef_Sedlak

The environment variables used at openvidu-recording-java are not the same as the ones used at openvidu-call.

Try to set this environment variable

SERVER_SSL_ENABLED=false

The tutorial is configured to work with SSL:

But the nginx proxy is doing a reverse proxy to http://localhost:5442

What I think is happening is that your tutorial is running in the machine with SSL when it shouldn’t, becasue the nginx proxy is the one managing them.

I hope this solves your problem :slight_smile:

Regards.

1 Like
5

Hi, I tried as you instructed and it worked straight away. Thank you so much, I would have never realized that on my own, but I will keep that in mind from now on. Thank you very much once again :slight_smile:

2 Likes