suggestions For Login Details When Adding Virtualmin Server To WHMCS Configuration For Automation tasks?

Hi, folks:
I’m just curious what opinions you folks have on this, or does it not matter what I do here?
What I’m wondering is what userID/password would be best to place into the server settings in WHMCS when adding the virtualmin server for automation tasks to be possible.
Would it be best to place the login details of root?
Or domain owner?
Or something else.
Just a thought their.
Also, because virtualmin will be running on the same box as WHMCS, must I spesify an external URL like:
https://domain.com:10000?
Or would something like localhost:10000 work?
I’m also not sure if the SSL factor will matter in such a situation.
Thanks!

for sure you should not use root
I created a user in webmin who is allowed to create domains/virtual servers only.
This user I added to whmcs

if its running on the same box or not, just fill in the fqdn of the box and IP, including the 10000 port.
You never know if in future you want to move the whmcs domain to its own box some day, like I did and that makes one thing less to worry about.

You do want ssl to be enabled, unless you want your passwords out in the open. besides webmin is running ssl

You want to run the whmcs domain in mode CGI not FCGI because the latter will force a reload of apache and during the process you’ll get a 500 error in the browser. though the new domain is created correctly.

Okay, so what’s the easiest way to insure that WHMCS is running in mode CGI? I’m sure that’s somewhere in the virtual server settings, but forget exactly where.

it’s in virtualmin-Server Configuration-Website Options-choose CGI Wrapper in the right pane

Ronald: Thanks.
If you could get back to me at some point, I’m trying to decide if I absolutely need to resort to the next thing on my list-weather or not to use the Pop3 mail import or whatever script that is vs piping.
I would prefer piping, as my mail system has been slammed with over 512 messages alone int he past week each time that Cron script executes on the system, but I’m not sure of how to get the pipe script to actually work.
WHMCS doesn’t help so much with specific control panel related questions like this, from what I’ve noticed.
They tend to stick to WHMCS specific stuff, but this pipe script thing is Virtualmin-specific, as the php -q stuff doesn’t seem to work properly.
They suggest for other non CPanel control panels to use the pop3 script, but I honestly dont’ care if I should or not, as I don’t want to. :stuck_out_tongue:
I can be extremely stubbern about exactly what I want to get working sometimes. LOL
But any ideas on exactly how to get this working would be appreciated so that I’m not stuck guessing for hours on end and most likely, frustrating myself all the more wile trying to go back and forth for forum responses.
Thanks much!

What I did is:
Webmin - System - Scheduled Cron Jobs and click Create a new scheduled cron job in the right pane.

Then the Command would be
GET http://domain.tld/clients/admin/cron.php
The path should be changed to your specific path

I’ve set this to 0900 AM every morning.

So, what will that do? In the meantime, if I have a user trying to email the support department etc, until this cron.php script runs, I’m assuming that they won’t get support ticket emails?

the daily cronjob is an administrative thing showing the invoices created and other stuff whmcs does. it will then send an email with the results.

Further I read your post wrong. You were talking about the support departments. These require a different cron…

you can try as command
/usr/bin/php -q /home/domain.tld/public_html/clients/pipe/pop.php (adjust your path)
then let it run every 5 minutes or so

If that isn’t working, try running it with curl:
curl http://domain.tld/clients/pipe/pop.php

I actually haven’t set that up yet after moving to a new server

khinton, I have looked into this a little more as I needed to set up the cron on my box as well.

Allthought the pop cron worked on my old box, i didn’t get it to work properly with the new one. This is due to the fact that cron is using php-cli.
php-cli doesn’t know anything about the Ioncube loader, so the script doesn’t execute.
I can not find where to tell php-cli about the ioncube loader, so I fell back on CURL, which is working fine.

The old box had an older version OS, I can not remember what I did years ago to make the suggested cron work.