Issues in deploying Miko in Azure

MikoPBX forum
1

HI,

I keep getting the following error message whenever I try to create an image from blob storage

The specified cookie value in VHD footer indicates that disk ‘mikopbx-2026.1.223-x86_64 (1).vhd’ with blob https://mikapbxxxxxxxx:8443/imgs/mikopbx-2026.1.223-x86_64.vhd is not a supported VHD. Disk is expected to have cookie value ‘conectix’. (Code: InvalidParameter, Target: disks)

I am using latest version that I downloaded from the website.

Any Solutions ?

2

>>???

Any one, any help would be great

3

Please check during assembly. Release MikoPBX 2026.2.83-dev — Nightly DEV · mikopbx/Core · GitHub

4

Hi,

Thanks for the report. I checked the VHD file from our latest releases and can confirm the image itself is a valid Azure-compatible fixed VHD: the footer contains the required conectix cookie, disk type is Fixed (2), virtual size is aligned to
1 MiB, and the footer checksum verifies correctly. So the problem is happening between the download and the Azure import, not in the file we publish.

The most likely causes, in order:

  1. The VHD was uploaded as a Block Blob instead of a Page Blob.
    This is by far the most common reason for the exact error you’re seeing. Azure Managed Disk import requires the source blob to be a Page Blob — a Block Blob will fail with the same “cookie value in VHD footer” message even when the file is
    perfectly fine.

Please re-upload using one of these commands, which force the correct blob type:

AzCopy (recommended)

azcopy copy “mikopbx-2026.1.223-x86_64.vhd”
“https://.blob.core.windows.net//mikopbx.vhd?”
–blob-type PageBlob

or Azure CLI

az storage blob upload
–account-name
–container-name
–type page
–file mikopbx-2026.1.223-x86_64.vhd
–name mikopbx.vhd

Then create the Managed Disk from that Page Blob (Portal: Create disk → Source type: Storage blob, or az disk create --source ).

  1. The sourceUri points to your own HTTP server.
    The URL in your error message — https://mikapbxxxxxxxx:8443/imgs/...vhd — looks like a self-hosted server, not Azure Storage. Azure can only import from a blob URL on *.blob.core.windows.net (with SAS if private). It cannot pull a VHD from an
    arbitrary external HTTPS endpoint. The VHD must first be uploaded into Azure Storage as a Page Blob as shown above.

  2. The downloaded file is truncated or corrupted.
    Before re-uploading, please verify the file you have locally:

Size must be exactly 630,194,688 bytes for the x86_64 image

ls -la mikopbx-2026.1.223-x86_64.vhd

The last 8 bytes of the file MUST read “conectix”

tail -c 512 mikopbx-2026.1.223-x86_64.vhd | head -c 8 ; echo

Compare SHA256 against the value published in checksum.md5 / release page

sha256sum mikopbx-2026.1.223-x86_64.vhd

If tail -c 512 | head -c 8 does not print conectix, the file was truncated during download — please download it again from our GitHub release page.

Let me know which of the three turns out to be the case and I’ll help you finish the import.

Best regards,
MikoPBX team