helix247

Hey Paul, Thanks for the reply. The firewall is disabled for testing on the server running blesta for testing purposes. Telnet connects fine on that port. According to blesta the cron taks has been stuck since 8:00 am or so this morning its now 8:45 p.m. Is there anyway I can see exactly what trouble it is running into? I have attached screenshots of settings minus user/pass/host ; telnet connecting from blesta vps, and cron showing frozen with no additional options. Thanks!

Greetings everyone! I am having a problem getting ticket imports to work using a pop3 email account. The email account is located on a cpanel server and the blesta software is on a separate vps. The pop3 account is configured using defaults like no ssl, 110 port, email account / password, and mail.exampledomain.com. I have these same credentials setup in outlook which is working. When the cron task executes for the import, it does not complete. After an hour I get the message about a stalled task on the dashboard. The automation section shows the spinning wheel but no option to kill the task. I have tried rebooting the vps and executing cron tasks manually from inside of blesta . I have also tried disabling and then re-enabling the task. I read on another post that i could go and remove the error from the database, but I think it might be better to first figure out what is causing the issue. The logs inside of blesta don't seem to indicate a problem with the task itself, the just display that it started and finished a few hours later. Any help on how I could trouble shoot this would be greatly appreciated. It is running on a VPS with Ubuntu 14.04, PHP 5.5 and NGINX if that helps at all. I compiled mailparse from source as at first their was a warning that mailparse was required, but after compiling that error no longer exists.

Thanks for the input guys. I have not been able to reproduce this so I don't know if it was a fluke. I am running behind a NAT and I am using Nginx as a revere proxy to Apache. I am not overly concerned about the IP issue. I wanted to check and see if you guys thought it was an issue from a security point of view. I think that information is not useful by itself. I just wanted to be sure it wasn't Blesta's way of pointing out a missed setting or something. Thanks again, I really love blesta!

Greetings Everyone! I have just deployed Blesta and wanted to know if this this is common. I have a user that registered using the registration form. No products or services were purchased, just a registration. I went to take a look at the logs and it shows the clients login after registering, which makes sense because they are forwarded there automatically. There then is a second login a minute later. Now, here is the kicker, the IP address for the first login is the clients. The IP address for the second login is the local IP (not public) for the server. I have not been able to reproduce this myself, so I wanted to see if this is expected.