cloudrck

This works in Nginx.

Does anyone else have issues trying to upload files via the Support Manager in Blesta? Uploads work fine using Nginx/PHP and Nginx/RoR with plain HTTP. But with Blesta and HTTPS it doesn't seem to work.
 
 
The folder is writable.
Blesta gives this error
 
Nginx logs
2013/12/17 08:14:51 [warn] 2651#0: *50775 an upstream response is buffered to a temporary file /var/lib/nginx/fastcgi/7/05/0000000057 while reading upstream, client: 111.111.111.111, server: my.cloudrck.com, request: "GET /admin/clients/viewinvoice/23/107/ HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "my.cloudrck.com", referrer: "https://my.cloudrck.com/admin/clients/view/23/" 2013/12/18 04:17:46 [warn] 2650#0: *58956 an upstream response is buffered to a temporary file /var/lib/nginx/fastcgi/8/06/0000000068 while reading upstream, client: 111.111.111.111, server: my.cloudrck.com, request: "GET /client/invoices/view/105/ HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "my.cloudrck.com", referrer: "https://my.cloudrck.com/client/" 2013/12/18 13:29:55 [error] 2653#0: *63423 client intended to send too large body: 1670524 bytes, client: 111.111.111.111, server: my.cloudrck.com, request: "POST /client/plugin/support_manager/client_tickets/reply/108/ HTTP/1.1", host: "my.cloudrck.com", referrer: "https://my.cloudrck.com/client/plugin/support_manager/client_tickets/reply/108/" I've searched online and saw a few people with the same issues but with no solution. This appears to be an issue with using SSL. My client_max_body_size setting doesn't seem to matter.

I was deciding between Hugo and Jekyll. Jekyll is more popular, but Hugo is gaining in popularity. I looked at both and was drawn more to Hugo, partly because Hugo is so much faster in terms of building the site with around ~1ms write time per page. The entire site is written in about 700ms and ready for deployment. I do also like that Hugo's built in server automatically refreshes the site when you save changes, though I'm not sure if Jekyll does this or not.

Ok, thanks

The code is encrypted for licensing purposes, so sorry the source code won’t be released, and we won’t be going anywhere as I put my heart, blood and soul into my business and if the worst came to the worst we would most likely pass it onto the developers

I just force https on the apache file (HSTS)

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.

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.

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.

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

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

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.

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 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";}

Should be automatically created if the upload folder is 777 or 666 or whatever when installing the plugin.

There will always be bad players, whether malicious or negligent. Unfortunately, it will result in calls for government regulation. Rather, I suggest people do their research on exchanges before doing business with them, and diversify. Never put all your coins in the same place. Don't leave large deposits in exchanges, transfer them out into wallets you control. Never use a hosted wallet.

If you go around on Bitcoin/crypto related forums, you'll see people warning against MtGox a while back. They never knew what they were doing from the beginning, just trying to cash in on the bandwagon jumpers, it was only a matter of time before their incompetence caught up with them.

This will mark all tickets in all departments closed.
UPDATE `support_tickets` SET `status` = 'closed' Are you wanting to close them in a single department only? If so then you'll need to find the department ID in the 'support_departments' table and use the following. Where the number 1 is you'll need to change it to the department ID of choice:
UPDATE `support_tickets` SET `status` = 'closed' WHERE `department_id` = '1'

That's it, thanks. I was too lazy to go through the database and figure this out myself.
Yes, but I didn't want to go through 10 pages and delete tickets

I'm still working on how the market works, thinking about using http://www.middlecoin.com/ for max profitability. I should be getting the card soon (prices went up again, go figure) and I got a new 1000W PSU)
 
The only other issue I have to worry about is electricity use, at the moment this is what my usage amounts to for my entire household. I will see  how this fairs when my new equipment gets here.

I bumped up the engine clock from 800Mhz to 900Mhz, upped the voltage +0.025 and changed settings to
cgminer --scrypt -o stratum+tcp://lite.wemineltc.com:3334 -u cloudrck.1 -p x -I 13 -w 128 --shaders 512 --thread-concurrency 4000 Now I'm getting 150Kh/s with a 4 degrees C increase in temperature at the moment.

You're overlooking the real issue. Whether or not a certificate message appears or not the connection is still unsecure. You don't want to spend $8 for an SSL cert? Then get a free Class 1 at StartSSL. There is no reason to not spend a few bucks for added security. You shouldn't even consider forcing HTTP, if I see someone can't take the effort to get a SSL certificate I move right along.
 
 
Learn what your Nginix code means and understand what it does before you use it. Than you will understand why it isn't giving you the desired result. Than get a SSL cert.