Troubleshooting
Common issues and solutions when running figranium.
1. Browser fails to launch#
Error: Failed to launch browser: Chromium revision is not downloaded.
- Cause: Playwright needs specific browser binaries.
- Fix (Docker):
- Rebuild the image:
docker compose build --no-cache.
- Rebuild the image:
- Fix (NPM):
- Run
npx playwright install chromium.
- Run
Error: Protocol error (Target.detachFromTarget): Target closed.
- Cause: The browser crashed due to memory limits.
- Fix:
- Increase Docker memory:
--memory="2g" --shm-size="1g". - Use
--disable-dev-shm-usageflag (figranium does this by default).
- Increase Docker memory:
2. Proxies not working#
Error: ERR_PROXY_CONNECTION_FAILED
- Cause: Invalid proxy credentials or network firewall.
- Fix:
- Verify proxy server address and port.
- Check
Settings > Proxiesfor connectivity status (future feature). - Ensure your server can reach the proxy (check outbound rules).
3. Element not found#
Error: Timeout 30000ms exceeded while waiting for selector ".foo"
- Cause: The selector is incorrect or the element loads dynamically.
- Fix:
- Use Headful Debugging to inspect the page live.
- Increase
waittime before the action. - Use
wait_selectorexplicitly. - Check for iframes (figranium does not support cross-origin iframes yet).
4. Session Expired frequently#
Error: You are logged out repeatedly.
- Cause:
SESSION_SECRETchanged (server restart).- Cookies are blocked by browser.
- Fix:
- Set a static
SESSION_SECRETin.env. - Ensure
SESSION_COOKIE_SECUREmatches your protocol (HTTP vs HTTPS).
- Set a static
5. CAPTCHA / Bot Detection#
Error: Page shows a CAPTCHA or "Access Denied".
- Cause: The site detected automation.
- Fix:
- Enable Stealth Mode options in Task Editor.
- Use high-quality Residential Proxies.
- Rotate User Agents.
- Add random
waittimes between actions.