I’m trying to use RTview on an external web server separate from my test node and running into an error with one of the .js files from RTview. The error I’m getting is:
"haskell.js:82 Uncaught DOMException: Failed to construct 'WebSocket': The URL 'ws:://xxx.xxxxxxx.xxx/websocket/' is invalid."
The issue has to do with one of RTview’s javascript files wanting to connect via websocket using an unencrypted websocket connections. My server is using certificates. I was able to override the haskell.js file to change the ws to wss using the Chrome inspector tools, but I know this is a really hacky way of doing it.
Thank you. If you make any headway, I’m curious to hear how you configured your web server. I feel like maybe there’s something missing with my Nginx reverse proxy.
This javascript file doesn’t take into account https://. I’m going to fork it and see if I can get in PR for that change for the threepenny-gui. Maybe then we can that addressed for RTView.
It looks like the owner of threepenny-gui made some fixes to the intial repo.
It still is somewhat broken, but ended up fixing it myself. Rather than waiting for everything to get applied to rt-view, I ended up building the two packages together. Maybe in the future it will get resolved for us using this over https://. On the plus side, I learned a little bit about building packages with cabal.
Here are the steps I followed on Ubuntu Linux if you’re interested:
Install cabal: `sudo apt install cabal-install
Create directory for repos: mkdir rt-view && cd rt-view
Never had this exact problem. Though I have had these full queues earliert wenn RT-View was not reachable for some time. Since 0.3 this (at least) was resolved for me. Sorry I cannot really help much here.