Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

image.png

I'm running the prefect service (v.2.8.3) in a container and I'm getting this error when trying to access the web service from another domain. I found this issue reporting the same error but no solution.
I've also tried setting the `PREFECT_API_URL` variable to `0.0.0.0:4200/ap`i , but it's simply ignored. Is there any solution for this?

issue: <https://github.com/PrefectHQ/prefect/issues/5648>

You need to set the `--host` or <https://docs.prefect.io/api-ref/prefect/settings/#prefect.settings.PREFECT_SERVER_API_HOST> when starting the server.

even passing the `--host` flag or declaring the `PREFECT_SERVER_API_HOST` setting to `0.0.0.0` the error persists

You’ll want that to be an actual URL that the API can be reached at from the UI user’s machine

sure, but even changing to <http://mydomain.com|mydomain.com> it returns:
```Can't connect to Server API at <http://127.0.0.1:4200/api>. Check that it's accessible from your machine.```
apparently no variable is changing this value as anything I change keeps showing the IP 127.0.0.1

Remembering that I'm running the service inside a container

resolved by setting in Dockerfile
```ENV PREFECT_SERVER_API_HOST=<http://mydomain.com|mydomain.com>" ```
instead of directly inside the container
```prefect config PREFECT_SERVER_API_HOST="<http://mydomain.com|mydomain.com>" ```

```PREFECT_UI_API_URL = Setting(
    str,
    default=None,
    value_callback=default_ui_api_url,
)
"""The connection url for communication from the UI to the API.
Defaults to `PREFECT_API_URL` if set. Otherwise, the default URL is generated from
`PREFECT_SERVER_API_HOST` and `PREFECT_SERVER_API_PORT`. If providing a custom value,
the aforementioned settings may be templated into the given string.
"""```