-
Notifications
You must be signed in to change notification settings - Fork 632
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
403 Forbidden on install #523
Comments
Same issue here, have tried installing on both windows and Ubuntu
|
same on Ubuntu 20.04 which required running "npm_config_user=root npm install -g tileserver-gl" to get past some of these errors:
|
You can use |
Unfortunately, I need the full version. Is there any better solution? |
https://mapbox-node-binary.s3.amazonaws.com/@mapbox/mapbox-gl-native/v5.0.2/node-v83-linux-x64-Release.tar.gz : this .tar.gz isn't available on the stated URL anymore, or its access has now been restricted. That's what's causing tileserver-gl's installation to fail. Can someone from mapbox be contacted over this? Or, if the same .tar.gz is hosted somewhere else, then we need to edit the URL in whichever place its stored. |
Would it be possible to substitude that AWS link with something a gthub release: The version number there is different - latest is "maps-v1.6.0" . Whereas here its looking for: "@mapbox/mapbox-gl-native@5.0.2" |
But this may the one we're looking for: latest version is 5.0.2 |
Same error happens on How does one compile and install this thing from source, such that after it's done, when I do |
checked in https://github.com/mapbox/mapbox-gl-native repo found one solution here: mapbox/mapbox-gl-native#15903 to change node version to 10. Found another way forward here: mapbox/mapbox-gl-native#16485 (comment) So I git-cloned this repo, edited package.json, Addendum: Also had to replace
.. and then did It installed successfully this time. But on running with a .mbtiles file,
Giving up on this for now and trying the docker way instead. |
Did you manage to find a way to get it to work? |
@ivandza the docker way worked fine for me without any glitches. Thank heavens for containerization. sharing my docker command: docker run --name tileserver1 -d -v "$(pwd)":/data -p 7100:8080 -p 7101:80 maptiler/tileserver-gl -c config.json -b 0.0.0.0 -u "https://server.nikhilvj.co.in/tileserver/" It's up and running on https://server.nikhilvj.co.in/tileserver/ , showing all the previews properly, generating raster tiles, giving vector tiles properly when I add the vector layer in QGIS. The "$(pwd)" there puts in the current working folder in ubuntu bash. I'm keeping all the files : .mbtiles, config.json, other jsons for rasterizing etc there only Note that the operational port number changes from 80 to 8080 depending on whether you provide a config.json or not. I don't know why, but that's the way it is. here's a sample config.json which serves one .mbtiles as both vector and raster tiles: {
"options": {
"paths": {
"root": "",
"fonts": "",
"sprites": "",
"styles": "",
"mbtiles": "/data"
}
},
"styles": {
"geosadak_roads" : {
"style": "/data/geosadak_roads_style.json",
"serve_rendered": true,
"tilejson": {
"type": "overlay",
"bounds":[68.501795,8.078566,97.053463,35.392821]
}
}
},
"data": {
"geosadak_roads": {
"mbtiles": "geosadak_roads.mbtiles"
}
}
} Here is the geosadak_roads_style.json mentioned above: {
"version": 8,
"name": "geosadak_roads",
"metadata": {"maputnik:renderer": "mbgljs"},
"sources": {
"geosadak_roads": {
"type": "vector",
"url":"mbtiles://geosadak_roads.mbtiles"
}
},
"sprite": "",
"glyphs": "https://orangemug.github.io/font-glyphs/glyphs/{fontstack}/{range}.pbf",
"layers": [
{
"id": "geosadak_roads",
"type": "line",
"source": "geosadak_roads",
"source-layer": "geosadak_roads",
"paint": {
"line-width": 4,
"line-color": "rgba(255, 255, 153, 1)",
"line-opacity": 0.8
}
}
],
"id": "geosadak_roads"
} Hope this helps |
The text was updated successfully, but these errors were encountered: