|
| 1 | +--- |
| 2 | +title: "Defguard 2.0 is now feature-complete and entering the Beta stabilization phase." |
| 3 | +seoTitle: "Defguard 2.0 Beta 1: migration, built-in SSL, and video tutorials" |
| 4 | +description: "Defguard 2.0 Beta 1 introduces guided migration from 1.x, built-in SSL termination for Core and Edge, new certificate settings, and a video tutorial center." |
| 5 | +publishDate: 2026-04-09 |
| 6 | +author: "Robert Olejnik" |
| 7 | +image: "/images/blog/defguard-2-0-beta-1/migration.png" |
| 8 | +tags: ["product update"] |
| 9 | +draft: true |
| 10 | +--- |
| 11 | + |
| 12 | + |
| 13 | +Defguard 2.0 is now feature-complete and entering the Beta stabilization phase. |
| 14 | + |
| 15 | +Although we have been running and testing this version in production-like environments, we still recommend using it first in staging. Beta 1 includes a simple migration path from 1.x and a set of tutorial videos to make evaluation easier. |
| 16 | + |
| 17 | +If you are new to 2.0, start with the [Defguard 2.0 technical overview](https://defguard.net/blog/defguard-20-alpha-technical-overview/#why-a-major-upgrade-1) and [Alpha 2 release post](https://defguard.net/blog/defguard-2-0-release-alpha-2/). |
| 18 | + |
| 19 | +## What's changed in Beta 1 (vs Alpha 2 and Alpha 1) |
| 20 | + |
| 21 | +### Migration from 1.x |
| 22 | + |
| 23 | +Testing migration is straightforward: deploy Core 2.0 and connect it to a PostgreSQL snapshot of your existing 1.x environment. Core detects the previous setup and runs a guided step-by-step migration. |
| 24 | + |
| 25 | +The migration flow includes: |
| 26 | + |
| 27 | +1. Confirming or changing general configuration and URLs. |
| 28 | +2. Adopting Edge (previously Proxy) with the new UI-driven deployment process. |
| 29 | +3. Migrating each VPN location by deploying or upgrading a Gateway and adopting it. |
| 30 | + |
| 31 | +Make a database backup before production migration. |
| 32 | + |
| 33 | + |
| 34 | + |
| 35 | +### Defguard Core and Edge built-in SSL termination |
| 36 | + |
| 37 | +Starting in 2.0, Core and Edge can be configured with built-in SSL termination, reducing setup complexity for new deployments. |
| 38 | + |
| 39 | +#### Core SSL termination options |
| 40 | + |
| 41 | +For Core (internal Defguard URL), you can choose: |
| 42 | + |
| 43 | +- Do not configure SSL (recommended when an external reverse proxy handles TLS). |
| 44 | +- Generate certificates based on Defguard internal CA. |
| 45 | +- Upload your own certificate. |
| 46 | + |
| 47 | + |
| 48 | + |
| 49 | +Using a reverse proxy in production remains the best path for security and traffic control. |
| 50 | + |
| 51 | +#### Edge SSL termination options |
| 52 | + |
| 53 | +Edge supports the same options as Core and can additionally auto-configure a Let's Encrypt certificate via HTTP challenge when ports 80 and 443 are publicly reachable. |
| 54 | + |
| 55 | + |
| 56 | + |
| 57 | +### New certificate settings |
| 58 | + |
| 59 | +A new certificate section in settings lets you view the Defguard Root CA certificate and update SSL termination settings for both Core and Edge. |
| 60 | + |
| 61 | + |
| 62 | + |
| 63 | +### Video tutorials and contextual help |
| 64 | + |
| 65 | +Beta 1 introduces a dedicated video tutorial section where users can browse and play published tutorials. |
| 66 | + |
| 67 | + |
| 68 | + |
| 69 | +When a tutorial is relevant to a specific module, Defguard also shows a contextual button for section-specific guidance. |
| 70 | + |
| 71 | + |
| 72 | + |
| 73 | +### Easier VM/OVA upgrades |
| 74 | + |
| 75 | +We also introduced [OVA Virtual Images](https://docs.defguard.net/2.0/deployment-strategies/ova) for all-in-one testing and component-based VM deployments. |
| 76 | + |
| 77 | +Until a native self-update mechanism is available, OVA updates are handled through container image refreshes. For this, OVA includes [Dockge](https://github.com/louislam/dockge), making updates simpler from a UI. |
| 78 | + |
| 79 | +To enable Dockge: |
| 80 | + |
| 81 | +1. Enable it via Cloud Init: [Dockge docs](https://docs.defguard.net/2.0/deployment-strategies/ova#dockge) |
| 82 | +2. Open `https://<vm-ip>:5001` |
| 83 | +3. Create your Dockge credentials |
| 84 | + |
| 85 | +You can also update via SSH and Docker Compose if preferred. |
| 86 | + |
| 87 | +## Summary and release plan |
| 88 | + |
| 89 | +Beta 1 is intended to validate migration and operational workflows before the final 2.0 stable release. |
| 90 | + |
| 91 | +We plan to release 2.0.0 final after remaining minor, non-blocking bugs are resolved. You can track progress on the [2.0.0 project board](https://github.com/orgs/DefGuard/projects/5/views/23?sliceBy%5Bvalue%5D=2.0.0). |
| 92 | + |
| 93 | +Feedback from testing is highly appreciated. |
0 commit comments