cloudflare records

Web Testing
,
1

Hello,
I just moved my application and now I have cloudflare ahead of me, when I pass my tests 100% testcloud does not record the videos of the failed tests, could it be some cloudflare protection?

Thank you

2 Likes
2

Problem Analysis

Yes, Cloudflare protection is very likely the cause of your video recording issue. When you moved your application behind Cloudflare, it introduced a proxy layer that can interfere with TestCloud’s ability to record videos of failed tests. This is a known issue in the Katalon community.

Why This Happens

Cloudflare acts as a security proxy that can:

  1. Block or throttle video streaming - Cloudflare’s WAF (Web Application Firewall) and bot protection can interfere with the video recording stream from TestCloud
  2. Interfere with network connectivity - Cloudflare’s security mechanisms may block certain types of traffic or connections that TestCloud uses for video capture
  3. Detect automated testing - Cloudflare’s anti-bot protection is specifically designed to detect and block Selenium/automation traffic, which TestCloud relies on

According to the Katalon Community Forum, Cloudflare actively detects and blocks Selenium-based automation, making it impossible to bypass with standard WebDriver approaches.

Solutions

Solution 1: Whitelist TestCloud IPs in Cloudflare (Recommended)

Whitelist TestCloud’s infrastructure in your Cloudflare firewall rules to allow video recording traffic:

For applications behind a firewall (publicly accessible):

  1. Whitelist NAT Gateway IPs (TestCloud outgoing traffic):

    • US Region:
      • 34.197.223.43
      • 54.82.166.185
      • 54.197.235.86
    • EU Region:
      • 3.74.38.238
      • 3.64.239.83
      • 3.122.33.200

  2. In Cloudflare Dashboard:

    • Go to Security → WAF or Firewall Rules
    • Create a new firewall rule to Allow traffic from these IPs
    • Set the action to Allow (not just “Challenge”)

Important: Simply allowing the IP in Firewall Rules may not be enough. Cloudflare’s Allow action doesn’t exclude requests from other security mechanisms (like bot detection). You may need to:

  • Disable bot detection for these IPs
  • Disable CAPTCHA challenges for these IPs
  • Whitelist the IPs in your WAF rules with higher priority

Solution 2: Use TestCloud Tunnel (For Private Networks)

If your application is in a private network, use TestCloud’s Tunnel feature:

  1. Whitelist Tunnel Server endpoints:

    • tunnel-proxy-1.katalon.com:2345 (QUIC over UDP)
    • tunnel-proxy-2.katalon.com:2345 (QUIC over UDP)
    • Allow QUIC/UDP on port 2345

  2. In Katalon TestCloud:

    • Enable the Private/Local Testing toggle
    • Configure your test to use the tunnel

Solution 3: Disable Cloudflare Protection for Testing (Temporary)

For development/testing purposes only:

  • Create a separate subdomain for testing without Cloudflare protection
  • Or temporarily disable Cloudflare’s bot detection during test runs
  • Use a test environment that bypasses Cloudflare

Key Considerations

  1. Cloudflare Bot Detection is the Main Culprit - Cloudflare’s anti-bot system specifically targets automation tools like Selenium. Simply whitelisting IPs may not be sufficient if bot detection is enabled.

  2. Video Recording Requires Stable Connections - TestCloud needs stable, uninterrupted connections to capture video. Cloudflare’s security checks can interrupt these connections.

  3. Test vs. Production - Consider using a separate testing environment without Cloudflare, or use a subdomain that bypasses Cloudflare protection for automated testing.

  4. Firewall Rules Priority - In Cloudflare, ensure your whitelist rules have higher priority than your bot detection or WAF rules.

References

Next Steps: Start by whitelisting the TestCloud NAT Gateway IPs in your Cloudflare firewall rules, then test a failed test run to see if videos are now recorded. If the issue persists, you may need to disable bot detection for those IPs or consider using a separate testing environment.

3

Cloudflare’s Bot Fight Mode or Super Bot Fight Mode detects Katalon TestCloud browsers as automated traffic, blocking video recording for failed tests by issuing challenges or dropping sessions after “Checking your browser” loops.​

Quick Fixes

  • Whitelist Katalon IPs: In Cloudflare Dashboard > Security > Bots > Bot Fight Mode, add TestCloud user agents (Katalon*) or IP ranges (contact Katalon support for latest).​
  • Disable Bot Protection: Temporarily turn off Bot Fight Mode/Super Bot Fight Mode for your domain during testing via Security > Bots > Off.​

TestCloud Workarounds

Add Desired Capabilities to Project > Settings > TestCloud > Web UI:

{
  "goog:chromeOptions": {
    "args": ["--disable-blink-features=AutomationControlled", "excludeSwitches": ["enable-automation"], "useAutomationExtension": false]
  },
  "excludeSwitches": ["enable-automation"],
  "useAutomationExtension": false
}

This hides automation fingerprints; enable Video Recorder in Project > Settings > Report > Video Recorder During Execution if using local browsers. Videos appear in TestOps under failed runs post-bypass

4

hi @services2

yes, Cloudflare can definitely be the cause. when Cloudflare is in front of the app, things like bot protection, JS challenges, or WAF rules can interfere with the TestCloud browser session. when that happens, the test may still run, but TestCloud won’t always be able to record the video for failed tests

i’d suggest checking Cloudflare security events and making sure TestCloud traffic is whitelisted or not being challenged. this is a pretty common side effect after putting Cloudflare in front of an application

5

let know us on your issue resolution