Problems trying to add Brazilian map to metabase

Hi everyone,

I’m new on metabase and I’m trying to add brazilian map on Settings -> Admin -> Maps -> using the geoJSON link, but when I click the button “add map” it returns the error message Connexion refused by the host for URL

Does anyone knows what is going on?


Hi @LeonardoRN

Post “Diagnostic Info” from Admin > Troubleshooting.
And check the log for more details on error - Admin > Troubleshooting > Logs.
The error seems to indicate that Metabase cannot connect to the website, which could mean that you have a firewall blocking somewhere.

That link is not a GeoJSON file - that’s a website. The link to the GeoJSON file is:

Thanks flamber!
My firewall is blocking the link, so I cloned the geoJSON file to gitlab of my intranet and now I catch another error message: “Could not parse resource at URL”
Looking on the log I get the message:
:cause “Unexpected character (’<’ (code 60)): expected a valid value (number, String, array, object, ‘true’, ‘false’ or ‘null’)\n at [Source: (BufferedReader); line: 1, column: 2]”,

:message “Não foi possível parsear recurso na URL [internal address]/geodata-br/blob/master/geojson/geojs-100-mun.jsoncomo ]([internal address]/geodata-br/blob/master/geojson/geojs-100-mun.json%60como) JSON”,

:type java.lang.Exception}


@LeonardoRN My first guess is that it’s either not a valid GeoJSON file. Just like before, you are probably linking to a website, not a GeoJSON file.

Hi flamber! When I click on “openraw” on my gitlab I can see the content of the file:

I’m using metabase v 0.36.0 runnig over openshift

@LeonardoRN And what’s the URL for the “openraw”? Latest release is 0.37.2

@flamber, the URL for open raw is http://[internal_address]/geodata-br/raw/master/geojson/geojs-100-mun.json

@LeonardoRN Then use that.

Hi @flamber, I’m using that, but got the same error message:
Where you read “Não foi possível parsear recurso na URL” = “Could not parser resource at URL”

@LeonardoRN I don’t know what’s wrong with your webserver, but try a different webserver.

Thanks @flamber, I’ll try another way