Fetching Mails - external Cron - UserAgent unchangeable

ebbi

Hello there,

let me first describe you the situation. I just got my osTicket running with my imap getting fetched autmatically with a cron.php call. So Server Setup overall seems to be fine. Anyway, fetching mails wasn't working at all for the first hours of the installation even though a cron was set up, account data were right and imap fetching was enabled everywhere.

So I did some troubleshooting. We just have shared hosting, so the cron call is one of my hoster callung the /api/cron.php. It seems like they are using an external machine for this (took me a while to figure that out..). Via logging the accesses to the cron.php I found out the IP and User Agent of the machine doing the cronjob. Anyway, I cant change anything of that to make it running with a useragent string including the API key I created for the IP since it's not under my control, so what should I do?

At the moment I just commented out:

//if (!osTicket:())

// die('cron.php only supports local cron calls - use http -> api/tasks/cron');

Does this increase the vulnerabilty significantly? Honestly I didn't take the time to go through the is_cli() function - yet..especially since it seems to be working like this at the moment.

Do you have any other idea how to be able to fetch my mails via cron and e.g. not needing to disable the check?

Thanks in advance and for that awesome product!

Regards,

ebbi

ntozier

1. create an api key in Admin panel -> manage -> api keys

2. edit the include /scripts/rcron.php included in the distribution archive.

3. put it on your server.

4. change your cron to call it instead.

ebbi

Sounded great, thanks for your reply. Sounded more than simple, wanted to excuse for not finding that on my own.. well anyway, I did that and unfortunately still can't fetch mails.

Got me the rcron.php from the setup folder, inserted it into root and edited it. Means I added the location of the cron.php (/api/cron.php or http://myurl.com/api/cron.php(http://myurl.com/api/cron.php), tried both) and the api key I inserted for my Server IP.

Nothing happened.

So I added an API for my own IP atm - changed the code in the rcron of cause as well - and called the rcron.php manually - nothing happened & blank output. Added output of the result before the preg_match

if(preg_match('/HTTP\/.* (+) .*/', $result, $status) && $status == 200)

echo 'result: '.$result;

exit(0);

produces some lines of output, basically server an session info, finalizing with the already known:

cron.php only supports local cron calls - use http -> api/tasks/cron

Same happens if I leave the API code setted for the server an call the rcron manually.

This is bugging me, can't be that complicated.. I seem to be missing something I'm afraid..

For the moment I'll have to switch back to the commented lines skipping the is_cli check.

If you've got any further ideas please let me know. I'm on the watch as well!

Greetings,

ebbi

edit: btw I rechecked that the accessing IP from the cron calling Server hasn't changed & that the services for the API (can create tickets & can execute crons) are ticked)

ebbi

... got it

Well, got it.. with the rcron call I still was calling the cron.php directly - didn't work. Reading and taking the error serious that I should call /api/tasks/cron made it happen.. by finding out the following stated in the tasks.md:

Tasks

=======

The API supports tasks execution via the HTTP API. Cron is the only supported task as the moment.

Execute Cron Job

---------------

Cron job can be executed, remotely, by making a post to `POST /api/tasks/cron`. See `scripts/rcron.php`

After I read that I finally gave it a shot and did call the tasks/api instead of the file instead and there we go - Success.

Probably this helps some others as well.

So happy to now start working with osTicket. Thanks again for pointing me to the rcron ntozier.