MSR with reverse proxy

[therealdb]

Same here. I think @toggledbits is already informed.

[toggledbits]

Connection to the UI can be delayed by a slow-starting (or faulting) controller connection. That times out in 60 seconds. So it would be useful to wait a minute or two and then see if you can connect to the UI.

Either way... logs. Where are the logs? Did anybody look at the logs?

[toggledbits]

OK. I have logs from @therealdb that got me what I need, stay tuned...

[gwp1]

@toggledbits In all fairness I did glance thru them but nothing leapt out at me, primarily because I failed to timestamp when I did my deployments. Thanks @therealdb for providing the needful!

[toggledbits]

@gwp1 I'm going to add a startup troubleshooting section to the docs, but one of the other places you can look for messages is in your system's log file in /var/log. systemd will log things there as it tries to start the daemon. Synology docker users (and I imagine other NAS platforms have similar) can go into the "Details" for the container and find a Logs tab that has similar information (and command line users may find info in docker logs <container-name>).

Anyway, I've got it, rolling the respin now...

[toggledbits]

OK. 21360 has been respun. Please download new archives or containers as appropriate to your environment and try again.

[gwp1]

@toggledbits Confirmed issue is resolved. Thank you, sir!

[toggledbits]

@gwp1 said in [SOLVED] Release 21360 refuses connections after deployment:

Thank you, sir!

For breaking your system? Oh my... <embarrassed>

[toggledbits]

Can you all tell me what versions of nodejs you have running?

[gwp1]

@toggledbits v14.15.4

[wmarcolin]

@toggledbits hi!

In parts

1. NODE v17.0.1 and NPM 8.1.2;

2. New installation, follows with error I believe because of the lack of the directories that I informed in the ticket (Mantis 285) and you can see the error in the screen below;

3. Installation 21360 overwriting version 21353, working and I see that the Dynamic Groups theme works, sys_group.members information already loaded.

You mention above that in the case of Synology docker there would be another place to look for a problem log. For Windows v10 Bare Metal, is there the same facility? Could you inform it to make it easier to track?

Thanks.

[toggledbits]

Looks like you missed step 2 of the install process for Windows service. See the docs.

[wmarcolin]

@toggledbits

Please excuse me, you are absolutely right, it went unobserved, sorry.

One suggestion, in the same way that in all other commands (like step 3) you put the action with a stripe and the copy icon which makes it much easier, could you do this for step 2 in the document?

Thanks.

[toggledbits]

Yes, that would lay out much better, I agree. It will be so.

[wmarcolin]

@toggledbits hi!

A configuration doubt from the manual, in this setting:

set NODE_PATH=C:\Users\Example\Documents\Reactor

Isn't it supposed to indicate the directory where the node library is located?

set NODE_PATH=C:\Users\Example\Documents\Reactor%(#ff0000)[\node_modules]

Thanks

[toggledbits]

@wmarcolin said in [SOLVED] Release 21360 refuses connections after deployment:

Isn't it supposed to indicate the directory where the node library is located?

No, and doing so will make some components of Reactor not work.

[wmarcolin]

@toggledbits ok, thanks!