Alex Vojacek
-
Posts
90 -
Joined
-
Last visited
Posts posted by Alex Vojacek
-
-
Domain management in Blesta works if your customers have one domain they've bought at the same time as their hosting or if they've transferred the few they own and don't care about maintaining them (leaving that ICANN responsibility to you). It fails when you have a dozen+, spread across different registrars and if you're selling more exotic domain names (with the registration restrictions).
The biggest problem though is the lack of self-service option on the client side. It should be as good as what Enom or Logicboxes has to offer. Customers should be in control of their domains (contacts, DNSSEC, EPP, privacy protection, trustee service, etc.). Blesta should just sit one level above registrars, offering the huge benefit for customers of having only one system to use to manage all their domains.
It should be friendly to the customer and the admin... you nailed it on all your points.. That's EXACTLY what a billing system, or any system used for humans should be.
-
And 4.0 is to upgrade the php, framework and UI to make it better, and the small fixes and mass mailer everyone apparently needs to migrate. And then they can focus 100% on 4.1 which is (as far as I know) just revamping the domain management for people like him who "apparently" can't use the domain features.
Everyone "aparently" needs?. Blesta is NOT ICANN approved, period. And then mass mail that people "aparently" needs?.
Dude, you need to seriously reconsider the words you're using, this are not stupid request, this are in fact 2 VERY IMPORTANT features that are used almost all the time in the hosting bussiness. Lower down your tone a little, there are actual customes reading this, this is not the way to speak to them, at all.
If all of this is too complicated to do because you're doing some serious work on a future version you need to reconsider how the developer cycle is working, since you seem to be getting all your priorities wrong.
I can't put on hold essential features because I'm hoping a future version will include them and then go and ask for patience. If a customer don't see a feature he/she needs, I can't ask him/she patience because my billing doesn't support it... the customer will send me flying and get another hosting company that works the way he/she wants, period.
That's how bussiness works, re-prioritize the development cycle.
-
I left blesta because I couldn't handle domain management, at all, and the current state it is now it's almost ilegal to manage domains through blesta since it wont comply with ICANN, so... how is this feature that all the major billing systems already has, something like:
"They can't make it any faster as 4.0 isn't out and they have over 30+ tasks to do on that before they can waste a whole version on modifying and changing the way domains work. "
I stopped reading that phrase.. and I will re-phrase it. The developers CAN'T waste any more time on other features that are not as important as this one.
The sole fact that your clients are asking for this feature and you take it so lightly saying it's a WASTE doing such a task speaks volumes on what you'll get with the hosting market.
You definely made a billing system that is NOT hosting friendly at all and you don't recognize this.. no, it's even worse, you wont accept what your clients are asking for.
This attitude is not good. Clients ask for important stuff and developers should follow through and this is not an non-important feature... this is something all the other major billing systems already have and this is a feature that, as it is now it's not ICANN approved, turning all your hosting clients into an almost ilegal sellers of domains...
Developers should VERY concerned about this situation. When I left blesta, the only new feature I had was "Mass Cancelation" but I didn't have (and still isn't available) MASS EMAIL, a featured that is soo much more important than Mass Cancelation.
If I have downtime expected on the datacenter I won't be able to let my customers know about this, but, I would be able to Mass Cancel all of them if they complain !!
This is not the way you build a billing system. If I come here and seems to be complaining is because I felt I was not taking into consideration when I had my tons of problems with Blesta and developers were always doing more important stuff than the things I was asking, hence.. I left for WHMCS, when I customer goes, it should make you take notice of why it was, this is a good way of improving your attitude and your product.
Nobody asked me why I left, they lost my opinions about it the same way you'll loose the next customer that complains by replying "they can't waste time...".
-
May I suggest the developers to take this problem seriously and include the "test for the session path" onto the installer? It will save a lot of time to people who comes from a VPS trying to install blesta onto CentOS (which is the OS of choice for hosting).
Since CentOS clearly set this session path wrong, it should be mandatory to test for this to work properly before installing the software, this will avoid weird error messages (like the one I had) and the debugging should be much more easy then. -
The problem lies in blesta trying to use php include path, but the include path which is default for CentoOS does not have proper permissions, so, you have to force a path with a proper permission in there and IT WILL WORK.
I don't know what blesta is doing but i suspect it uses RSA to decode something and php is trying to put this into the session path, which not having the correct permission will not work and then php will throw an error in the RSA.
I repeat this so it's clear, Centos will NOT work on the default path, you have to manually include the path as I stated and it will work. I tried this 5 times in a row on a new VPS just to be sure it was this and I confirm it once again now.
Solution:
Put this into /etc/php.ini
include_path = /usr/share/php
make sure the directory has correct permissions and restart php and installer should work properly.
-
Ok, this is driving me nutz.
I redid the whole VPS and used Apache instead, tried apache 2.2 and apache 2.4 same thing, same error, my friend moved blesta to our interworx installation and now it's working, i want to find out WHY it's not working on my webserver, i did EVERYTHING by the rules.
Can anyone profficient enough with blesta point me in the right direction?
https://stackoverflow.com/questions/25854207/access-denied-on-paypal-ipn-verification
This guy found out that if paypal does not recive a header with at lease a User-Agent: something it wont work, i forced the header on nginx and apache to no avail...
-
That's actually a bit strange.
If you do not explicitly set the include_path setting in php.ini, the defaults do should work.
I do not set that value there myself.
Still wonder if the real problem isn't in any of your other (php-fpm related) configuration files.
And that making the setting in php.ini perhaps prevents the other configuration file from imposing the restriction, as a side effect.
But either way, glad it solved it for you.
With Linux, there is no such thing as "strange", at least in my book
-
With php.ini and include_path = /usr/share/php
Current include path: /usr/share/php Modifying include path to include: /home/blesta/alex/test/includes Include path is now: /usr/share/php:/home/blesta/alex/test/includes Success. Attempting to a include file. Should print "SUCCESS!!" below... SUCCESS!!
Centos recently installed with EPEL + remi + nginx + php-fpm default (no tweaking at all)
Current include path: .:/usr/share/pear:/usr/share/php Modifying include path to include: /home/blesta/alex/test/includes Include path is now: .:/usr/share/pear:/usr/share/php:/home/blesta/alex/test/includes Success. Attempting to a include file. Should print "SUCCESS!!" below... SUCCESS!!
Be adviced that the default "didn't" worked with me and gave me errors in RSA.
-
This is FANTASTIC news !.
I'm sure it's one more step to iron out installation issues and I'm sure a lot of people using nginx will appreciate. Thanks so much for your hard work Cody !
-
This is not my day it seems.
I did backup the database twice for blesta before doing the upgrade but now i try to restore the database backup i did on my brand new installation of blesta and i get this window:
I tried to recover the original blesta files but the same error displays.
Does anybody know how to recover from this?
-
Well, i can confirm this happens when you install nginx, since it wont have the values specified in that thread by default, in fact, it has the admin value set and not visible as default.
Just to state this for any people experiencing this issue with any VPS using nginx, you need to manually add this value to /etc/php.ini
include_path = /usr/share/php
and Blesta will install perfectly without a single hitch.
This was a really good find, it should be documented since the majority using apache wont face this issue. Thanks to all and specially to Max for finding the issue.
-
Thanks Max for finding the problem !
-
Maybe Blesta should run the server for you? bake a cake? Blesta isn't a genius sadly.
I don't mean to be rude with my problem, I already know how to manage a server, this never happened to me before, probably because the value was already set and the new packages simply removed the value and set the admin value by default.
I'm just saying this is not easy to find and probably the installler could be more specific to this problem since it WILL show it's ugly face on any VPS installation with CentOS, and I did try like 10 combinations already.
-
The val
You don't need to put in any directory, just double check the value can be overriden by code.
If your using nginx instead of Apache, check your php-fpm.conf.
Just so you know, the value is NOT there in CentOS 6.5 installing with remi repositories, is not there either if you install nginx from EPEL, it's simply not there, not the include_path nor the admin value.
I had to manually add the value as stated in the previous post, why this bug was driving me nuts !
Anyone using a clean CentoOS installation with nginx will experience this same issue.
Adding it to php-fpm.conf didn't work, it needed to be added to /etc/php.ini
-
Putting the value in php-fpm.d/blesta.conf didn't work, no matter what i do.
Switching to /etc/php.ini I put this:
include_path = /usr/share/php
That did the trick. This should be much better documented since it's not easy to find and the installation does not tell anything about this problem. It shouldn't be hard to display an error that says "please add include_path to your php.ini".
This should save days of frustration to people experiencing this problem, like me.
-
Yes, but no matter what directory i put into, it still wont work, i get stuck at the last phase of the installation.
-
I tried to replicate the problem with various CentoOS configure VPS, as per this thread
http://www.blesta.com/forums/index.php?/topic/3923-critical-keep-getting-call-to-undefined-function-crypt-random-when-trying-to-install-blesta/
Seems the install crash because the default value for nginx is not present.
you need to add this warning for any nginx user that they need to manually add:
include_path = /usr/share/php
in /etc/php.ini or blesta will FAIL to install.
-
Could sombody PLEASE HELP ME ?
I'm stuck without blesta, i can't install it, this is ludicrous, I'm doing everything by the book, there is no way blesta installs and i was able to install it perfectly previously, i don't know if it's the installer or Centos just broke something in the last updates.
I really need help, i'm without my billing software and my clients can't use it, this is seriously damaging my bussiness.
-
Nobody?
I find it really hard to understand why installing this on a simple VPS will always get me the same error. Does anyone use a VPS with blesta?. I cannot be the only one with this problem !
-
Nice, I am having the exact same issue and since you decided to just NOT put the solution I am strugling with it since 2 days ago.
Can you please provide a solution to this?
-
Hello there, i'm not new to blesta, i've been using it since more than a year now.
I always used it in a VPS configured by myself, Centos 6.5 with php 5.4 and nginx.
Everything was working just fine, up until i tried to update the license (reissue this site dashboard).
Now everything stopped working on the admin so I did a fresh reinstall.
Now each and every time i try to install it, it all goes well up to the point of asking the license, where i enter everything blesta responds with:
Call to undefined function crypt_random() on line 1660 in /home/blesta/alex/vendors/phpseclib/Crypt/RSA.php
I know i have that file and every other file in there, I already tried blesta 3.3.2 and blesta 3.4 from scratch, no luck.
All the php requirements are meet, i even tried insstalling all packages for seclib
yum install php-phpseclib*
Still no luck, this NEVER happened to me before, I tried remi packages for php 5.4, php 5.5 (with included fix in blesta) and php 5.6, they all give me the same result.
This is killing my bussiness, clients can't login since I don't have a billing system anymore, this is critical, can anybody help me?
-
No, because i've stated i'm not using Apache, i'm using nginx with no extra security or any module outside what blesta recommends.
-
I'm running latest nginx with remi repositories on CentoOS 6.5 with php-fpm.
This is all latest packages and i double checked with the nginx log and all connections are done through http 1.1
-
Yes i am using the primary e-mail address.
Blesta Warning System By Cubedata
in The Marketplace
Posted
I am sorry but WHY on earth would you want a system that penalize a customer if he doesn't pay in time?. This feels like you want to put the customer into a school regime were the admin will yell at him if he misbehaves.
I dont see this working in any meaningful way, it will just harm the customer-service provider relationship and I'm sure it will provoke more users to leave your services for good.
You don't penalize a user for late fee, PERIOD. You can add the "late-fee fee" but that's about it. I've never seen any system that worked this way, why are you trying to reinvent the wheel. Concentrate on making something that will add value to the customer instead of trying penalize them.