Vezpi/Blog
1
0
Fork 0
Code Issues 2 Pull Requests Actions Wiki Activity

Auto-update blog content from Obsidian: 2025-10-20 10:03:04
All checks were successful
Blog Deployment / Check-Rebuild (push) Successful in 6s
Details
Blog Deployment / Build (push) Has been skipped
Details
Blog Deployment / Deploy-Staging (push) Successful in 10s
Details
Blog Deployment / Test-Staging (push) Successful in 3s
Details
Blog Deployment / Merge (push) Successful in 6s
Details
Blog Deployment / Deploy-Production (push) Successful in 9s
Details
Blog Deployment / Test-Production (push) Successful in 3s
Details
Blog Deployment / Clean (push) Has been skipped
Details
Blog Deployment / Notify (push) Successful in 2s
Details

Browse Source
This commit is contained in:
Gitea Actions
2025-10-20 10:03:04 +00:00
parent 753f72b862
commit 7d4be00d18
1 changed files with 29 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
content/post/13-migration-opnsense-proxmox-highly-available.md
View File

@@ -321,7 +321,7 @@ On both firewalls, In `System` > `Firmware` > `Plugins`, I tick the box to show
I refresh the page and, on the master, in `Services` > `Caddy` > `General Settings`: I refresh the page and, on the master, in `Services` > `Caddy` > `General Settings`:
- **Enable Caddy**: Yes - **Enable Caddy**: Yes
- **Enable Layer4 Proxy**: Yes - **Enable Layer4 Proxy**: Yes
- **ACME**: `<my mail address>` - **ACME**: `<email address>`
- **Auto HTTPS**: On (default) - **Auto HTTPS**: On (default)
There are two types of redirections, the `Reverse Proxy` and the `Layer4 Proxy`. The first one is for HTTPS only, where Caddy will manage the SSL. There are two types of redirections, the `Reverse Proxy` and the `Layer4 Proxy`. The first one is for HTTPS only, where Caddy will manage the SSL.
@@ -334,15 +334,35 @@ These services should not be exposed to everyone. In the `Access` tab, I create
Then in the `Domains` tab, I add my domains. For example, this is here I define `cerbere.vezpi.com`, my URL to reach my OPNsense WebGUI: Then in the `Domains` tab, I add my domains. For example, this is here I define `cerbere.vezpi.com`, my URL to reach my OPNsense WebGUI:
- **Enable**: Yes - **Enable**: Yes
- **Frontend**
- **Protocol**: `https://` - **Protocol**: `https://`
- **Domain**: `cerbere.vezpi.com` - **Domain**: `cerbere.vezpi.com`
- **Port**: leave empty - **Port**: leave empty
- **Certificate**: Auto HTTPS - **Certificate**: Auto HTTPS
- **Description**: OPNsense - **Description**: OPNsense
- **Access**
- **Access List**: `Internal` - **Access List**: `Internal`
- **HTTP Access Log**: Enabled - **HTTP Access Log**: Enabled
Finally in the `Handlers` tab, I define to which upstream these domains are forwarded to. Finally in the `Handlers` tab, I define to which upstream these domains are forwarded to. For `cerbere.vezpi.com` I define this:
- **Enabled**: Yes
- **Frontend**
- **Domain**: `https://cerbere.vezpi.com`
- **Subdomain**: None
- **Handler**
- **Path**: any
- **Access**
- **Access List**: None
- **Directive**
- **Directive**: `reverse_proxy`
- **Upstream**
- **Protocol**: `https://`
- **Upstream Domain**: `127.0.0.1`
- **Upstream Port**: `4443`
- **TLS Insecure Skip Verify**: Enabled
- **Description**: OPNSense
### mDNS Repeater ### mDNS Repeater