Hi! First off, thanks for the wonderful bit of software!

I have a certain map in a .mbtile file that I would like to server to my app. After some fiddling around today, I got the map service running correctly on my local machine and could preview the app at localhost or a public IP if I configure my node.js server to do so. The next step was to transfer everything to Heroku, at which point the map tiles no longer seem to get served.

As far as I can tell, all the code is the same between the local version and the heroku version. I know that the server is at least somewhat functional, as I can access the metadata of the .mbtile file through the net without issue. When requesting specific map tiles however (or when trying to preview by going to [app url]/[filename]/map) my app gets a 404 response. Trying this in a browser simply returns an empty page with nothing on it. I am not sure why this happens, and unfortunately have not found much help by searching my issue. The only suspicion I have is that I may have to specify which layer to deliver the data from. Having said that, I can't explain why the local version runs fine.

UPDATE: I'm now one step closer to figuring out why this is happening. It has something to do with transmitting over https. Since yesterday I've set up my own node.js server running tilehut that is hooked up to a domain with an ssl certificate. After setting that up I confirmed the server is working as it is supposed to, since I can ping the server and request health status. I can even request and view the meta.json file of map files.

The problem comes when requesting the map tiles themselves (or trying to preview the map). When running this over the regular http server, everything works as you would expect. When running over https however, the server responds with 404 not found in my app and a blank screen in the browser. I imagine there is something in the configuration for tilehut that I need to change to properly work over https, but I'm afraid I can't quite work it out myself.