# Start Browser: Chrome not reachable❕

**URL:** <https://community.automationedge.com/t/start-browser-chrome-not-reachable/2293>\
**Category:** Self-Help & Learn\
**Tags:** rpa, article\
**Created:** [July 2, 2020, 12:34pm UTC](https://community.automationedge.com/t/start-browser-chrome-not-reachable/2293 "2020-07-02T12:34:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![aesupport](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.automationedge.com/aesupport/32/371_2.png) [@aesupport](https://community.automationedge.com/u/aesupport)\
**Post date:** [July 2, 2020, 12:34pm UTC](https://community.automationedge.com/t/start-browser-chrome-not-reachable/2293/1 "2020-07-02T12:34:51Z")

</div>

**Problem:**

> _After first run it executed, but if executed it again, get the same driver error._

- Chrome version: 83.x

- process-studio-5.5.0

- web-gui-1.5

**Solution:**

> _This happens because some drivers are running in the background. To resolve this, go through below solution:_

➡ After the execution of each web-gui workflow, click on the option **“Clear all browser instances”** from **Tools** option so that the driver running in the background gets closed properly.

![chromeInstance](https://canada1.discourse-cdn.com/flex027/uploads/automationedge/original/1X/b24e0c71ac20d4b8a80f0d5ea18123950aa81136.jpeg)

Clear the browser instance and run the process again.

Enjoy the automation with ☞ **AutomationEdge!!**

---

<div class="post-metadata">

**Author:** ![bhushan839030](https://avatars.discourse-cdn.com/v4/letter/b/9de0a6/32.png) [@bhushan839030](https://community.automationedge.com/u/bhushan839030)\
**Post date:** [May 6, 2021, 2:46am UTC](https://community.automationedge.com/t/start-browser-chrome-not-reachable/2293/2 "2021-05-06T02:46:57Z")

</div>

First option clear all browser instances then run if not run then check the start node is clicked in start browser steps.