# \[synthetics\] errors with private location with synthetics browser monitors

**URL:** <https://discuss.elastic.co/t/synthetics-errors-with-private-location-with-synthetics-browser-monitors/327094>\
**Category:** APM\
**Tags:** docker, synthetics\
**Created:** [March 6, 2023, 2:48pm UTC](https://discuss.elastic.co/t/synthetics-errors-with-private-location-with-synthetics-browser-monitors/327094 "2023-03-06T14:48:06Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![irivas95](https://avatars.discourse-cdn.com/v4/letter/i/839c29/32.png) [@irivas95](https://discuss.elastic.co/u/irivas95)\
**Post date:** [March 6, 2023, 2:48pm UTC](https://discuss.elastic.co/t/synthetics-errors-with-private-location-with-synthetics-browser-monitors/327094/1 "2023-03-06T14:48:06Z")

</div>

Hi,  
I am trying to create a monitor using a private location. I am following this [procedure](https://www.elastic.co/guide/en/observability/master/synthetics-private-location.html#synthetics-private-location-fleet-agent)

however, when I set up the monitor with the private location from the uptime page in kibana, I get the following error:

```auto
io:job could not be initialized: browser monitors cannot be created outside the official elastic docker image

```

as additional information I am using fleet server on elastic cloud 8.6 and an elastic agent 8.6 installed in a container in GCP virtual machine .

Could you help me?  
thanks in advance

---

<div class="post-metadata">

**Author:** ![Christopher\_Kaufmann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christopher_kaufmann/32/48929_2.png) [@Christopher\_Kaufmann](https://discuss.elastic.co/u/Christopher_Kaufmann)\
**Post date:** [March 9, 2023, 5:14pm UTC](https://discuss.elastic.co/t/synthetics-errors-with-private-location-with-synthetics-browser-monitors/327094/2 "2023-03-09T17:14:13Z")

</div>

Hey irivas95,  
if you want to set up a private location you need to use the `elastic-agent-complete` Docker image as described here:

> **[Monitor resources on private networks | Elastic Observability \[8.11\] | Elastic](https://www.elastic.co/guide/en/observability/current/synthetics-private-location.html#synthetics-private-location-connect)**

> Elastic provides Docker images that you can use to run Fleet and an Elastic Agent more easily. For monitors running on private locations, you _must_ use the `elastic-agent-complete` Docker image to create a self-hosted Elastic Agent node. The standard Elastic Cloud or self-hosted Elastic Agent will not work.

Hope that helps,  
Chris

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 30, 2023, 1:14pm UTC](https://discuss.elastic.co/t/synthetics-errors-with-private-location-with-synthetics-browser-monitors/327094/3 "2023-03-30T13:14:25Z")

</div>

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.