This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 27%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMU%3C/text%3E%3C/svg%3E)
I have setup bigbluebutton on Azure VM Standard_D8as_v5, after installation everything works fine. there are no issues in any functionality. But when I restart the VM, the VM donot respond and the VM went into the error state. This only happens after the succesful install of bigbluebutton 3.0 on ubuntu 22.04 on Azure VM.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 33%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESP%3C/text%3E%3C/svg%3E)
Hi Mansoor Ur Rehman,
I understand your concern — the VM becomes unresponsive after installing BigBlueButton and rebooting. The first step is to check the VM's Activity Logs in the Azure portal to identify the root cause of the issue.
BigBlueButton depends on multiple services (such as nginx, FreeSWITCH, Redis, etc.) that must start in the correct order and with the appropriate permissions. If a critical service fails or crashes during boot, it can cause the VM to become unresponsive.
Additionally, use the Azure Serial Console to troubleshoot boot-related issues. This tool allows you to access the VM during the early boot process and inspect any errors that may be preventing it from starting correctly. serial-console-linux
Make sure that disk space and memory are not exhausted, as BigBlueButton requires significant system resources, especially for handling recordings and media processing.
If you are able to temporarily access the VM, check the status of BigBlueButton services by running:
bash
Copy
bbb-conf --status
This will help verify which components are running and if any have failed.
If the answer is helpful, please click "Accept Answer" and "Upvote it" as it can be helpful to others in the community.
Thank You.
[ OK ] Finished Uncomplicated firewall.
[ 5.367883] cloud-init[744]: Cloud-init v. 25.1.2-0ubuntu0~22.04.2 running 'init-local' at Fri, 13 Jun 2025 12:00:17 +0000. Up 5.34 seconds.
[ 5.569654] /dev/sr0: Can't lookup blockdev
[ OK ] Finished Setup network rules for WALinuxAgent.
[ 35.597046] cloud-init[744]: 2025-06-13 12:00:48,213 - azure.py[WARNING]: Polling IMDS failed attempt 1 with exception: UrlError("HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /metadata/instance?api-version=2021-08-01&extended=true (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x73a119c05150>, 'Connection to 169.254.169.254 timed out. (connect timeout=30.0)'))")
[ 66.629839] cloud-init[744]: 2025-06-13 12:01:19,246 - azure.py[WARNING]: Polling IMDS failed attempt 2 with exception: UrlError("HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /metadata/instance?api-version=2021-08-01&extended=true (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x73a119c047f0>, 'Connection to 169.254.169.254 timed out. (connect timeout=30.0)'))")
[ 97.636734] cloud-init[744]: 2025-06-13 12:01:50,252 - azure.py[WARNING]: Polling IMDS failed attempt 3 with exception: UrlError("HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /metadata/instance?api-version=2021-08-01&extended=true (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x73a119c04f10>, 'Connection to 169.254.169.254 timed out. (connect timeout=30.0)'))")
[ 128.669518] cloud-init[744]: 2025-06-13 12:02:21,285 - azure.py[WARNING]: Polling IMDS failed attempt 4 with exception: UrlError("HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /metadata/instance?api-version=2021-08-01&extended=true (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x73a119c05d50>, 'Connection to 169.254.169.254 timed out. (connect timeout=30.0)'))")
These are my vm serial logs, seem some kind of network issue,
I have tried to restart in safe mode, but the serial gets disconnected.
this is the error on redeployment
Hi Mansoor Ur Rehman,
Your logs show repeated warnings from cloud-init on the Azure VM, indicating that it is unable to reach the Azure Instance Metadata Service (IMDS) at 169.254.169.254 during provisioning. IMDS is critical for Azure VMs to retrieve necessary metadata for proper initialization.
Regarding the serial console error, it appears that multiple serial console sessions were opened, which can cause conflicts. Azure supports only one active serial console session at a time. Please close any extra sessions, wait for approximately 30 minutes, and then try accessing the serial console again.
To temporarily bypass cloud-init, you can either:
Add cloud-init.disable to the kernel boot parameters, or
sudo systemctl mask cloud-init
Also, ensure that no NSG (Network Security Group) rules or OS-level firewall rules are blocking HTTP (port 80) access to 169.254.169.254.
Since BigBlueButton (BBB) may impact WALinuxAgent or related systemd dependencies, verify that the agent is running properly:
sudo systemctl status walinuxagent
Please refer the doument related cloud-init:
https://learn.microsoft.com/en-us/azure/virtual-machines/linux/cloud-init-troubleshooting
If the answer is helpful, please click "Accept Answer" and "Upvote it" as it can be helpful to others in the community.
Thank You.
Thank you
The issue was with UFW, as per bbb documentation we only need to allow port 80 and 443, I have disabled the firewall , and it worked.