Feature Requests
Completed :latest

Feature Request - ignore self-signed certs

I'm running this on my LAN with self-signed certs, and am unable to download the agent through the batch file without receiving the following:

ℹ  📦 Installing required dependencies...
✅ Dependencies installed successfully!
ℹ  🚀 Installing PatchMon Agent...
ℹ     Server: https://patchmon.wapnet.local.lan
ℹ     API ID: patchmon_04a19e6c7b96ce8b
ℹ  📁 Creating configuration directory...
ℹ  📥 Downloading PatchMon agent script...
curl: (60) SSL certificate problem: self-signed certificate in certificate chain
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

I got around the first check by changing the command to curl -ks https://mypatchmon.mylan.local.net....etc, but this is a stopgap

2 Comments

Posting anonymously

audricd·7 months ago

hello,

i am running into the same issue
And unfortunately, unless I am doing something wrong, -sS -k does not help, i get exactly the same behavior: nothing. no error, but not working either.

root@sonarr:~# curl -sS -k http://patchmon.lab:3196/api/v1/hosts/install -H "X-API-ID: patchmon_cfb3b92e600682e1" -H "X-API-KEY: e381cd2f3f1613006f96e295a6c25ea3e6441452139f02f5046f3a5aa86fb7dc" | sh
INFO: Verifying system datetime and timezone...

Current System Date/Time:
   • Date/Time: Fri Jan  2 01:52:29 PM UTC 2026
   • Timezone: Etc/UTC

Non-interactive installation detected

Please verify the date/time shown above is correct.
If the date/time is incorrect, it may cause issues with:
   • Logging timestamps
   • Scheduled updates
   • Data synchronization

Continuing with installation...
SUCCESS: Date/time verification completed (assumed correct)

INFO: Starting PatchMon Agent Installation...
INFO: Server: https://patchmon.lab:3196
INFO: API ID: patchmon_cfb3b92...
INFO: Machine ID: 93b52a6e5d274dd6...
INFO: Architecture: arm64
INFO: Installing required dependencies...

INFO: Detected apt-get (Debian/Ubuntu)

INFO: Updating package lists...
Hit:1 http://deb.debian.org/debian trixie InRelease
Hit:2 http://deb.debian.org/debian trixie-updates InRelease
Hit:3 http://deb.debian.org/debian-security trixie-security InRelease
Reading package lists... Done

INFO: Installing jq, curl, and bc...
SUCCESS: All required packages are already installed

SUCCESS: Dependencies installation completed

INFO: Setting up configuration directory...
INFO: Creating new configuration directory...
INFO: Checking if agent is already configured...
SUCCESS: Agent not yet configured - proceeding with installation

INFO: Creating configuration files...
INFO: Downloading PatchMon agent binary...
root@sonarr:~# 

<img width="1737" height="909" alt="Image" src="https://github.com/user-attachments/assets/b5450c22-07d3-4eec-986d-263f71e8eb0a" />

the host remains offline, and everytime i go to it on patchmon, the pop up to set it up appears. it apparently never established connection.

clicking on fetching report does nothing.

edit:
without -k as i was saying, it literally does nothing:

root@portatimox:~# curl -s https://patchmon.lab:3196/api/v1/hosts/install -H "X-API-ID: patchmon_5108bff60f947e5f" -H "X-API-KEY: f032c2ba8a1f2fa53575e90e00d22b8f3c0ecf16c0a4f5dda5cb5a005432e4f3" | sh
root@portatimox:~# 

and by the way, i see the toggle you mentioned above @9technologygroup but only in this section:

<img width="1809" height="1330" alt="Image" src="https://github.com/user-attachments/assets/76cf7c3d-14c9-49ef-88c6-4c9b289d012c" />

whereas, i would also have expected it in the pop up to set up, not only uninstall, an agent.
but either way, it doesnt work for me.

its worth mentioning (i think): at first, when i set it up, i did NOT set up https. since... in the wizard, i only get the option to use lets encrypt. which i dont want to. only having this option, i said "no" on the wizard. set it up via http web ui. added a couple of hosts. just to make sure the product has the features i was expecting / looking for. and only then, i updated /opt/patchmon.lab/backend/.env with https in the URL for CORS, and i updated the nginx file (/etc/nginx/sites-available/patchmon.lab):

server {                                                                                                                                                                                                                                    
    listen 80;                                                                                                                                                                                                                              
    listen [::]:80;                                                                                                                                                                                                                         
    server_name patchmon.lab;                                                                                                                                                                                                               
                                                                                                                                                                                                                                            
    location /.well-known/acme-challenge/ {                                                                                                                                                                                                 
        root /var/www/acme;                                                                                                                                                                                                                 
        try_files $uri =404;

Posting anonymously

9technologygroup·11 months ago

I'm running this on my LAN with self-signed certs, and am unable to download the agent through the batch file without receiving the following:

ℹ  📦 Installing required dependencies...
✅ Dependencies installed successfully!
ℹ  🚀 Installing PatchMon Agent...
ℹ     Server: https://patchmon.wapnet.local.lan
ℹ     API ID: patchmon_04a19e6c7b96ce8b
ℹ  📁 Creating configuration directory...
ℹ  📥 Downloading PatchMon agent script...
curl: (60) SSL certificate problem: self-signed certificate in certificate chain
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

I got around the first check by changing the command to curl -ks https://mypatchmon.mylan.local.net....etc, but this is a stopgap

curl -sS -k
At the beginning of the one-line command would help however you're right, What we can do for ease is make this an option to ignore self-signed certificates and so it will give you the command to copy which suits your own environment.

I have added this to the v.1.2.7 so that in the next release we will have a toggle where if you have a self-signed cert then the command for one-liner will suit your setup.

Do you feel that would be valuable for you and others who have self-signed certs?

Posting anonymously