• Getting passed anti-bot mechanisms

  These are 4 things to get passed most anti-bot mechanisms: Basic bypassing methods These 3 will get you passed most bot detection mechanisms, https://www.browserless.io/docs/bypass-bot-detection. Use the &headless=false flag: Some sites will check your user-agent, which by default explicitly claims you're running headless chrome, this is a dead giveaway. It can be changed by setting a specific user-agent but we highly rPopular

• It's working locally but not with browserless

  The type of issue your facing may have different root causes, is your site not loading or are you experiencing different behaviors or timeouts? Here are a couple things you can try if the site won't load properly: Use the &headless=false flag to emulate a browser window and run headful (xvsb), it also sets a use-like user agent. Some sites check your geolocation and will only display information for people in certain countrieFew readers

• Using more units than expected

  You might be using too many units because you're not closing the browser after you're done using it, and reaching the default 15-minute global timeout (consuming 30 units per browser). The quickest fix is to set the max timeout you expect your browser to run by modifying the timeout flag, this will ensure your browsers closes once this timeout is reached e.g. if your sessions take less than 10 seconds, you can setFew readers

• Increase the default timeout

  The default timeout for browser sessions on the cloud-subscription plans is set to 15 minutes. You can increase or decrease this value with the &timeout flag. On dedicated plans, you can set the maximum global timeout in the worker settings, which will apply to all your sessions or set the &timeout flag for each individual browser session.Few readers