Tag: HonestHosting
-
Introducing Caddy Consul Plugin
Turning Consul Into Your Ingress Brain: Introducing Caddy + Consul
Modern infrastructure has a persistent problem: service discovery and ingress rarely speak the same language. You end up stitching together tools like Fabio, Envoy, or custom glue just to get traffic routed correctly.
What if your ingress layer could directly understand your service registry?
That’s exactly what Caddy + Consul delivers.
A Smarter Ingress Layer
At its core, the plugin transforms Caddy into a dynamic, service-aware ingress controller, powered entirely by HashiCorp Consul.
Instead of static configs or periodic polling, it continuously watches Consul’s catalog and health data using blocking queries — meaning:
- No manual config updates
- No reloads
- No lag between deploy and availability
Traffic routing becomes a real-time reflection of your infrastructure state.
Replace Fabio — Without Losing Compatibility
If you’ve used Fabio before, this will feel familiar — but more powerful.
- Supports
urlprefix-tags for drop-in migration - Maintains tag-driven routing semantics
- Adds richer capabilities like weighted routing and path handling
You can migrate gradually, not rewrite everything overnight.
Unified HTTP and TCP/TLS Routing
Most ingress solutions split responsibilities. This doesn’t.
With one system, you get:
- HTTP routing: host-based, path-based, wildcard domains
- TCP/TLS routing: port-based, SNI-based, TLS passthrough
- Layer 4 support via extensions like caddy-l4
This means one ingress layer for everything — web apps, APIs, and raw TCP services.
Health-Aware by Design
Routing isn’t just dynamic — it’s correct.
Only healthy services receive traffic, based on Consul’s health checks. That eliminates a whole class of failures where traffic hits dead or degraded instances.
Built for Consul Connect
If you’re using Consul Connect, the plugin integrates directly with sidecar proxies:
- Honors service mesh intentions
- Routes through secure sidecar paths
- Works alongside your existing mesh model
This bridges the gap between service mesh and ingress, without duplicating complexity.
Zero-Restart Configuration
One of the standout features: no restarts required.
All routing updates are applied live via Caddy’s admin API. That means:
- Instant propagation of new services
- No downtime during deploys
- No config reload race conditions
Conflict-Aware Routing
Dynamic systems can get messy — this one doesn’t.
- Static config always wins
- Duplicate routes resolve deterministically (“first seen wins”)
This gives you predictability without sacrificing flexibility.
Designed for Real Infrastructure
This isn’t just a plugin — it’s an architectural shift:
- Your infrastructure becomes self-describing and self-routing
- Consul becomes the source of truth
- Caddy becomes the execution layer
The Big Idea
Instead of maintaining ingress separately from your services, this approach flips the model:
Your services define the network.
Register a service in Consul, tag it appropriately, and it’s instantly routable — HTTP, TCP, TLS, all included.
Final Thoughts
If you’re running Caddy and Nomad + Consul, this plugin removes an entire layer of operational overhead.
No more syncing configs.
No more ingress drift.
No more restarts.Just declare your services — and let the network configure itself.
Next Steps
We continue to work hard to bring you the best value for all of your WordPress hosting needs. If you have any questions, concerns, or would generally like to chat, feel free to contact us anytime. We want to make sure you get the most out of HonestHosting.io!
- App Login: https://app.honesthosting.io/login
- Step-by-step Documentation: https://docs.honesthosting.io
- Live Chat & Discord Community: https://discord.gg/H5mWqsktj6
- Personalized Help: https://cal.com/kmott/hh-intro
-
Platform Update – April 2026
Another day and another month has passed–HonestHosting continues to push the state of WordPress hosting forward into the modern age. While everyone is freaking out about AI-this, Claude-that, we are over here quietly plumbing Caddy + Consul in our primary datacenter to drop request latency by 200ms, building an easy-to-use WordPress site migrator, and fixing a bug in sidekick.
CADDY CONSUL
Caddy + Consul turns your service registry into a real-time ingress layer, automatically routing traffic based on Consul service registrations and health checks. It eliminates static configs and reloads by dynamically updating routes as your infrastructure changes. Compatible with Fabio-style tags, it enables easy migration while adding support for HTTP, TCP, and TLS routing in a single system. With built-in awareness of Consul Connect and service health, it ensures traffic only reaches valid, secure backends. The result is a simpler, self-configuring network where your services define how traffic flows.
HONEST HOSTING SITE MIGRATOR
The HonestHosting Site Migrator is a WordPress plugin designed to seamlessly move existing sites into the HonestHosting platform using a modern, streaming-based approach. Instead of traditional bulky exports, it breaks site data into memory-efficient, resumable chunks and uploads them directly to S3, enabling reliable migrations even for large sites.
It handles everything from preflight validation and file/database scanning to secure transfer and final import signaling, all driven from the source site itself. The process is resilient to interruptions and even supports incremental syncs over time, making ongoing migrations or updates practical.
Overall, it’s built for scalability and automation—turning WordPress migration from a fragile, manual task into a repeatable, cloud-native workflow that integrates tightly with the HonestHosting ecosystem.
SIDEKICK BUGFIX
A recent issue in the Honest Hosting Sidekick project uncovered a subtle but important caching flaw: responses were not properly scoped by hostname, creating a risk of cross-domain cache pollution. In multi-tenant environments, this meant one site could potentially receive cached content intended for another.
The resolution was straightforward but critical—include the request hostname in the cache key to ensure strict isolation between domains. This fix reinforces correct caching behavior and prevents unintended content leakage across sites.
It’s a strong reminder that in shared infrastructure, even small cache key decisions can have major implications for correctness and security.
NEXT STEPS
We continue to work hard to bring you the best value for all of your WordPress hosting needs. If you have any questions, concerns, or would generally like to chat, feel free to contact us anytime. We want to make sure you get the most out of HonestHosting.io!
- App Login: https://app.honesthosting.io/login
- Step-by-step Documentation: https://docs.honesthosting.io
- Live Chat & Discord Community: https://discord.gg/H5mWqsktj6
- Personalized Help: https://cal.com/kmott/hh-intro