It happens only when i connect to squidex_squidex (which is container name).
If i connect to bash inside my app container (not the one which runs squidex but, the one which runs application consuming squidex API).
And when i call:
curl -X POST -d 'grant_type=client_credentials&client_id=xxx&client_secret=xxx&scope=squidex-api' http://squidex_squidex/identity-server/connect/token
I got:
<!DOCTYPE html>
<html>
<head>
<base href="/">
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Error - Squidex Headless CMS</title>
<link rel="stylesheet" href="/styles.css" />
</head>
<body class="profile">
<div class="profile-container">
<img class="profile-logo" alt="Squidex Headless CMS" title="Squidex Headless CMS" src="/images/logo.svg" />
<div class="profile-card card">
<div class="profile-card-body card-body">
<img class="splash-image" src="/squid.svg?title=OH%20DAMN&text=I%20am%20sorry%2C%20that%20something%20went%20wrong" />
<h1 class="splash-h1">Operation failed</h1>
<p class="splash-text">
<span>We are really sorry that something went wrong.</span>
</p>
</div>
</div>
<div class="profile-footer text-center mt-4 mb-2">
<small class="text-muted">
Proudly made by<br />Sebastian Stehle and Contributors, 2016-2021
</small>
</div>
</div>
</body>
If i make the same call but instead of container name use actual domain which is used to host squidex.
curl -X POST -d 'grant_type=client_credentials&client_id=xxx&client_secret=xxx&scope=squidex-api' https://squidex.xxx.ltd/identity-server/connect/token
I got valid token.
{
"access_token": "exxxx",
"token_type": "Bearer",
"expires_in": 2591999,
"scope": "squidex-api"