Closed cacpmw closed 1 year ago
I'm not very well versed in using a reverse-proxy using local domains and neither with NPM, but I think your problem lies in the fact that you defined the "https" protocol in the proxy manager, instead of regular "http". If you want to define a https between meshcentral and the reverse-proxy, you must also provide meshcentral with the appropriate certificates.
I'm not very well versed in using a reverse-proxy using local domains and neither with NPM, but I think your problem lies in the fact that you defined the "https" protocol in the proxy manager, instead of regular "http". If you want to define a https between meshcentral and the reverse-proxy, you must also provide meshcentral with the appropriate certificates.
I chose HTTPS because meshcentral uses port 443 I will try changing it to http
Update: I did everything again from scratch but now using a duckdns.org domain which allowed me to get https and it worked! Closing the issue.
I installed Mesh Central via docker following the instructions and I run all my services through nginx proxy manager. I do not own a real world domain so I always use a local domain (i.e meshcentral.homeapps.local) and all my services run on the same machine as nginx proxy manager.
Here is my container config:
Here is my NGINX PROXY MANAGER
And after this I edit my hosts file to be able to resolve the local domain
As my domains are no public I cant issue the certificate with lets encrypt (so it is said on nginx proxy manager logs)
This is what I am getting on my browser
Docker logs:
This process has always worked for me. I really dont get what it wrong I can access is through https://127.0.0.1:8086 though