Skip to content
Big Daddy Access Account

Big Daddy Login and Page Troubleshooting

Match a blank page, broken layout or unexpected countdown to a specific check. Includes illustrated WARP setup for iPhone and Android.

A brass diagnostic lens over stacked blue browser tiles

Match the problem to its next check

Nothing loads
Compare with another address on the same connection.
Layout breaks
Try a current browser and note the device zoom.
Countdown is empty
Check that your browser allows JavaScript for the page.

If a page does not load

Confirm the address and test a second known page on the same network. If the connection works elsewhere, try the affected address in a new tab and note the exact message shown.

If a page loads only partly

Check whether the same page works in another current browser. Try changing a single setting at a time so you can identify which change affects the display. If a reference panel remains empty, review whether JavaScript is allowed for this site.

If a countdown looks wrong

Check the period name, device time and period ID. Refresh the page once and compare the identifier. If an issue remains, report the URL and behaviour without including account information.

Determine where the problem starts

Problems before the page title appears call for different checks from problems that happen after you tap a control. If the address never loads, check a known page on the same connection and write down the browser’s error message. If the page opens but an element stays blank, compare the same URL in another browser where you can see the full address.

Reset only what you need to test

Reload the page first and check whether the condition repeats. If a browser setting changed recently, review that setting before clearing all data. Change one thing at a time and write down what you tested. When reporting a countdown error, include the affected duration and India-time period ID and describe whether it happened on a reload, after returning to the tab, or while watching an interval end.

Only one page fails to load

Begin with the exact URL that failed. Describe precisely what you see while the relevant information is still in front of you. Next locate a known page on the same domain. These two observations answer different parts of the question, so give each its own line in your notes. If you cannot find one of them, mark it as unavailable. Filling in a missing detail from memory can make a later comparison look more certain than it really is.

Use the comparison to decide how to proceed. The practical next step is to identify whether the failure is page specific. Before doing so, pause long enough to identify what would tell you the issue is resolved. If the evidence points in two directions, retain both observations and read the surrounding instructions again. When describing the situation to someone else, start with what actually happened and finish with the outstanding question. This lets another person address the missing detail without needing access to your device, account or private records.

A prediction panel stays empty

Write a brief account in the order in which things happened. Start with the browser permission for JavaScript, then add the same period page in a second browser. Include the action you took between those observations. Two views can look inconsistent simply because they were taken at different stages of the same task. Keeping the sequence clear helps you decide whether the difference needs attention or whether you are comparing information that serves different purposes.

To follow up, record which environment shows the panel. Keep the original context available while you review the second observation. A label copied into a message may be hard to understand once the text immediately before and after it has been removed. If you are keeping a screenshot for your own use, capture the part that identifies the context as well as the part that caught your attention. When sharing a description, omit unrelated details and ask one specific question about the difference you observed.

An address redirects repeatedly

Treat this as a question with two pieces of evidence. The first is the starting URL. The second is the last address visible before the error. Check whether both pieces refer to the same person, device, page or event as appropriate. A close visual resemblance can make two separate events look connected. Look for a shared detail that actually establishes the connection before drawing a conclusion.

Once the relationship is clear, report the navigation path without personal parameters. If you need to stop partway through, keep a short private note of the point you reached and the information still missing. On returning, read that note before repeating the action. This is particularly helpful when another person is assisting you because it lets you explain which checks have already been completed. Give the helper the observation needed to answer your question and keep other information on your own device. Close the note when you have a clear answer so you can distinguish a settled question from a new occurrence.

A mobile menu will not scroll

Look closely at the location of your finger within the open menu and identify the detail that changes your interpretation. Compare it with the available height in the current orientation. Read any short labels together with the sentence or setting they belong to. The same word can describe a choice before an action, the state during it, or the record afterwards. Decide which of those stages you are looking at before you use one observation to explain the other.

A useful next action is to test the menu scroll area directly. Make the decision while you can still describe why you chose it. If the issue appears again later, check the circumstances afresh. A previous answer may depend on information that has since changed. For a follow-up report, state which part is the same as before and which part is new. This gives the reader a concrete starting point and avoids asking them to reconstruct an entire sequence from a single screen or a vague account of the outcome.

A picture is missing from a page

Use a side-by-side comparison for this case. On one side record the section containing the missing image. On the other record whether the other images on that page load. Add enough surrounding context to recognise each observation when you return to it later. If either side contains information about somebody else, use a short description in your notes and keep their personal details out of the comparison.

The purpose of the comparison is to help you identify the affected section in a report. Check whether the two observations agree on the detail that matters to your decision. If they do, move forward only as far as that agreement supports. If they do not, identify exactly what remains unclear and look for the information at its original source. Keep a distinction between something you personally observed and an explanation another person suggested. That distinction matters when a change happens quickly or when an old screenshot continues to circulate after the original page or setting has changed.

A problem disappears after a reload

Consider what you would need to explain this case to a reader who has never seen your screen. Begin with the action immediately before the failure, and describe where it appeared. Follow with the result of repeating that same action, explaining why the second observation is relevant to the first. A short, ordered explanation helps reveal whether a crucial step has been left out. If you cannot say how the two observations are connected, note that uncertainty before acting.

Your next decision is whether to record whether the symptom is reproducible. Check what information is already available and what would need to be confirmed independently. Avoid changing several things simply to see whether the problem goes away, especially when you need a clear record of its cause. Once you have made one deliberate change or checked one detail, record the outcome in a sentence. If the result is different from what you expected, keep both the expectation and the observation together for anyone reviewing your report.

1.1.1.1 with WARP setup

Choose your device. The screenshots are from an earlier app version, so labels and layouts may differ on your device.

iPhone and iPad

  1. Open the App Store

    iPhone and iPad WARP setup screenshot, step 1

    Use the store on your device and search for Cloudflare’s 1.1.1.1 app.

  2. Install and open the app

    iPhone and iPad WARP setup screenshot, step 2

    Check the developer name, install the app and review the terms when it opens.

  3. Review the VPN profile

    iPhone and iPad WARP setup screenshot, step 3

    Read the iOS system prompt before allowing the app to add a VPN configuration.

  4. Check the connection

    iPhone and iPad WARP setup screenshot, step 4

    Turn on WARP and check the status shown in the app.

Cloudflare instructions for iPhone and iPad

Android

  1. Open Google Play

    Android WARP setup screenshot, step 1

    Use Google Play on your device and search for Cloudflare’s 1.1.1.1 app.

  2. Install and open the app

    Android WARP setup screenshot, step 2

    Check the publisher, install the app and review the terms when it opens.

  3. Turn on WARP

    Android WARP setup screenshot, step 3

    Use the switch in the app to start the connection.

  4. Review the VPN request

    Android WARP setup screenshot, step 4

    Read the Android system prompt, then check the app’s connection status after responding.

Cloudflare instructions for Android