How to monitor a website behind a login with Fluxguard

To monitor a website behind a login with Fluxguard, create a session that visits the login page, enters credentials through page actions, submits the form, and then visits the protected page. Fluxguard documents that cookies and local storage persist between pages in a session. Run a crawl and inspect the captured screenshot to confirm it shows the authenticated page; configuring actions alone does not prove that login succeeded. Use this only for sites you own or are authorized to access.

1. Identify the authentication type

First determine whether the site uses an HTML login form or browser-level HTTP Basic Authentication. Fluxguard documents separate setup paths:

• Form login: add actions that target the username field, password field, and submit control.
• Basic authentication: enter credentials under Session Settings → Crawl → authentication fields.

These instructions do not establish compatibility with every MFA challenge, CAPTCHA, identity-provider redirect, or custom authentication policy. Validate the actual authorized site with a crawl.

2. Configure a form login in Fluxguard

1. Add the login page to a session. Run an initial crawl so Fluxguard captures the page before login. This gives you a baseline view and a place to configure actions.
2. Inspect the login controls. Use Fluxguard’s Visual Selector or inspect the page in a modern browser to identify the username input, password input, and submit control.
3. Add the actions. Configure the username field with the account’s username, the password field with its password, and an action to submit the form. Use the selectors that match the actual page.
4. Prefer stable selectors. A short selector based on a stable ID, name, or other distinctive attribute is generally less coupled to layout than a long path through many nested elements. Fluxguard’s tutorial warns that deeply hierarchical selectors can break when the layout changes. Check that each selector uniquely identifies the intended control.
5. Allow the page to settle. Increase the post-submit wait when the site needs time to navigate or load its dashboard. Fluxguard’s tutorial gives 6,000 milliseconds as an example, not a universal setting; choose a delay based on the site’s observed behavior.
6. Save the actions and order the pages. Place protected pages after the login step in the session. Fluxguard says pages in a session run in sequence and preserve cookies and local storage between pages.
7. Run a verification crawl. Open the resulting capture and inspect its screenshot. Confirm that it contains account-specific or otherwise clearly authenticated content rather than a login form, loading screen, or access-denied page.

If you need to capture both the pre-login page and the authenticated view of the same URL, Fluxguard’s tutorial suggests adding the login page twice in the session: once for the initial page and once after the login actions.

3. Configure browser Basic Authentication

For a browser-level Basic Authentication challenge, use Fluxguard’s session settings rather than form-field actions:

1. Open Session Settings.
2. Go to the Crawl tab.
3. Enter the credentials in the authentication fields.
4. Save the settings, run a crawl, and verify the captured page is the expected protected content.

If the site presents a regular HTML form, use the form-action workflow instead. A browser authentication prompt and an in-page login form are different mechanisms.

4. Check the capture and monitor changes

After a successful verification crawl, review the session’s capture history and comparison views for later runs. Fluxguard’s console guide describes text, rendered HTML, screenshot or pixel, and network comparison information. Choose the comparison that answers your monitoring question: rendered changes for visual regressions, text or HTML for content changes, and network details when a page’s requests help explain a failed or unexpected capture.

Check the screenshot after changes to the login flow, page layout, or selectors. A crawl that completes can still capture the wrong state, such as a login page or an intermediate redirect.

5. Keep credentials and access in scope

• Monitor only sites you own or have permission to access. Fluxguard’s tutorial explicitly limits product use to authorized sites.
• Use an account with only the access needed for the pages being monitored, where your site’s account policy permits it.
• Do not put credentials into selectors or page URLs. Enter them only in the designated action or authentication fields.
• If your organization requires MFA, an identity provider, or other access controls, check that the chosen workflow is allowed by your policy and verify the result. The cited Fluxguard documentation does not promise universal support for those flows.

6. Troubleshooting

Symptom	Likely cause	What to check
The capture still shows the login form	A selector did not match, the submit action did not run, credentials were rejected, or the page was captured before login finished.	Inspect the capture, confirm each selector targets the intended element, check the credentials and submit control, and increase the post-submit wait if the site is slow.
A selector worked and then stopped	The site changed its markup or layout, or the selector depended on a long chain of parent elements.	Reinspect the current page and replace the selector with a shorter, unique match. Run a new verification crawl.
The dashboard is captured, but a later protected page is logged out	The target may not be ordered after the login page, or the session’s state may not be available in the flow as configured.	Confirm the page sequence and verify the login page’s capture first. Fluxguard documents cookies and local storage persisting across session pages.
The screenshot shows a spinner, partial page, or empty content	The site may need more time after submission or before the protected content renders.	Increase the post-submit wait and run another crawl. Verify the resulting screenshot rather than assuming the delay is sufficient.
Basic Authentication does not unlock the page	The site may use an HTML form instead of a browser-level Basic Authentication challenge, or the credentials may be incorrect.	Identify the actual challenge type. Use form actions for an HTML form and the Crawl authentication fields for Basic Authentication.
An MFA, CAPTCHA, or identity-provider flow blocks the session	The flow may require an interaction or challenge not covered by the documented setup.	Do not assume compatibility. Check the site’s access policy and validate the authorized flow; consult Fluxguard support or documentation for that specific case.

7. Reliability, timing, and plan considerations

Login monitoring depends on more than whether the target URL responds: credentials must remain valid, selectors must keep matching, and the authenticated page must finish loading before capture. Recheck the capture after login-page redesigns, password rotations, or changes to redirects and account policy. Fluxguard’s tutorial gives 6 seconds only as an example wait, so tune the delay to the site rather than applying it blindly.

Fluxguard’s pricing page lists Form Submission Tracking for monitoring behind logins and gated content in its Standard plan feature list. It also states that paid plans begin with a seven-day free trial and prices are in US dollars. Plan details and prices can change; confirm the live pricing page before choosing a plan. The documentation provides no benchmark or universal compatibility guarantee for authenticated sites.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. It captures public pages with one request; it is not a replacement for Fluxguard’s documented logged-in session workflow when the target requires credentials. For a public page or a page accessible without a login, the API call is:

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

See the ScreenshotNeo API documentation for the request options and response details. ScreenshotNeo removes cookie banners, popups, and chat widgets before the shot. Bot checks, blank pages, and failed loads are never billed. Its MCP server gives AI agents tools to take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Sign up for 1,000 free screenshots a month, no card required.

FAQ

Can I monitor both the login page and the page after login?

Yes. Fluxguard’s tutorial suggests adding the login page twice when the session should capture it both before and after login, then placing protected pages after the login actions.

Does a successful crawl mean the login worked?

No. Open the capture and confirm the screenshot shows the authenticated content you intended to monitor.

Does Fluxguard document support for every MFA or CAPTCHA flow?

No universal compatibility is established by the cited tutorial. Test the authorized site and consult the product’s current guidance for the specific flow.