Notifications & CLI errors & network port confusion in documentation

[psyray]

Hi,

I followed the doc to install an instance on a debian server.
Take apart the bad copy/paste reported here, no problem, reconmap is running fine, except two things, notifications and cli

In the console log I find this error for the notifications

And this one for the CLI

According to your reply in the discussion of the CORS problem, I want to set up the right URL in the environment.js

But I'm stuck with the network port configuration, something weird is reported in the doc and I want to look into with you.

In the network port page of the docs you write

But in the docker-compose.yml you setup the agent config on 5520 port

So there is a conflict here, agent and notifications are on the same port.
It's a little confusing

My questions are :

• What is the good port ?
• Should I change, in the docker-compose.yml, the agent port to 5530 ?
• And the notification port ? No config in docker-compose.yml ?
• Should I create also a subdomain for the notification ? for the agent ?
• And, lastly, what url should I put into the environment.js
  Mine is actually
  

[psyray]

@santiagolizardo ping ?
I really want to fully test your awesome app, but I'm stuck with this.
Thanks

[psyray]

According to the environment.js in your demo, I've set the 2 localhost in the config above, to the main domain, the one I use to access reconmap dashboard.
But same problem.

[santiagolizardo]

Hi @psyray ; It's not well documented, but the agent and notifications service are the same, hence you see them with the same port in that example. You can optionally deploy them separately in cases where you want notifications running in one box and agent in another.
Aside of that, the problem you are getting is due to the secure websocket. Because the SECURE_TRANSPORT_ENABLED setting is set to true, it tries to use wss:// but you are probably pointing to the service directly. If you were to put it behind an nginx server and terminate the SSL there it would work. I can try to document it to make things simpler.
Hope that helps a bit. Thanks

[psyray]

Thanks for your help 😉

[psyray]

And lastly, if I understand well, in the debian install docs it miss the web socket configuration in nginx, right ?

[psyray]

Web socket seems to work with this nginx reverse proxy config on the main host (dashboard host)

location /notifications/ {
    proxy_pass http://127.0.0.1:5520;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
    proxy_set_header Host $host;
}
location /term/ {
    proxy_pass http://127.0.0.1:5520;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
    proxy_set_header Host $host;
}