Replies: 20 comments 3 replies
-
Server Info (please complete the following information): OS: [Ubuntu 20] Installation Method: [X ] Standard I had the same issue, and I suspect this is the root cause possibly:
Then at the end of the upgrade I had this notice:
Running the npm update as suggested produces the same error as above. Here's the output of the log file:
|
Beta Was this translation helpful? Give feedback.
-
Hmmm, I´ve got no Errors on update.sh --force: 0 verbose cli /usr/bin/node /usr/bin/npm |
Beta Was this translation helpful? Give feedback.
-
But I Do get a cross-origin error in Firefox / Chrome fomr time to time and a message about missing backend: Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf https://api.netbloks.de/core/dashinfo/. (Grund: CORS-Anfrage schlug fehl). Statuscode: (null). |
Beta Was this translation helpful? Give feedback.
-
output of |
Beta Was this translation helpful? Give feedback.
-
127.0.0.1 localhost --- BEGIN PVE ---136.243.250.101 rmm.netbloks.de rmm --- END PVE ---2a01:4f8:242:ef01::101 rmm.netbloks.de rmm 127.0.1.1 api.netbloks.de rmm.netbloks.de rem.netbloks.de api rmm rem Worked like this with 0.17.3 |
Beta Was this translation helpful? Give feedback.
-
There has been a rework of the nats-server: A missconfigured nats would explain the symptoms |
Beta Was this translation helpful? Give feedback.
-
strange,
Sorry keep replying with an old account, dont know why! Correct, nats was reworked to save cert issues and is now bound to 127.0.0.1 but I suspect your dns not set to 127.0.0.1 is effecting it |
Beta Was this translation helpful? Give feedback.
-
That makes sense. I´ve restored a backup. |
Beta Was this translation helpful? Give feedback.
-
Still no connection from Agents.
|
Beta Was this translation helpful? Give feedback.
-
For information: |
Beta Was this translation helpful? Give feedback.
-
can you try |
Beta Was this translation helpful? Give feedback.
-
Did that to no avail. |
Beta Was this translation helpful? Give feedback.
-
Is there a method to recreate the nats-Config file? |
Beta Was this translation helpful? Give feedback.
-
update with force does that, shall get back to you, are you a sponsor? |
Beta Was this translation helpful? Give feedback.
-
Yes, I am. |
Beta Was this translation helpful? Give feedback.
-
can you open a ticket please? https://support.amidaware.com |
Beta Was this translation helpful? Give feedback.
-
Done. |
Beta Was this translation helpful? Give feedback.
-
I´ve found the error: I hat the /etc/nginx/sites-enabled/rmm.conf File modified:
Since nats does not listen to localhost anymore, I had to specify 127.0.0.1 again:
|
Beta Was this translation helpful? Give feedback.
-
ah so doing something custom :) |
Beta Was this translation helpful? Give feedback.
-
to revert to the previous behavior before the nats rework, you can add the following to
just make sure ports 9235 and 4222 are not exposed publicly if you need to do this but yes this is only needed if you are doing something unsupported or custom. |
Beta Was this translation helpful? Give feedback.
-
Server Info (please complete the following information):
Installation Method:
Describe the bug
All Agents are marked as "Offline"
Remotecontrol still works
Remotecommands seem not to be working.
To Reproduce
Steps to reproduce the behavior:
Upgrade to 0.17.5
Clear all Caches etc.
Login to TRMM
All Agents offline
Expected behavior
All Agents online and doing update to newest version
Beta Was this translation helpful? Give feedback.
All reactions