[APP][Pro] Web Proxy - Remotely access local web pages in your Dashboards

Apps
21

It does!

1000066137
1000066137963Ɨ160 15.6 KB

22

Version 1.0.7

  • Updated app image to remove text
23

+1 for music choice :smiley:

24

Version 1.1.0

  • Added WebSocket support
25

Iā€™ve just added WebSocket support in the test version, can you try it again with this version?

26

Installed testversion, but same.message

1000066132
10000661321080Ɨ1180 53.8 KB

27

Version 1.1.1

  • Added support for dynamic script loading
28

Can you try again with the new test version?

29

Still no luck. Same message

30

How did you build the dashboard? I installed Node-RED on a Raspberry Pi but I canā€™t see where you can open the dashboard UI

31

Yes om a pi5. Go to the dashboard tab

1000066164
10000661641080Ɨ583 70.3 KB

And then:

1000066162
10000661621061Ɨ605 64.7 KB

32

I donā€™t have the option for the dashboard. Is there something specific you need to do first?

image
image321Ɨ271 7.06 KB

33

Long time ago, but got the info here back then:

34

There is a video in the first post to set up the dashboard ui

35

I was able to reproduce the issue, it appears that my proxy app doesnā€™t intercept the SocketIO requests correctly. Probably itā€™s in the domain check (which checks if the URL needs to be rewritten) which interprets socket.io as the root domain, while itā€™s just a URL on the IP of the Node-RED server.

I also see another issue with an HTML file, but Iā€™m not sure if thatā€™s intended behaviour. I will need to check that.

I will fix the issue but it might take some time because I have to check how the dashboard loads the HTML files

1 Like
36

Would be great if you can fix it!

37

I was able to fix the URL part of it, but it looks like SocketIO is very different from regular WS. It first attempts polling but that doesnā€™t work. Itā€™s likely because my web request proxy function just returns the data it receives on the web request and then closes the connection, while polling needs to send realtime data.

The WS upgrade feature of SocketIO is also not working, it looks like the connection is being closed too quickly. I donā€™t know if thereā€™s a solution for that, I would have to do some more debugging on why it closes the connection. It might be because thereā€™s simply too much latency in between the connection request and the authentication WS message, but I have to check that.

1 Like
38

I did some more testing and it appears that the web page requests the connection to be closed before itā€™s established

image
image1440Ɨ374 26.7 KB

I donā€™t know why the page doesnā€™t wait for the connection to be established, maybe it takes too long with the proxy inbetween.
While I probably canā€™t get the WS proxy to work with this page, I can try to write a function to handle the long polling that SocketIO also supports.

2 Likes
39

Hope that will be the solution, otherwise i will have to live with itšŸ˜‰. Thanks for all the work you put into it.

1 Like
40

Version 1.1.2

  • Added cookie support
  • Added redirect (302) support
  • Fixed URL constructor