endpoint failure in cxserver deployment

ActivePublic

Actions

Only route that explicitly returns 404 is fetchPage.

I believe TestClient needs to be added to the config.yaml or config.prod.yaml. The tests when run from command line automatically load config.dev.yaml, but that does not happen in production.

Not sure why the HTTP code is 404 though and not 500.

In P7783#45771, @Nikerabbit wrote:

Only route that explicitly returns 404 is fetchPage.

I believe TestClient needs to be added to the config.yaml or config.prod.yaml. The tests when run from command line automatically load config.dev.yaml, but that does not happen in production.

Yes, the yaml file in production should have the following lines for mt key

TestClient:
  languages: config/TestClient.yaml

Not sure why the HTTP code is 404 though and not 500.

From v1.js, getMTClient

if ( !provider ) {
	res.status( 404 ).end( 'Provider not supported' );
	return;
}