As you see in the picture the initial get token in mep-agent fails.

This is the mep-agent instance in the pod of my own user application.

The application is deployed and instantiated successfully via the web interfaces of developer and mecm platforms.

Due to failing of get token no further request through mep-agent works.

What can be the reason for this behaviour?

In case of any errors on the mep/mepauth side there are error logs see here in the code:

But no one of this logs is to read in the mepauth.log file, see picture below. There is no log entry near the timestamp from the get token failure, see picture of mep-auth.log above. So the get token request seems not to be received bei mep/mepauth. The log

`log.Info("Get token request received.")`

in the get token handler in the picture above doesn't appear in the mepauth.log even though three user applications with mep-agent are running and healthy.

Since the request is not sent to mep/mepauth, it's assumed that an error occured within

errGetMepToken := GetMepToken(auth)

in fact before the request execution.

The error can only be occured in the highlighted block in the postTokenRequest function below or in

// doRequest: do request.
func doRequest(req *http.Request) (*http.Response, error) {
	var tr = &http.Transport{
		TLSClientConfig: TLSConf,
	}
	client := &http.Client{Transport: tr}
	return client.Do(req)
}

before the request is sent.

Edit:
I debugged the startup sequence of mep-agent and found out that the request for mep/token is ended with tcp timeout:

Error code is 10060.

To confirm this behaviour I try to connect to the Nodeport of mep-api-gw and it failed as I expected.

All of other NodePorts response somehow to the curl request but the mep-api-gw service says "network unreachable".