# Google Botguard Bypass

* *main.go : 93*

```
// change this
launcher.NewBrowser().MustGet()
// by this
u := launcher.MustResolveURL("http://127.0.0.1:9222")
rod.New().ControlURL(u).MustConnect()
```

This is necessary to use the existing debug port instead of starting a new instance! (Don't forget to import "github.com/go-rod/rod")

Then create a script to pre-launch Chrome in case of an evilginx kernel error!

* *script-chrome.sh*

```

#!/bin/bash pkill -f "google-chrome" sleep 1
mkdir -p /run/user/0 chmod 700 /run/user/0 export 
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/0/bus
google-chrome --remote-debugging-port=9222 --no-sandbox --disable-gpu --headless & CHROME_PID=$!
echo "Waiting for Chrome to start..." for i in {1..10}; do sleep 1 if curl -s 
http://127.0.0.1:9222/json > /dev/null; then echo "Chrome is ready on port 9222" # Keep Chrome running in the background disown 
$CHROME_PID exit 0 fi echo "Attempt $i..." done
echo "Failed to start Chrome after 10 attempts" kill $CHROME_PID exit 1
```

*Don't forget to do the virtual display :*

```
Xvfb :99 -screen 0 1920x1080x24 &
export DISPLAY=:99
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://rproxylab.gitbook.io/evilginx-lab-by-cfs0x/info-and-manual/google-botguard-bypass.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.