Apologies, your second post stated install certbot using yum - but when I tried it, yum could not find it, but if it’s GitHub, then it would not. Hence my reasoning that certbot not installed
Hopefully IW will incorporate very soon, but only after it’s been tested
NP. I think you misread a bit still though. The plugin installs Let’s Encrypt on the system using the Let’s Encrypt Github repo to the path I just previously posted. The code that runs certbot when you use Let’s Encrypt in Interworx isn’t part of the plugin code. It’s hard coded into Interworx. That’s why I need to know exactly what’s being passed to certbot and which of the certbot exes are being used. There are more than one at that path and I already tried replacing the main certbot with a script to record stdin input then ran it from the panel but it didn’t use the main certbot program so I got no IO.
As for yum, I only mentioned it because before I realized that the git repo was already on my server as a result of the plugin/installer, I used yum to install it (The package is in one of the extended RHEL repos, I forget which one but I have them all installed). So now I have Let’s Encrypt installed to the system as well as what Interworx pulls to that other path I posted. That’s why I asked if the panel specifies the full path when running it or if it was included in the system path prior to me installing it with yum.
If those questions were answered, a patch would be easy. I’ve been sick so I haven’t felt like tinkering to figure out which file is executed by the panel’s inner code. If it’s still not fixed by the time I feel better and have a few extra minutes I’ll figure it out myself and make a bash script patch.