[PR #172] [CLOSED] Master #1551

New issue

Closed

opened 2026-03-02 02:23:46 +03:00 by kerem · 0 comments

kerem commented

2026-03-02 02:23:46 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/amidaware/tacticalrmm/pull/172
Author: @capnjck
Created: 11/7/2020
Status: ❌ Closed

Base: develop ← Head: master

📝 Commits (10+)

3287b4a Merge branch 'develop'
081ad3c Merge branch 'develop'
29b04ee Merge branch 'develop'
4992002 Merge branch 'develop'
192e418 Merge branch 'develop'
1f77acd Merge branch 'develop'
cf0941c Merge branch 'develop'
c2a9685 Merge branch 'develop'
293f44c Release 0.1.0
4d27f2b Release 0.1.1

📊 Changes

1 file changed (+1 additions, -4 deletions)

View changed files

📝 install.sh (+1 -4)

📄 Description

When using a reverse proxy at the boarder of the network (For example, I have HAProxy on my OPNSense router, with TacticalRMM on my Proxmox host as an LXC Container), using a different certificate. The box TacticalRMM is installed on, will not look at that certificate. By default, Meshcentral will look at 'mesh.yourdomain.tld', which if the installer went through everything properly, will be pointing to 127.0.1.1. If in a situation like this, you need to change the 'CertURL' in /meshcentral/meshcentral-data/config.json to point to the boarder device, at a URL that hosts the same certificate as the mesh.yourdomain.tld does.

I could imagine this is common enough to add a note about it in the installation instructions.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/amidaware/tacticalrmm/pull/172 **Author:** [@capnjck](https://github.com/capnjck) **Created:** 11/7/2020 **Status:** ❌ Closed **Base:** `develop` ← **Head:** `master` --- ### 📝 Commits (10+) - [`3287b4a`](https://github.com/amidaware/tacticalrmm/commit/3287b4a23b03bdffd1d7bd6155bceb31211c5dbe) Merge branch 'develop' - [`081ad3c`](https://github.com/amidaware/tacticalrmm/commit/081ad3c30b4fc12e36c07e602e54b9f94d216ef5) Merge branch 'develop' - [`29b04ee`](https://github.com/amidaware/tacticalrmm/commit/29b04ee2f290731cae45e80e83f682ac32795c39) Merge branch 'develop' - [`4992002`](https://github.com/amidaware/tacticalrmm/commit/4992002a2814afa9be042f0441da0d70f764ff09) Merge branch 'develop' - [`192e418`](https://github.com/amidaware/tacticalrmm/commit/192e418d08a6873d334aa2d0d2260602f7a7fb42) Merge branch 'develop' - [`1f77acd`](https://github.com/amidaware/tacticalrmm/commit/1f77acdd22d07ed936c7c1fc9f3c31312796c093) Merge branch 'develop' - [`cf0941c`](https://github.com/amidaware/tacticalrmm/commit/cf0941cda96d253220f791688a7d740807836b32) Merge branch 'develop' - [`c2a9685`](https://github.com/amidaware/tacticalrmm/commit/c2a968548074203a4ad191ced9b5aa66f6e6273e) Merge branch 'develop' - [`293f44c`](https://github.com/amidaware/tacticalrmm/commit/293f44c91ac4c8bba9e67ecc1ad3322964c2b29d) Release 0.1.0 - [`4d27f2b`](https://github.com/amidaware/tacticalrmm/commit/4d27f2b59491f1b4576a93eca2ac70332caaa176) Release 0.1.1 ### 📊 Changes **1 file changed** (+1 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `install.sh` (+1 -4) </details> ### 📄 Description When using a reverse proxy at the boarder of the network (For example, I have HAProxy on my OPNSense router, with TacticalRMM on my Proxmox host as an LXC Container), using a different certificate. The box TacticalRMM is installed on, will not look at that certificate. By default, Meshcentral will look at 'mesh.yourdomain.tld', which if the installer went through everything properly, will be pointing to 127.0.1.1. If in a situation like this, you need to change the 'CertURL' in /meshcentral/meshcentral-data/config.json to point to the boarder device, at a URL that hosts the same certificate as the mesh.yourdomain.tld does. I could imagine this is common enough to add a note about it in the installation instructions. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>