timnboys

The php 7.1 support will be coming soon due to the needed ioncube upgrade been procured finally.

which is why you need a dev license you can get free from @Paul

then talk to the developers of swiftmailer directly then? or use a cc processor that doesn't require you to use tls v1.2? as I usually only use paypal gateway since it handles both and each is handled off on paypal's site so I don't have to deal with no pci compliance which is why I am guessing you are enforcing tls v1.2 only on your mail system.

read the github issues on that: https://github.com/swiftmailer/swiftmailer/issues/598 which is suggested to do this instead: https://github.com/swiftmailer/swiftmailer/blob/5.x/lib/classes/Swift/Transport/StreamBuffer.php#L95 change this from: public function startTLS() { return stream_socket_enable_crypto($this->_stream, true, STREAM_CRYPTO_METHOD_TLS_CLIENT); } to public function startTLS() { return stream_socket_enable_crypto($this->_stream, true, STREAM_CRYPTO_METHOD_TLSv1_2_CLIENT); } that will force swiftmailer to only use tls v1.2 not any other version.

possibly they forgot to install php-mcrypt, and other related php extensions like it? as I have them installed and don't have any issues.

more debug logs from blesta then? as I would check to see what blesta is saying when sending it for your answer.

no control panel only plain ssh/cli on centos 7. and I already resolved it for myself using what I said to cam.

what mail server are you running? as I use zimbra ose as my mail server stack and don't have any problems currently with blesta & tls smtp encryption.

yep that is the root cause though when you run the cron as root that causes psr monolog to create the log files as root therefore preventing itself and apache from writing/reading it hence this error.

try running the cron as apache(if on centos) or www-data(if on ubuntu) for blesta as that resolved it for myself though aren't you related to the person who took over ftpit lol ? since people want copy & paste to fix this run this in root ssh on the vm/machine with blesta on it centos: crontab -u apache -e press insert paste line given to you by blesta for the cron press esc type :wq remember to remove the cron line from root cron if you put it in there like this: crontab -e press insert delete all lines to leave it blank. press esc type :wq fixed ubuntu: crontab -u www-data -e press insert paste line given to you by blesta for the cron press esc type :wq remember to remove the cron line from root cron if you put it in there like this: crontab -e press insert delete all lines to leave it blank. press esc type :wq fixed

I suggest @Paul @Tyson @Jono @Cody answer this for you lol.

have you not looked over the developers listed by blesta? https://www.blesta.com/development/ hint CubeData(my company) and @cyandark is on there

well according to paul both maxmind & this one could be used at once there is supposed to be a core issue for it but don't know the link off the top of my head.

the problem with explaining the module is what is there to explain about a anti fraud module like maxmind for blesta lol? though mostly I will just copy and paste what I wrote on my fraudrecord page: https://cubedata.net/fraudrecord hmm that page was more bland then I thought it was lol maybe I should point you to http://fraudrecord.com that is basically a blacklist like spamhaus you could say for bad clients who chargebacked against you, did public threats, etc(I cannot name all the reasons they can be listed for) but it is very helpful since it is basically hosting providers helping each other with valuable information on spammers,etc that you can see if there listed or not and know whether to automatically deny them or not so you do not have the headache and trouble like the provider that reported the person did. also @bdacus01 I want to say I am not very good at handling PR(Public Relations) so I apologize if the product page was lacking in information on what it does. besides I think my best "sales pitch writeup" was in my thread for it here: I admit I haven't updated the opening post with fresh screenshots from v4 of blesta but I will get to that soon enough

so are you the one that asked in my ticketing system asking about what my fraudrecord anti fraud module does lol?

ah on @cyandark's blesta or what exactly? some context would be nice

if anyone is having issues with blesta_cms not showing and showing 404 error instead you might want to try this: 3. You need to then edit the `/config/routes.php` Find: ``` if (file_exists(PLUGINDIR . "cms")) Router::route("^(?!" . $admin_loc . "|api|callback|cron|404|uploads|" . $client_loc . "|install|order|plugin|widget)", "/cms/main/index/$1"); ``` Replace with: ``` if (file_exists(PLUGINDIR . "blesta_cms")){ Router::route("^(?!" . $admin_loc . "|api|callback|cron|404|uploads|" . $client_loc . "|install|order|plugin|widget)", "/blesta_cms/main/index/$1"); } ``` I say the above because I got this part: if (file_exists(PLUGINDIR . "cms")) but I didn't notice the bolded part editing the file over putty Router::route("^(?!" . $admin_loc . "|api|callback|cron|404|uploads|" . $client_loc . "|install|order|plugin|widget)", "/cms/main/index/$1"); so once I changed it to this: Router::route("^(?!" . $admin_loc . "|api|callback|cron|404|uploads|" . $client_loc . "|install|order|plugin|widget)", "/blesta_cms/main/index/$1"); it worked I am hoping I help other people who either missed that since putty wasn't that big to see it or was tired and couldn't notice that until looking at the readme again lol

I like this idea +1

okay?......

hmm? well I will just unsuspend everything and reactivate the account since mostly I just wanted to hear from you

I don't want to cancel it mike but I wanted to verify what was happening since all of this took me by surprise it would have been helpful if you could have let me & @cyandark know what happened hopefully as we are understanding and would have worked with you and taken away all "license fee's" for you until you got back on your feet so you could "resell" licenses free until you was able to afford them again. I tagged cyandark since he didn't hear from you on blesta_cms so was very confused since neither me him or anyone heard from you until now.

don't know I cannot say what paul is currently doing but for me I am currently waiting for the funds to come for the upgrade to the ioncube encoder to enable php 7.1 encoding though for my own stuff.

Mike when you release a statement on licensecart's future please let me know since as a precautionary matter since I had no clue how this was going to pan out I disabled your account in my blesta for precautionary measures including suspending all licenses until I heard from you directly.

you got $160 to spend on upgrading to v10 encoder to enable php 7.1 encoding lol? that is probably what all devs are waiting on the funds for that lol.

try reading this I asked on there livechat?