FreeTakServer icon indicating copy to clipboard operation
FreeTakServer copied to clipboard

Webmap not working in AWS

Open Dnlogan87 opened this issue 10 months ago • 10 comments

Installed fresh to aws using zerotouch deployment. Install completed properly and accessing the server shows all servers running properly, however when clicking the WEBMAP tab the webmap fails to load and a message is given at the top (Cannot GET /tak-map). What should I do to fix this?

Dnlogan87 avatar Apr 19 '24 22:04 Dnlogan87

open your nodered installation and check if the IP in config is set properly https://freetakteam.github.io/FreeTAKServer-User-Docs/FreeTAKHub/WebMap/Installation/

brothercorvo avatar Apr 21 '24 19:04 brothercorvo

when I open Node Red im getting the warnings that flows stopped due to missing node types -worldmap -worldmap in.

On Sun, Apr 21, 2024, 15:23 Corvo @.***> wrote:

open your nodered installation and check if the IP in config is set properly

https://freetakteam.github.io/FreeTAKServer-User-Docs/FreeTAKHub/WebMap/Installation/

— Reply to this email directly, view it on GitHub https://github.com/FreeTAKTeam/FreeTakServer/issues/692#issuecomment-2068172378, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDMG3NOGIZHNHZYFX34JBC3Y6QGZTAVCNFSM6AAAAABGP5LZMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRYGE3TEMZXHA . You are receiving this because you authored the thread.Message ID: @.***>

Dnlogan87 avatar Apr 28 '24 16:04 Dnlogan87

Also under the manage palette, for the webmap im getting the error; SyntaxError: Unexpected Token '.' (line 203)

On Sun, Apr 28, 2024, 12:20 Demetrios Logan @.***> wrote:

when I open Node Red im getting the warnings that flows stopped due to missing node types -worldmap -worldmap in.

On Sun, Apr 21, 2024, 15:23 Corvo @.***> wrote:

open your nodered installation and check if the IP in config is set properly

https://freetakteam.github.io/FreeTAKServer-User-Docs/FreeTAKHub/WebMap/Installation/

— Reply to this email directly, view it on GitHub https://github.com/FreeTAKTeam/FreeTakServer/issues/692#issuecomment-2068172378, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDMG3NOGIZHNHZYFX34JBC3Y6QGZTAVCNFSM6AAAAABGP5LZMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRYGE3TEMZXHA . You are receiving this because you authored the thread.Message ID: @.***>

Dnlogan87 avatar Apr 29 '24 00:04 Dnlogan87

This seems like the installation failed to add dependencies, @brothercorvo have you seen this before?

naman108 avatar May 19 '24 13:05 naman108

As I said: the component used by the webmap is not installed. To solve the issue you should update node red to the current version.

brothercorvo avatar May 19 '24 17:05 brothercorvo

Same Problem here. How exactly can I update Nodered? The Nodes in the "Manage Pallette" show they are up to date.

Sebull-git avatar Jun 10 '24 12:06 Sebull-git

I had this same problem not on AWS, just in a fresh Ubuntu 22.04 container running the zero touch script. Maps were not loading. The problem appears to be that the default nodejs and nodered versions in the Ubuntu repos are ancient.

@Sebull-git I had success with the following process:

  1. Add the nodesource repo to get newer builds of nodejs following their instructions
  2. I had to uninstall the libnode-dev package because of a conflict; sudo apt remove libnode-dev.
  3. Update nodejs -- sudo apt update followed by sudo apt dist-upgrade.
  4. Update nodered sudo npm install -g --unsafe-perm node-red
  5. Restart nodered sudo systemctl restart nodered

Following that and the maps seems to work now, though no promises it didn't break something else.

It looks like the zero touch installer needs to be modified to make sure recent versions of nodejs and node-red get installed on platforms where the package repo versions are too old.

jasonmhite avatar Aug 29 '24 19:08 jasonmhite

PS: I'm still having a problem getting anything to actually display on the map. I have devices connected and they can see each other, but nothing at all displays in the web map.

jasonmhitegtc avatar Aug 29 '24 20:08 jasonmhitegtc

Ensure that the config node has the proper IP

brothercorvo avatar Aug 29 '24 22:08 brothercorvo

@brothercorvo Indeed, that worked thanks!

jasonmhitegtc avatar Aug 30 '24 16:08 jasonmhitegtc