austenite
-
Posts
128 -
Joined
-
Last visited
-
Days Won
8
Posts posted by austenite
-
-
-
1 hour ago, Jonathan said:
Make sure the privileges on your API token in WHM is set to all. That will fix the ACL selection issue.
Thank you!
This also resolved the issue of reseller privileges not being assigned at account creation. These API tokens seem to have taken the place of the Remote Access Key.
-
Hi there
Hoping someone else can help or has at least had this issue, reseller accounts that are meant to be activated in WHM with reseller privileges don't seem to be having the privileges applied, meaning they end up only having CPanel access until I modify the account to be given WHM access within WHM directly.
Blesta 4.2.2, CPanel module version 2.6.0, anyone else having other issues at all or able to offer some insight? I've also provisioned a couple of test accounts within Blesta with no luck, the account type within the package is set to 'Reseller'.
EDIT: I have also added another ACL in case the privs aren't being set correctly however this new ACL isn't being picked up by the CPanel module in the edit package interface when I try to switch the package to this ACL.
-
-
I was hoping someone here could lend a hand with some issues I'm having with an upgrade, currently we're running 4.1.2.
I have downloaded and performed the upgrade to both the 4.2.0 full release and to 4.2.2 and both are reported as successful although it doesn't seem to actually stick, see steps below:
[austenit@server22 myaustenite]$ wget https://account.blesta.com/client/plugin/download_manager/client_main/download/104/blesta-4.2.0.zip
[austenit@server22 myaustenite]$ unzip -o blesta-4.2.0.zip
[austenit@server22 myaustenite]$ php /home/austenit/public_html/myaustenite/index.php *hidden*/upgrade ---------------------------------------- Blesta CLI Upgrader ---------------------------------------- Upgrade from 4.1.1 to 4.1.2? (Y/N):
It's the same result regardless of which version I download, how can I upgrade past 4.1.2?
-
I can remember sharing my previous integration but never got round to sharing the new one, here it is. Let me know what you think!
- Michael, activa and Blesta Addons
-
3
-
As others have mentioned it's a start but there's still some work to do, the website looks relatively empty at the moment. If you're not much of a web designer and I'd recommend getting a theme from themeforest or hiring a designer to take care of the theme for you and then also speaking to an integration specialist to integrate the Blesta install with the website itself and finally having a professional logo created. It can be quite daunting but just stick at it and you'll get there. Good luck!
-
Oh my, Christmas has just come early.
- bunny, Michael, Blesta Addons and 1 other
-
4
-
-
@INUMIO-Rob Our site is also just good old fashioned HTML, we also got our Blesta install properly integrated and feel it really finished off the site. I would always recommend having it professionally integrated.
-
@Paul It was me who reported to you that the module works fine with Plesk Onyx, which is version 17. Prior to this we also used the module on Plesk version 12.5 with no issues either.
In both cases these were our own servers with full root access, can't imagine the OP being a reseller would make any difference. Sounds like a config error!
-
8 hours ago, Jonathan said:
Bump. Still causing issues almost daily
Hi, nice to see one of the big boys supporting Blesta!
3 hours ago, Paul said:Are you all happy with what's described in CORE-2056? I'm going to bump it into consideration for 4.1. While it's assigned to that version, there's no guarantee anything in that version will be included.
Speaking of fraud checks though, we also need to modularize this so it's easy for people to build others and drop them in. I'd love to be able to run fraud checks through multiple different APIs at once too. More advanced options like text or phone verifications would be great. Someday.
Loving the direction of this and looking forward to seeing it implemented.
-
-
@CyberHour A bit off-topic but it's annoying me. You really need to install SSL on your Blesta install on your website.
-
On 15/01/2017 at 6:48 AM, neweraweb said:
Activa,
That's a fair assessment, Blesta just feels like it was made as a billing system for VPS type offers not web hosting or anything else really.
I only expect it will get better in time, but right now that's the general feel of it.
I use it exclusively for shared hosting and feel like I have everything I need, nothing less, nothing more. It's a lightweight, no bloat, straight to the point, no gimmicky and certainly no bull**** piece of software.
I can sleep at night using the system, safe in the mind that it won't break or suddenly stop working. I receive an order during the night, Blesta checks for fraud, activates it immediately and emails the customer all the information they need. What more could you need for shared hosting? It really is a hassle free system and I've found requires less man hours to maintain than WHMCS.
Just my 2 cents
-
47 minutes ago, Dewlance.in said:
Thanks for the response, the English is quite poor in the demo so I will not be purchasing.
-
1 hour ago, Dewlance.in said:
Seems it was down for temporary time. Now you can place an order.
At ordering when I click to view the demo articles your blesta is offline with an error.
-
True, manners cost nothing!
- katycomputer, Paul, BeZazz and 2 others
-
5
-
@Dewlance.in I just went to order the articles but your billing system is down!
-
@Laflecha you could have your clients visit http://yourdomain.com:2082. Note you have to use port 2082 (unencrypted) rather 2083 (encrypted) otherwise they'll receive an SSL mismatch error.
Clients may not be comfortable logging into an unencrypted connection therefore I'd recommend just pointing them to the hostname enabled with SSL on port 2083 to login, most non tech savvy clients don't know the difference anyway.
-
-
This could be caused by the fact that you're using 'Test Client' as the cardholders name, which I assume isn't the real name. You need to use real details. I've never had this issue using Stripe though I no longer use it. I hope you're going to gain PCI Compliance before using the gateway, otherwise it's a no go.
See this information here https://support.formstack.com/customer/portal/articles/1899106
Regarding PCI Compliance
-
What control panel are you using?
-
As @Licensecart Says we utilise Blesta and use Plesk servers. Everything works as it should.
The only issue which I've reported can be seen here https://dev.blesta.com/browse/CORE-2288
CPanel ACL
in Support
Posted
Hi there
Never sold reseller accounts until recently so have only just came across this issue, but the core Blesta CPanel module doesn't appear to pass the ACL (Account Creation Limits) onto the account creation, it can create a reseller account according to the package you've assigned it. However the ACL is something that isn't defined by the package and is something I'm having to modify post account creation. These also aren't defined per the ACL Lists but have to be passed to the server on account creation from Blesta. See my screenshot for the values I'm describing, note that these values aren't defined anywhere when creating a package, nor is there any way to edit or set a 'standard value' for these within WHM. These values are set per account and therefore these have to be set at account creation, is there anyway the core module can have this sort of behaviour implemented and what are others doing to overcome this?
The WHM API token has full access.
This was previously brought up here - https://www.blesta.com/forums/index.php?/topic/7417-setting-up-whm-reseller/ but no fix actually provided, instead the poster used CPanel extended which done the job. I don't want to use the third party module, mainly because it keeps being broken, then fixed then broken and would like to stick to the official module.