Azure OpenVidu Single Node COMMUNITY installation: connection refused

Peter · June 19, 2026, 3:30pm

Just installed (tried multiple times) OpenVidu Single Node COMMUNITY on Azure, by following these instructions OpenVidu Single Node installation on Azure - OpenVidu

I’m using let’s encrypt, I configured a domain pointing to the public ip address configured on Azure, and used this for the installation. Everything pretty standard.

No faults where shown when the deployment was done. However, when I want to go the OpenVidu dashboard to test if its running, via ‘https://my.domain/dashboard’, I get a ‘connection refused’.

Any help would be much appreciated…

Peter

===== Additional info:

No errors in:

/var/log/cloud-init-output.log

/var/log/cloud-init.log

As far as I can tell the openvidu is running. “systemctl status openvidu” gives

● openvidu.service - OpenVidu Community - Single Node

 Loaded: loaded (/etc/systemd/system/openvidu.service; enabled; preset: enabled)

 Active: active (running) since Fri 2026-06-19 14:59:02 UTC; 16min ago

Process: 7890 ExecStartPre=/bin/sh -c docker-compose down && /usr/local/bin/update_secret_from_config.sh (code=exited, status=0/SUCCESS)

Main PID: 8388 (docker-compose)

  Tasks: 7 (limit: 1038)

 Memory: 21.4M (peak: 109.5M)

    CPU: 29.454s

 CGroup: /system.slice/openvidu.service

         └─8388 /usr/local/bin/docker-compose up

I do see some mongo errors, but I don’t know if they are relevant:

mongo | {“t”:{“$date”:“2026-06-19T15:07:50.000+00:00”},“s”:“W”, “c”:“QUERY”, “id”:23799, “ctx”:“ftdc”,“msg”:“Aggregate command executor error”,“attr”:{“error”:{“code”:26,“codeName”:“NamespaceNotFound”,“errmsg”:“Unable to retrieve storageStats in $collStats stage :: caused by :: Collection [config.image_collection] not found.”},“stats”:{},“cmd”:{“aggregate”:“image_collection”,“cursor”:{},“pipeline”:[{“$collStats”:{“storageStats”:{“waitForLock”:false,“numericOnly”:true}}}],“$db”:“config”}}}

cruizba · June 22, 2026, 9:50am

Hello @Peter

What version are you deploying?

What is the output of docker ps? Are containers restarting?

Peter · June 22, 2026, 1:48pm

Thanks for replying!

I’m deploying version 3.7.0.

======

Docker ps, returns:

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

0920a44f3f3d mongo:8.0.21 “/bin/sh -c '\n . /c…” 39 hours ago Up 39 hours mongo

8e4d0cccebe2 openvidu/openvidu-operator:3.7.0 “/bin/operator” 39 hours ago Restarting (1) 16 seconds ago openvidu-init

46dbba2d8917 openvidu/openvidu-operator:3.7.0 “/bin/operator” 39 hours ago Up 39 hours operator

======

Did a restart using: sudo systemctl restart openvidu

And aftwards ran sudo systemctl status openvidu, resulted in:

● openvidu.service - OpenVidu Community - Single Node

 Loaded: loaded (/etc/systemd/system/openvidu.service; enabled; preset: enabled)

 Active: active (running) since Mon 2026-06-22 13:45:56 UTC; 3s ago

Process: 281788 ExecStartPre=/bin/sh -c docker-compose down && /usr/local/bin/update_secret_from_config.sh (code=exited, status=0/SUCCESS)

Main PID: 282285 (docker-compose)

  Tasks: 6 (limit: 1038)

 Memory: 89.0M (peak: 106.0M)

    CPU: 19.415s

 CGroup: /system.slice/openvidu.service

         └─282285 /usr/local/bin/docker-compose up

Jun 22 13:45:58 OpenViduSkySoft-VM-CE docker-compose[282285]: Container loki Creating

Jun 22 13:45:58 OpenViduSkySoft-VM-CE docker-compose[282285]: Container minio Creating

Jun 22 13:45:58 OpenViduSkySoft-VM-CE docker-compose[282285]: Container egress Creating

Jun 22 13:45:58 OpenViduSkySoft-VM-CE docker-compose[282285]: Container mongo Creating

Jun 22 13:45:58 OpenViduSkySoft-VM-CE docker-compose[282285]: Container operator Created

Jun 22 13:45:59 OpenViduSkySoft-VM-CE docker-compose[282285]: Container caddy Created

Jun 22 13:46:00 OpenViduSkySoft-VM-CE docker-compose[282285]: Container openvidu Created

Jun 22 13:46:00 OpenViduSkySoft-VM-CE docker-compose[282285]: Container prometheus Creating

Jun 22 13:46:00 OpenViduSkySoft-VM-CE docker-compose[282285]: Container dashboard Created

Jun 22 13:46:01 OpenViduSkySoft-VM-CE docker-compose[282285]: Container ingress Created

====

Peter

cruizba · June 22, 2026, 2:05pm

Try the following (as root).

Stop openvidu:

systemctl stop openvidu

Stop all containers:

docker rm -f $(docker ps -a -q)

Restart docker daemon:

systemctl restart docker

Start OpenVidu

systemctl start openvidu

I do not know why this happen, looks like a race condition caused by docker because the rest of the containers are created but not running. Let me know if this fix the issue.

Peter · June 26, 2026, 9:30am

Thanks, but I tried this and it didn’t resolve my issue. Any other ideas?

Running “sudo systemctl status openvidu” gives:

● openvidu.service - OpenVidu Community - Single Node

     Loaded: loaded (/etc/systemd/system/openvidu.service; enabled; preset: enabled)

     Active: active (running) since Fri 2026-06-26 09:20:14 UTC; 2min 23s ago

    Process: 3843 ExecStartPre=/bin/sh -c docker-compose down && /usr/local/bin/update_secret_from_config.sh (code=exited, status=0/SUCCESS)

   Main PID: 4344 (docker-compose)

      Tasks: 7 (limit: 1038)

     Memory: 34.1M (peak: 109.4M)

        CPU: 20.084s

     CGroup: /system.slice/openvidu.service

             └─4344 /usr/local/bin/docker-compose up



Jun 26 09:22:38 OpenViduSkySoft-VM-CE docker-compose[4344]: mongo          | {"t":{"$date":"2026-06-26T09:22:38.000+00:00"},"s":"W",  "c":"QUERY",    "id":23799,   "ctx":"ftdc","msg":"Aggregate command executor error","attr":{"error":{"code":26,"codeName":"NamespaceNotFound","errmsg":"Unable >

Jun 26 09:22:39 OpenViduSkySoft-VM-CE docker-compose[4344]: mongo          | {"t":{"$date":"2026-06-26T09:22:39.124+00:00"},"s":"W",  "c":"QUERY",    "id":23799,   "ctx":"ftdc","msg":"Aggregate command executor error","attr":{"error":{"code":26,"codeName":"NamespaceNotFound","errmsg":"Unable >

Jun 26 09:22:39 OpenViduSkySoft-VM-CE docker-compose[4344]: mongo          | {"t":{"$date":"2026-06-26T09:22:39.124+00:00"},"s":"W",  "c":"QUERY",    "id":23799,   "ctx":"ftdc","msg":"Aggregate command executor error","attr":{"error":{"code":26,"codeName":"NamespaceNotFound","errmsg":"Unable >

Jun 26 09:22:39 OpenViduSkySoft-VM-CE docker-compose[4344]: mongo          | {"t":{"$date":"2026-06-26T09:22:39.126+00:00"},"s":"W",  "c":"QUERY",    "id":23799,   "ctx":"ftdc","msg":"Aggregate command executor error","attr":{"error":{"code":26,"codeName":"NamespaceNotFound","errmsg":"Unable >

Jun 26 09:22:40 OpenViduSkySoft-VM-CE docker-compose[4344]: mongo          | {"t":{"$date":"2026-06-26T09:22:40.000+00:00"},"s":"W",  "c":"QUERY",    "id":23799,   "ctx":"ftdc","msg":"Aggregate command executor error","attr":{"error":{"code":26,"codeName":"NamespaceNotFound","errmsg":"Unable >

Jun 26 09:22:40 OpenViduSkySoft-VM-CE docker-compose[4344]: mongo          | {"t":{"$date":"2026-06-26T09:22:40.000+00:00"},"s":"W",  "c":"QUERY",    "id":23799,   "ctx":"ftdc","msg":"Aggregate command executor error","attr":{"error":{"code":26,"codeName":"NamespaceNotFound","errmsg":"Unable >

Jun 26 09:22:40 OpenViduSkySoft-VM-CE docker-compose[4344]: mongo          | {"t":{"$date":"2026-06-26T09:22:40.000+00:00"},"s":"W",  "c":"QUERY",    "id":23799,   "ctx":"ftdc","msg":"Aggregate command executor error","attr":{"error":{"code":26,"codeName":"NamespaceNotFound","errmsg":"Unable >

Jun 26 09:22:41 OpenViduSkySoft-VM-CE docker-compose[4344]: mongo          | {"t":{"$date":"2026-06-26T09:22:41.122+00:00"},"s":"W",  "c":"QUERY",    "id":23799,   "ctx":"ftdc","msg":"Aggregate command executor error","attr":{"error":{"code":26,"codeName":"NamespaceNotFound","errmsg":"Unable >

Jun 26 09:22:41 OpenViduSkySoft-VM-CE docker-compose[4344]: mongo          | {"t":{"$date":"2026-06-26T09:22:41.122+00:00"},"s":"W",  "c":"QUERY",    "id":23799,   "ctx":"ftdc","msg":"Aggregate command executor error","attr":{"error":{"code":26,"codeName":"NamespaceNotFound","errmsg":"Unable >

Jun 26 09:22:41 OpenViduSkySoft-VM-CE docker-compose[4344]: mongo          | {"t":{"$date":"2026-06-26T09:22:41.122+00:00"},"s":"W",  "c":"QUERY",    "id":23799,   "ctx":"ftdc","msg":"Aggregate command executor error","attr":{"error":{"code":26,"codeName":"NamespaceNotFound","errmsg":"Unable >

Running “sudo docker compose ps” gives:

WARN[0000] The "RUNNING_SYSTEMD" variable is not set. Defaulting to a blank string. 

NAME            IMAGE                                        COMMAND                   SERVICE         CREATED         STATUS                          PORTS

mongo           docker.io/mongo:8.0.21                       "/bin/sh -c '\n  . /c…"   mongo           4 minutes ago   Up 4 minutes                    

openvidu-init   docker.io/openvidu/openvidu-operator:3.7.0   "/bin/operator"           openvidu-init   4 minutes ago   Restarting (1) 12 seconds ago   

operator        docker.io/openvidu/openvidu-operator:3.7.0   "/bin/operator"           operator        4 minutes ago   Up 4 minutes

Also tried “curl -I https://localhost/dashboard”, which resulted in:

curl: (7) Failed to connect to localhost port 443 after 0 ms: Couldn't connect to server

And: “sudo docker compose logs openvidu-init | tail -100”

WARN[0000] The "RUNNING_SYSTEMD" variable is not set. Defaulting to a blank string. 

openvidu-init  | 2026-06-26T09:29:22Z | INFO  | config-manager      | Reading environment file envConfigFileDir=/opt/openvidu/config/openvidu.env

openvidu-init  | 2026-06-26T09:29:22Z | INFO  | config-manager      | Successfully loaded local configuration

openvidu-init  | 2026-06-26T09:29:22Z | INFO  | config-manager      | Processing runtime configurations for all services

openvidu-init  | 2026-06-26T09:29:22Z | INFO  | config-manager      | Successfully processed runtime service configuration serviceName=dashboard

openvidu-init  | 2026-06-26T09:29:22Z | INFO  | config-manager      | Successfully processed runtime service configuration serviceName=grafana

openvidu-init  | 2026-06-26T09:29:22Z | INFO  | config-manager      | Successfully processed runtime service configuration serviceName=openvidu-meet

openvidu-init  | 2026-06-26T09:29:22Z | INFO  | config-manager      | Successfully processed runtime service configuration serviceName=agent-speech-processing

openvidu-init  | 2026-06-26T09:29:22Z | INFO  | config-manager      | Successfully processed runtime service configuration serviceName=redis

openvidu-init  | 2026-06-26T09:29:22Z | INFO  | config-manager      | Successfully processed runtime service configuration serviceName=mongo

openvidu-init  | 2026-06-26T09:29:22Z | INFO  | config-manager      | Successfully processed runtime service configuration serviceName=caddy

openvidu-init  | 2026-06-26T09:29:22Z | INFO  | config-manager      | Successfully processed runtime service configuration serviceName=openvidu

openvidu-init  | 2026-06-26T09:29:22Z | INFO  | config-manager      | Successfully processed runtime service configuration serviceName=prometheus

openvidu-init  | 2026-06-26T09:29:22Z | INFO  | config-manager      | Successfully processed runtime service configuration serviceName=promtail

openvidu-init  | 2026-06-26T09:29:22Z | INFO  | config-manager      | Successfully processed runtime service configuration serviceName=loki

openvidu-init  | 2026-06-26T09:29:22Z | INFO  | config-manager      | Successfully processed runtime service configuration serviceName=minio

openvidu-init  | 2026-06-26T09:29:22Z | INFO  | config-manager      | Successfully processed runtime service configuration serviceName=ingress

openvidu-init  | 2026-06-26T09:29:22Z | INFO  | config-manager      | Successfully processed runtime service configuration serviceName=egress

openvidu-init  | 2026-06-26T09:29:22Z | INFO  | config-manager      | Successfully processed runtime configurations for all services

openvidu-init  | 2026-06-26T09:29:22Z | INFO  | main                | OpenVidu Single Node configuration initialized

openvidu-init  | 2026-06-26T09:29:22Z | INFO  | mongo-operator      | *** Initializing MongoDB cluster ***

openvidu-init  | 2026-06-26T09:29:22Z | INFO  | mongo-operator      | Can't update admin user with old credentials. Checking new credentials...

openvidu-init  | 2026-06-26T09:29:22Z | FATAL | main                | Error initializing mongo elastic operator error="Error pinging MongoDB: connection() error occurred during connection handshake: auth error: sasl conversation error: unable to authenticate using mechanism \"SCRAM-SHA-1\": (AuthenticationFailed) Authentication failed."

cruizba · June 26, 2026, 11:01am

Yes.

As the error is in the first initialization process, I suppose you do not have any data yet, so you can try to remove /opt/openvidu/data:

Try this:

Stop openvidu:

systemctl stop openvidu

Stop all containers:

docker rm -f $(docker ps -a -q)

Remove the /opt/openvidu/data directory

Only remove if it is the first time you are running OpenVidu and you don’t have any important data

rm -rf /opt/openvidu/data

Restart docker daemon

systemctl restart docker

Start OpenVidu

systemctl start openvidu

Let me know if this works.

Peter · June 26, 2026, 2:15pm

So, I did it this. Didn’t seem to help. But before I could really check, the VM on Azure starting acting weird and I’ve not been able to connect to it via ssh anymore. No idea what is going, tried a bunch of things.

I will now delete everything on Azure that has to do with the OpenVidu installation, and try one more time.

I will follow OpenVidu Single Node installation on Azure - OpenVidu once again, using Let’sEncrypt with a new FDQN and a new Public IP Adress… Anything special I need to consider?

And I will report back on how it went…

cruizba · June 26, 2026, 2:29pm

Not really, it should work. We will try in our Azure account just in case something is wrong.

cruizba · June 26, 2026, 3:09pm

I’ve tested it right now and I was able to run it with these parameters with and without a domain name (using sslip automatically). Both scenarios works correctly.

cruizba · June 26, 2026, 3:45pm

Something is flaky, definitely, I’ve tried multiple times to deploy, and one of the times it did not start properly. But at some point if you redeploy it should work.

The previous capture was Single Node PRO. This is another capture of docker ps after installing Single Node Community:

I think the error is somewhat related with Docker, I need to test for the newer 3.8.0 with recent versions of Docker to see if this flaky start does not happen again.

Peter · June 28, 2026, 9:27am

So, tried again today. Got it working on the third deployment. Berfore every deployment I deleted everything and started over again (when wanting to do a ‘redeployment’, it asks for a string value for ‘Admin Ssh Key’, what do you enter here?).

First and second deployment gave the following for ‘sudo docker ps’:

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

Nothing was displayed.

Third attempts worked, not really changed anything in the deployment settings. Just didn’t use underscores in the naming of various resources. …

Anyway, I can keep going on now and start using OpenVidu again!

Cheers,

Peter

cruizba · July 1, 2026, 9:07am

Hey @Peter,

How did you deploy the Azure deployment? What file did you use?

Technically if you use the official documentation and click to the “Deploy to Azure” button, the form should not ask for Admin Ssh Key.

Deploy Azure 3.7.0

In the forms it let you select your SSH key:

Peter · July 1, 2026, 1:56pm

Yes, I used the deploy to azure button from the official documentation. And your screenshot shows what’s presented when I deploy for the first time.

When however I want to redeploy, to quickly try again, I go to the created ‘OpenVidu’ resource group. Then under ‘Settings’, I choose ‘Deployments’ and I select a deployment to redeploy, I get presented with the ‘Admin Ssh Key’ string input field.

sergio.fernandez · July 1, 2026, 5:06pm

Hi, this is Sergio from the OpenVidu team.

What you did of redeploying from Azure using that same deployment is perfectly valid. That said, the recommended approach is to delete the failed deployment and redeploy from the button instead.The reason is that the Admin SSH Key variable uses the Object type from Azure’s Bicep language, so without our custom form view you won’t be able to fill in that variable properly hence the recommendation.

Hope this helps!

Topic		Replies	Views
Deploy openvidu docker on Azure Issues with deployment v2	15	1924	November 5, 2021
OpenVidu Installation is not working "ERR_CONNECTION_REFUSED" Issues with deployment v2	1	755	July 28, 2020
Video transmission not working Issues with deployment v2	23	1361	August 5, 2020
Openvidu showing black screen when deployed on Azure Issues with deployment v2	2	388	September 23, 2021
OPENVIDU 3.1.0 Single Node Installation Issue Issues with deployments	10	117	March 27, 2025

Azure OpenVidu Single Node COMMUNITY installation: connection refused

Related topics