cloudrck

I think I'll just write a connector to the Universal Module to control some Cloudstack functions. BTW, anyone looking for a billing software that works with Cloudstack, they are insanely expensive and in my opinion a few have unreasonable pricing.

I'm going to be switching all of our services to a cloud based solution shortly. As of right now we are setting our sights on CloudStack. I would rather stick with Blesta and not have to go to the two or three competitors. Are there any plans on creating a Cloudstack Module?

Looks like a JavaScript issue. You check your browser logs? I know this has happened to me when the network was slow either on the server or my internet connection

I disagree, systemd is a drop-in replacement for SysV. You can use your SysV scripts with systemd as long as they don't declare incomplete dependencies in your LSB block. You can't please everyone, people complain when you stay the same and don't innovate, people complain when you change. Damned if you do, damned if you don't. I happen to like the clean syntax for systemd much more than SysV.

Make a shell script to dump the DB, compress and rsync the data somewhere.

Check your webserver logs and search for the file and see if there are any errors associated with it. Also, if need be check the MD5 sum of the original file. Than check the MD5 after a few upload/downloads and see if it is the same after each download or whether it changes on subsequent downloads. I haven't used PHP in a while, but I remember issues like this where PHP would write errors to the image file.

It actually is, since 1998, it's only used for legacy applications and should be avoided otherwise. SSL should be avoided when possible and TLS should be used. Gmail runs TLS over the standard port 587. Anyway, Which provider is this, your datacenter the server is located? That seems odd. What do your PHP and mail logs say? We can only speculate as to what the problem may be, but a quick look at the logs should shed some light on the issue. I'm using Mandrillapp for blesta and I don't have this problem, so sounds like a server configuration issue.

No, I didn't bother to check whether one created a username. I would still think each account required a unique email. Not a big deal I suppose

I had someone attempt to purchase services on two seperate occasions and they created two seperate accounts. But they managed to somehow use the same email address for both accounts. And since the username is the same as the email, I'm not sure how this would work for logging in. Shouldn't Blesta require each account have a unique email address?

Shouldn't there be a novalidate-cert option with whatever IMAP function Blesta is using? I don't see the point of having another company signing my certificate over me signing it.

Ok, could it be that Maxmind rejected the order? This client was obvious scammer, using an anon proxy which I have set to "review", but he made it to Bitpay, paid, and it confirmed with Bitpay. But Blesta/Maxmind appears to have not liked the order, there's a red X in the billing/overview on that order. If this is the case, why would he be allowed to pay, and if he paid why would it not show up as pending in Blesta. I'll look into it tomorrow if I have the time.

Seems as if only step 1 & 2 are being executed. INPUT INPUT Both are successful.

No, that's not the issue. The payment has been confirmed via Bitpay and the Bitcoin network, it's been three days. As I've said before, nothing has changed except for the upgrade. Blesta has no clue the payment was even pending. There's a disconnect between Bitpay & Blesta.

After upgrading from 3.3.2 to 3.4.0, I've had a new customer account pay by Bitpay, it never showed up in the Blesta control panel, not even in pending. The payment was confirmed by Bitpay, but it never made it back to Blesta. So the invoice is never marked as paid, as there is no transaction that shows up. Checking the logs through the panel shows no error messages, just one Bitpay line with one Input and one Output, both successful. I know before there is usually several for one payment. I should note that the invoice was overpaid, but not sure if that would/should make a difference. Also, seems Bitpay has created a new API since I first started using it. I'm still using the Legacy API Key, rather than the new API token system. Not sure if Blesta has changed this or not. Running Blesta v3.4.0, Debian/MariaDB/Nginx

Yeah, I had to change the primary email address at PayPal to the same address used in Blesta.

Though I agree with you, if your passwords can be brute forced before you find out the storage was hacked than you are using insecure passwords. Ideally they should be complex enough so if someone gets the hash it would take years to crack.

OKay, I'll take a look into it. Thanks

User friendly isn't always a good thing, LastPass is miles ahead of what I see from PasswordBox in terms of security. Have you found any research papers dealing with PasswordBox? If not I wouldn't touch it no matter how pretty it was.

I would use something like KeePassX to strore your credentials securely on a USB drive. I would encrypt the drive as well. You could also use something a bit easier like LastPass with 2Factor-Auth and the other security settings they have in place.

I've been having issues for the past few months that I haven't had time to investigate. For accounts who are setup on PayPal Subcriptions, their recurring payment does not get marked in Blesta. The following error appears in the logs. Running Blesta v3.2.2, Debian/MariaDB/Nginx

Can you email me the file, I'd like to take a stab at manually decoding it.

Pratically no time, both INPUT and OUTPUT time was 5:14:32 PM Yes all info has been applied. i even regenerated keys and still no luck. Yes PayPal notifing Blesta of refunds work fine.

I haven't read the PayPal API docs, but from what Blesta made it seem, it should be possible to do refunds if you have API credentials.

I don't think I've ever been able to get this functionaility to work correctly. Trying to process a PayPal refund using Blesta fails. In the Blesta logs, The INPUT is a success. The Output is a failure. https://api-3t.paypal.com/nvp a:6:{s:9:"TIMESTAMP";s:20:"2014-07-07T22:14:33Z";s:13:"CORRELATIONID";s:12:"xxxxxxxxxx";s:3:"ACK";s:7:"Failure";s:12:"L_ERRORCODE0";s:5:"10001";s:15:"L_SHORTMESSAGE0";s:14:"Internal Error";s:14:"L_LONGMESSAGE0";s:26:"Timeout processing request";}

Okay, thanks, good to know.