Service health shows different tld name

Kobo On Your Own Server
1

When I check on https://kf.kobo.DOMAIN_NAME.ACTULA_TLD/service_health/ , I notice the tld is completely different than the the actual TLD :

OK KPI

Mongo: OK in 0.0011 seconds
Postgres: OK in 0.00685 seconds
Enketo [http://ee.kobo.DOMAIN_NAME.internal]: OK in 0.511 seconds
KoBoCAT [http://kc.kobo.DOMAIN_NAME.internal]: OK in 0.0474 seconds

----BEGIN KOBOCAT RESPONSE----
OK

Mongo: OK in 0.0183 seconds
Postgres: OK in 0.011 seconds

---- END KOBOCAT RESPONSE ----

Is this something normal in self hosted KoboToolbox, or that the .internal
was picked up by Kobotoobox somewhere else ?

Edit:
The Kobocat and Enketo are reachables using the the actual tld (ee.kobo.DOMAIN_NAME.TLD and kc.kobo.DOMAIN_NAME.TLD)

2

It’s how the services refer to each other internally; it’s normal I guess.

1 Like