Custom Iglu server not accessible from enrich

For engineers Troubleshooting
1

Hi,

my iglu-resolver.json for snowplow-enrich-kinesis looks like

{
  "schema": "iglu:com.snowplowanalytics.iglu/resolver-config/jsonschema/1-0-1",
  "data": {
    "repositories": [
      {
        "name": "my Iglu Server",
        "priority": 0,
        "vendorPrefixes": ["de.my"],
        "connection": {
          "http": {
            "uri": "https:/snowplow-iglu-prod.my.de/api",
            "apikey": "the-key"
          }
        }
      },
      {
        "name": "Iglu Central",
        "priority": 1,
        "vendorPrefixes": [ "com.snowplowanalytics" ],
        "connection": {
          "http": {
            "uri": "http://iglucentral.com"
          }
        }
      },
...

However, when the enricher tries to validate an event using my custom-schema (which is visible via https://snowplow-iglu-prod.my.de/api/schemas/de.my?repr=Uri) ) I receive the following in the bad stream:

 {
                                "repository": "my Iglu Server",
                                "errors": [
                                    {
                                        "error": "ClientFailure",
                                        "message": "Error connecting to https://localhost using address localhost:443 (unresolved: false)"
                                    }
                                ],
                                "attempts": 1,
                                "lastAttempt": "2024-03-27T13:23:06.117Z"
                            }

Any idea where it picks up the localhost?

2

:wave: I’m fairly certain the issue is that the config that enrich is using is not the one you’ve posted, for two reasons:

  • The error says it’s attempting to reach localhost
  • The config you’ve posted is missing a/ character in http://, so it would produce a different error.

So I think it’s as simple as checking that the correct config is being used, and of course correcting that small typo. :slight_smile:

3

Thanks a lot for the quick reply.
Actually it was only the missing “/”. I was too blind to see it as the error message pointed me in a different direction.

4

Glad to hear you sorted it! That error message is very misleading alright