# Problem with synthetic monitoring in kibana

**URL:** https://discuss.elastic.co/t/problem-with-synthetic-monitoring-in-kibana/358445
**Category:** Synthetics
**Created:** [April 29, 2024, 6:16pm UTC](https://discuss.elastic.co/t/problem-with-synthetic-monitoring-in-kibana/358445 "2024-04-29T18:16:47Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![HOrellana03](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/horellana03/32/124605_2.png) [@HOrellana03](https://discuss.elastic.co/u/HOrellana03)
#### Post date: [April 29, 2024, 6:16pm UTC](https://discuss.elastic.co/t/problem-with-synthetic-monitoring-in-kibana/358445/1 "2024-04-29T18:16:47Z")

</div>

Hello, I am new to Kibana synthetic monitoring, I have configured monitoring with Journey in 2 locations, one local and one in the cloud.  
The one that is in the cloud is running without problems.  
But for the local one, it is giving the following error.

_"journey did not finish executing, 0 steps ran: command '/usr/share/elastic-agent/.node/node/bin/elastic-synthetics elastic-synthetics --playwright-options {"page":{"setDefaultTimeout": 120}} --screenshots on --throttling {"download":5,"latency":20,"upload":3} --inline --rich-events' exited unexpectedly with code: 1"_

It should be noted that until last week, it was running without problems in both locations.

Thanks for the help.

---

<div class="post-metadata">

### Author: ![emilioalvap](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/emilioalvap/32/99310_2.png) [@emilioalvap](https://discuss.elastic.co/u/emilioalvap)
#### Post date: [May 3, 2024, 10:59am UTC](https://discuss.elastic.co/t/problem-with-synthetic-monitoring-in-kibana/358445/2 "2024-05-03T10:59:05Z")

</div>

Hi @HOrellana03,

Thanks for your interest in Synthetics!

This type of error is most commonly related to private location setup misconfigurations preventing elastic-synthetics from running. What platform is this private location running on (docker, k8s, etc)? If running in a containerized environment, what is its setup for uid/gid/fs permissions?

Also to discard some easy stuff, if you're using any string interpolation assignment, eg: `"my string ${mystring}`, please refactor it for string concatenation -\> `"my string "+ mystring` as `${}` is not supported atm and its known for breaking journey code.
