I'm trying to access z-way remotely (by hitting it directly, without using the find.z-wave.me service). As such, the domain I hit it on is different from 127.0.0.1 or find.z-wave.me, and it never loads. It works fine if I access it by using the IP address of my raspberry pi directly.
I've set it up behind nginx as a reverse proxy (but I've also tested trying to directly access it). When I try to access it, the title of the browser tab changes to "Smarthome" but no page shows up and it spins for a long time. After a few minutes, this page loads, and the Javascript console suggests that build.js never finished downloading:
Does anyone have any idea why this would happen?
Can't access z-way if it's on a different host
Re: Can't access z-way if it's on a different host
I have had an issue visually similar to what you are seeing (I didnt open up dev tools to be able to tell you if i got the same message) and the solution to my issue was to clear cookies/cache. I suspect that may not resolve your issue, but is a good idea to eliminate some browser issues.
Is there any security devices inline between the server and the browser?
Can you open <zway_ip>:8083/smarthome/app/js/build.js without any issues?
Is there any security devices inline between the server and the browser?
Can you open <zway_ip>:8083/smarthome/app/js/build.js without any issues?