Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Web-UI is opening Chromium even though Chrome Path is set to Chrome #241

Open
joshuaheller opened this issue Feb 6, 2025 · 5 comments
Open

Comments

@joshuaheller
Copy link

I have set my Chrome Path and Use Own Browser to true. But whenever I run the Agent it is starting Chromium (blue icon) instead of my acutal chrome instance set in the .env. This is problematic because some websites detect it as a Bot and hence the Agent flow is blocked through Cloudflare captcha.

Any solutions to this?

Image

Image

Image

@warmshao
Copy link
Collaborator

warmshao commented Feb 6, 2025

I have set my Chrome Path and Use Own Browser to true. But whenever I run the Agent it is starting Chromium (blue icon) instead of my acutal chrome instance set in the .env. This is problematic because some websites detect it as a Bot and hence the Agent flow is blocked through Cloudflare captcha.

Any solutions to this?

Image

Image

Image

If you want to use your own browser, set Chrome_user_data to empty.

@joshuaheller
Copy link
Author

Okay, I tried again.

Chrome folder is set correctly:
Image

Use own browser is set
Chrome is closed.
Then Chromium is opened again:

Image

Am I missing something?

(Sorry had to re-open, accidentally closed it)

@joshuaheller joshuaheller reopened this Feb 6, 2025
@vvincent1234
Copy link
Contributor

Okay, I tried again.

Chrome folder is set correctly: Image

Use own browser is set Chrome is closed. Then Chromium is opened again:

Image

Am I missing something?

(Sorry had to re-open, accidentally closed it)

have you closed all chrome windows before running?

@joshuaheller
Copy link
Author

Yes, as I mentioned I closed Chrome.

@zxdwhda
Copy link

zxdwhda commented Feb 12, 2025

I also encountered this problem, I chose to delete all files, but not the system environment, and rewrite the configuration file .env, and now I'm successful!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants