adam/Remote-Terminal-for-MeshCore
1
0 Fork 0
mirror of https://github.com/jkingsman/Remote-Terminal-for-MeshCore.git synced 2026-11-03 08:02:19 +01:00
Code Issues 26 Packages Projects Releases Wiki Activity

Issue when accessing frontend via NPM #175

New Issue
Closed
opened 2026-10-05 02:01:56 +02:00 by adam · 2 comments
adam commented 2026-10-05 02:01:56 +02:00
Owner
Copy link
Copy source

Hi, I have just installed and enabled RemoteTerm on a Raspberry PI 64bit and when I access the frontend page pointing the direct link everything works 100% fine.
However when I set the proxy NPM (Nginx Proxy Manager) in my case, I can access the frontend and I can navigate all menu, but the system says that the Radio is disconnected and acts like it is.
However the radio is still connected and when I switch to direct HTTP connection I can see it's on and works 100% fine.
If the node receives a new msg, if I use the proxy, I need to refresh the page in order to see the updated messages; so it kind of work, but not as it should be.
I tried also to include the location /meshcore/ in NPM, but ending with the same issue as without.
Is there anything that I'm making wrong when setting NPM to access RemoteTerm in HTTPS ?
Thanks, Armando

Hi, I have just installed and enabled RemoteTerm on a Raspberry PI 64bit and when I access the frontend page pointing the direct link everything works 100% fine. However when I set the proxy NPM (Nginx Proxy Manager) in my case, I can access the frontend and I can navigate all menu, but the system says that the Radio is disconnected and acts like it is. However the radio is still connected and when I switch to direct HTTP connection I can see it's on and works 100% fine. If the node receives a new msg, if I use the proxy, I need to refresh the page in order to see the updated messages; so it kind of work, but not as it should be. I tried also to include the location /meshcore/ in NPM, but ending with the same issue as without. Is there anything that I'm making wrong when setting NPM to access RemoteTerm in HTTPS ? Thanks, Armando <!-- github-sync-id:4368763081 -->
adam closed this issue 2026-10-05 02:01:56 +02:00
adam commented 2026-10-05 02:01:57 +02:00
Author
Owner
Copy link
Copy source

This sounds greatly like there is not forwarding configured for websockets. Have you configured that? I haven't used node proxy manager but whatever you use will need to forward both http and web socket traffic.

This sounds greatly like there is not forwarding configured for websockets. Have you configured that? I haven't used node proxy manager but whatever you use will need to forward both http and web socket traffic. <!-- github-comment-id:4364362865 -->
adam commented 2026-10-05 02:01:57 +02:00
Author
Owner
Copy link
Copy source

Thank you for the hint, I didn't know it needed also that.
Sure, now I have enabled Websocket support and now it works fine indeed.
Thank you again for the hint, that made it.
Cheer, Armando

Thank you for the hint, I didn't know it needed also that. Sure, now I have enabled Websocket support and now it works fine indeed. Thank you again for the hint, that made it. Cheer, Armando <!-- github-comment-id:4364406834 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#175