Replies: 1 comment 13 replies
-
|
Hello, the API "Not Found" is meant to come up, to be clear did you install using insecure or another way? becaus you cant change from insecure to using a proxy after |
Beta Was this translation helpful? Give feedback.
-
|
follow the docs and do it as it says |
Beta Was this translation helpful? Give feedback.
-
|
Just an update: I tested Mesh locally before setting up the second firewall reverse proxy, and it seems to be working. So the problem has to be with the firewall. Unfortunately, in my case, our firewall appears not to support WebSockets, which is why it's not working in the first place. |
Beta Was this translation helpful? Give feedback.
-
|
ok, so its your firewall at fault then, maybe worth looking at other proxies? |
Beta Was this translation helpful? Give feedback.
-
|
Well, what I can do is forward three random ports in the Firewall to the TRMM Server and configure nginx to listen on these ports and then forward them to port 443. But would that even work? Because the agents require port 443, don't they? |
Beta Was this translation helpful? Give feedback.
-
|
It can work on other ports but it's a lot of messing around. Best to look at alternative proxys for your network as I'm sure other systems you will use will use websockets |
Beta Was this translation helpful? Give feedback.
-
Hey guys, I've been trying to install TacticalRMM the traditional way for a few days now. I'm having some issues with figuring out how to use self-signed full-chain certificates because my firewall already has a reverse proxy that uses its own certificates. So far, I've completed the installation, and I can log in to rmm.domain.com and mesh.domain.com. However, when loading api.domain.com, I get "Not Found - The requested resource was not found on this server." Additionally, logging into Mesh Central says that the WebSocket cannot connect, and the agents won't install. Any help would be appreciated.
Beta Was this translation helpful? Give feedback.
All reactions