Discussions

Hi Control D Team,

I’m currently using Control D under the Personal Plan, and I’m encountering significant inconsistencies with the Blocked Page Response feature—specifically when configuring between the Branded and Custom options across multiple profiles. These issues are impacting usability and reliability. as at least personal use.

🧩 Observed Issues:

1. Inconsistent Profile Behavior:

   • Setting the Branded Block Page in one profile seems to affect other profiles unpredictably.
   • Customization made in one profile (e.g., logo, title, message) do not consistently apply or persist across sessions.

2. Settings Reverting Unexpectedly:

   • After configuring a profile with specific Branded settings, revisiting the profile sometimes shows the settings have reverted to default or switched to Custom mode without user intervention.

3. Unclear Global vs. Profile-Specific Behavior:

   • The documentation suggests that Branded Block Page settings are global, but in practice, changes in one profile do not reliably propagate to others, leading to confusion.

4. Unclear AI Guidance (Barry)

   • Initially, Barry advised to “enable” the block response option for global application—however, there’s no single enable/disable toggle, just Branded or Custom modes.
   • Later, Barry stated that setting one profile should suffice for others, which causes a loop: turning off the feature in one profile leads to it reactivating across others, often with random presets.

🔧 Steps We Tried:

• Used the recommended Control D IPs According to Barry for other profiles:

  IPv4: 23.171.240.158  
  IPv6: 2606:1a40:3000:4800::158
  

• Applied the following block page customization in one single Profile's Branded Response in one profile and other's are pointed to above IPs as Custom:

  • Logo URL:
    N/A
  • Title:
    {domain} blocked by example
  • Message:
    Access to {domain} has been blocked by example for security and policy compliance. Request access if needed.

• Cleared browser cache and cookies, then re-applied Custom settings one profile at a time.

• Despite these steps, the settings continue to behave inconsistently.

🔧 Troubleshooting Steps Taken:

• Tested across multiple browsers (Firefox, Chrome, Brave) and devices, including isolated environments, to rule out cache or browser-specific issues.
• Cleared browser caches and cookies before each test.
• Attempted to configure each profile individually and observed inconsistent behavior.
• Verified that the root certificate was correctly installed on all devices.

❓ Questions:

• Is there a delay or background propagation mechanism for block response settings across profiles?
• Is this expected behavior or a possible bug in the Personal Plan dashboard?
• What is the correct method to apply profile-specific block response settings without unintentional global overrides?

💡 Suggested Improvement: Global Branded Profile Option

According to Barry’s guidance and the documentation, a single Branded profile should apply globally in the Personal Plan. To simplify configuration and avoid confusion:

• Add a “Global Branded Profile” toggle in the account or dashboard settings that, when enabled, applies the chosen block page (logo, title, message) across all profiles instantly—no per-profile edits required.
• Allow assignment of multiple block pages to different profiles only if explicitly needed (e.g., for separate teams or use cases), otherwise default to the global setting.
• Provide a clear Global vs. Profile-Specific UI distinction, so users immediately understand whether they’re editing the global block page or a profile-specific override.

This enhancement would greatly reduce complexity, prevent inadvertent overrides, and align the UI with the documented behavior.

We would greatly appreciate your assistance or clarification on this matter. Thank you for your time and support.