Closed cornerstoneconsulting-pro closed 3 months ago
NPM or using a another proxy isn't officially supported and not going to work out of the box. you can try looking through the unsupported section on our docs or asking for help in our Discord in the unsupported channel.
NPM or using a another proxy isn't officially supported and not going to work out of the box. you can try looking through the unsupported section on our docs or asking for help in our Discord in the unsupported channel.
Doesn't it have NPM built in by default to handle the certificates? I should also add that I can go to https://localipaddress and I can get logged in. Only using the domain name I have for it doesn't work.
Edit: https://mydomain.com gives a "This site can't be reached error", http://mydomain.com lands on the screenshot above. If I do https://localipadress it will load but with the certificate error, and http://localipaddress loads the "Welcome to Nginx" page.
Is this a new install?
To be clear Nginx which is used with TRMM is different from NPM so do you have another proxy in the mix?
Is this a new install?
To be clear Nginx which is used with TRMM is different from NPM so do you have another proxy in the mix?
Yes. I already took it down and I'm going to try and re-deploy and see how it behaves before adding the Cloudflare tunnel. If I run into it again, I'll report back with more details.
Both api and mesh open up to their respective sites, but for some reason rmm will open to the NPM Defaut Site page. And to clarify, this is when I am trying to access the site within my local network. I have gotten it to load when connecting from outside of my network with a Cloudflared tunnel. Is there supposed to be a login for the admin page to get rmm to redirect/load correctly or is this not normal behavior?