If you experience errors only on a dedicated environment such as
prod, dev or install, it means that cache is not fresh for
these environments. As a first try, you should always call
bin/roadizcache:clear-eprod; (replace prod by your environment)
in command line.

If you still get errors from a specific env and you are using an
OPcode cache or var cache (APC, XCache), call
clear_cache.php entry point from your browser or execute
curlhttp://localhost/clear_cache.php from your command line.

If you are using a OPCode var cache like APC, XCache, you should
purge it as Roadiz stores doctrine configuration there for better
performances, call clear_cache.php entry point from your browser or
curlhttp://localhost/clear_cache.php from your command line.

If you are behind a reverse-proxy like Varnish or Nginx proxy on a
Docker environment, IP addresses, domain name and proto (https/http)
could not be correctly set. So you will have to tell Roadiz to trust
your proxy in order to use X_FORWARDED_* env vars.

Add this line to your index.php and preview.php files after
$request=Request::createFromGlobals(); line.

$request=Request::createFromGlobals();// Existing line to get request// Trust incoming request IP as your reverse proxy for only X_FORWARDED… headers.Request::setTrustedProxies([$request->server->get('REMOTE_ADDR')],Request::HEADER_X_FORWARDED_ALL);