Tech

Let's encrypt with the Vodia PBX

Published on:

June 12, 2019

The Vodia Networks Multi-Tenant (MT) edition now supports the creation of X.509 certificates using the ACME protocol, which can be facilitated through HTTP and DNS challenges. This feature allows administrators to establish a Fully Qualified Domain Name (FQDN) on the PBX, enhancing security with HTTPS. To create a domain, users log in to their Vodia Cloud PBX, navigate to the domain section and set up an A record in their DNS provider (like GoDaddy). Once the domain is established, the PBX can automatically manage certificates, including renewal and deletion, ensuring secure management access.

The Vodia MT edition can now create 509X certificates using the ACME protocol through HTTP and DNS challenges. This is helpful for administrators who want to create an FQDN on the PBX. The Vodia MT edition can also use dnsmadeeasy API requests. In this blog, we will discuss how to manually create an A record for your domain and creating the domain on the Vodia Multi-tenant PBX.

Prerequisite

  • Port 80
  • PBX must be on a Public IP
  • DNS Made Easy Optional
  • DNS Provider Ex (Godaddy)

Creating the Domain

Log in to your Vodia Cloud PBX and navigate to the list section. Press Create to create your domain name. We are calling our domain voice.pbxnvoip.com

Vodia Admin - Create New Domain

Secure https

  • In administrator, mode navigate to network --> ports
  • Activate (Redirect to https)

Creating an A record

We are using Godaddy for this example, as we thought it would be easy to follow.

  • Log in to your account
  • Choose your DNS name and navigate to (DNS), which should bring you to DNS management
GoDaddy - DNS setup
  • Click on Add and Choose (Type A record)
  • The host is the name of the new domain you created
  • (Points to) is the IP of the Vodia Cloud PBX
  • TTL can be set 1hr or 1/2hr
  • Save
  • Navigate to your domain name, e.g., voice.pbxnvoip.com
DNS Vodia

Note: The main limit is Certificates per Registered Domain (50 per week). A registered domain is, generally speaking, the part of the domain you purchased from your domain name registrar. For instance:

in the name www.example.com,the registered domain is example.com

In new.blog.example.co.uk,the registered domain is example.co.uk

We use the Public Suffix List to calculate the registered domain.)

Example:

Encrypt - Secure Connection
Certificate Information - Encrypt

ACME Directory URL & DNS provider:

  • The PBX now supports generating X.509 certificates using the ACME protocol through HTTP and DNS challenges. When using the HTTP challenge, the system must be on a public IP address and it must use port 80. When using the DNS challenge, the DNS must have access to the DNS provider (currently DNSMadeEasy is supported).
  • When adding a domain, the PBX will attempt to create the DNS entry for the new domain and issue a certificate for the domain. A few days before the certificate expires, the PBX will then attempt to reissue the certificate. When a domain gets deleted, the PBX will attempt to delete the DNS entry.
  • It is now also possible to define a DNS name for the system. The PBX will also attempt to generate a certificate for this DNS address so management has access to the system through a properly-encrypted HTTPS connection.

Latest Articles

View All

Why Area Codes Still Matter in a Mobile World

Even in 2025, area codes remain important for personal and business communications. People move frequently but usually keep their original phone numbers because changing them is inconvenient and tied to banking, two-factor authentication, and multiple online accounts. For PBX administrators, area codes are essential for routing calls accurately, displaying the correct caller ID, and managing costs. Vodia PBX simplifies area code management with pattern-based dial plans, automatic updates, and smart trunk selection. This ensures that calls reach the right destination efficiently, maintain a local presence to increase pickup rates, and provide reliable communication both in North America and internationally.

September 16, 2025

Keycloak OpenID Connect Integration for the Vodia PBX

Vodia’s PBX now integrates with Keycloak OpenID Connect, providing secure single sign-on for users so they can access all connected applications without repeated authentication. Logging out from one application automatically logs the user out of all connected systems, simplifying user management and improving security. Keycloak, a Cloud Native Computing Foundation project, supports standard protocols including OpenID Connect, OAuth 2.0, and SAML, offering enterprise-grade identity and access management. To ensure proper integration, Keycloak user emails must match the corresponding PBX extension emails. Complete guidance is available in the Vodia Keycloak integration guide.

September 12, 2025

Vodia Announces Partnership with Comms Group Global

Vodia Networks has announced a strategic distribution partnership with Comms Group Global (ASX: CCG), aiming to expand the reach of its feature-rich cloud PBX solutions across APAC and EMEA. Through this collaboration, Comms Group Global will serve as an official reseller, providing businesses of all sizes with scalable, secure, and integrated telephony solutions. Customers will benefit from advanced call management features, Microsoft Teams integration, and robust security standards, while also gaining access to Comms Group’s SIP coverage in over 65 countries. The partnership enables a streamlined “one-touch” provisioning process, ensuring fast and seamless deployment for enterprises and SMEs seeking to improve efficiency.

September 8, 2025