sometime when you access website that has https configured in non-https mode, browser does not understand that data and instead of showing the UI it just download the content (because it expects plain text data, while that actual data is encrypted). The reverse has same issue as well, when you access an http (non encrypted) website in https mode then also the brower downloads the data instead of showing the UI, since it expects encrypted data, but website is returning plain text,.
Explicitly type your website url including the scheme (http/https) and port to fix this. This bypass browser's auto detection (its based on port, http uses port 80, while https uses port 443) and instead user overrides all those details. A typical website address (also called as URL) takes this form:
Code:
scheme://Host or IP: Port
example:
Code:
http://foobar.com:80
#or
https://10.0.0.1:443
When default port is used (80 for http and 443 for https) it can be omitted
Code:
http://foobar.com
#or
https://10.0.0.1
Since reef-pi allows user to specify both the details (port and https) it is possible mess things up, i.e. use port 443 with http or port 80 with https. Both of them is legal (i.e. reef-pi will work fine and site can be accessed if all the details in address are provided explicitly) but its highly un-conventional and create problem for users (like the download thing) when they try to access website using just IP or hostname. To examplify, if you enable https and not updated the address to use port 443, then if you just type IP or hostname as address in browser without specifying port, it will download the page (since it cant understand) instead of rendering it.
I dont know for sure if this is your problem, but just to be safe, use full
http://IP:port or
https://IP:port format to access reef-pi to avoid any confusion.