github ChrispyBacon-dev/DockFlare v1.9.4
DockFlare v1.9.4: Bug Fixes and Stability Improvements

latest releases: v2.1.7, v2.1.6, v2.1.5...
one month ago

DockFlare v1.9.4: Bug Fixes and Stability Improvements

This release is a roll-up of several important bug fixes that improve the stability and usability of DockFlare. A big thank you to the community for the detailed bug reports!

What's Fixed?

UI and Manual Rule Fixes

  • Critical Fix for Email Authentication: I've resolved a critical bug that caused an "Internal Server Error" when creating or editing rules to use the "Authenticate by Email" policy from the web UI. This was a regression from recent API updates and is now fully functional again.

Label and Service Validation Fixes

  • Auto-Redirect for Identity Providers Restored: The access.auto_redirect_to_identity=true label functionality has been fixed. A regression was preventing the correct API payload from being sent to Cloudflare, and this now works as expected.
  • Improved Support for Docker Service Names: The validation for service URLs now correctly accepts underscores (_) in hostnames (e.g., http://my_docker_service:8080), making it much easier to use with standard Docker Compose naming conventions.
  • Optional Ports for HTTP/S: The port is now optional for http:// and https:// services in your labels. If omitted, Cloudflare's default ports (80/443) will be used.
Example: Using `auto_redirect_to_identity` with Labels

Here is a practical example of how to use the auto_redirect_to_identity feature with a single Identity Provider (IdP), such as Google or Azure AD.

docker-compose.yml Example

version: '3.8'
services:
  my-app:
    image: nginx:alpine # Replace with your actual application image
    restart: unless-stopped
    networks:
      - cloudflare-net
    labels:
      # --- Core DockFlare Labels ---
      - "dockflare.enable=true"
      - "dockflare.hostname=app.YOUR_DOMAIN.com"
      - "dockflare.service=http://my-app:80"

      # --- Access Policy Labels for Auto-Redirect ---
      # 1. Set the policy to 'authenticate'
      - "dockflare.access.policy=authenticate"
      
      # 2. Enable the auto-redirect feature
      - "dockflare.access.auto_redirect_to_identity=true"

      # 3. Provide the single IdP you want to redirect to
      #    See instructions below on how to find this UUID.
      - "dockflare.access.allowed_idps=YOUR_SINGLE_IDP_UUID_HERE"

networks:
  cloudflare-net:
    # Assumes you have an external network for DockFlare
    name: cloudflare-net
    external: true

How to Find Your IdP UUID

You can find the UUID for your configured login methods (like Google, Azure AD, etc.) in the Cloudflare Zero Trust dashboard:

  1. Navigate to your Cloudflare Zero Trust Dashboard.

  2. On the left-hand menu, go to Settings -> Authentication.

  3. Under the Login methods card, find the provider you want to use and click its Edit button.

  4. Look at the URL in your browser's address bar. The UUID is the long string at the very end.

    Example URL:
    https://one.dash.cloudflare.com/ACCOUNT_ID/access/identity-providers/edit/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

This update is recommended for all users to ensure the best stability and access to all features.

For a detailed list of all changes, please see the CHANGELOG.md.

Don't miss a new DockFlare release

NewReleases is sending notifications on new releases.