EidolonHost

Ah, nice... good to know. Hopefully it'll come out soon because I know one thing for sure: It'll help us spot domains that have illegal installations of Blesta and report them.

Blesta doesn't have one yet. It's however on the to-do list.

Hi, Blesta Devs!
 
It would be awesome if you guys could help the VestaCP developers create a method for Blesta to communicate with VestaCP, or vice versa.
 
VestaCP's website says they already work with WHMCS... though I don't have a WHMCS instance to test this claim. But I would suggest that this might be a good idea to have in place early.
 
Right now though, I'm working on figuring out how to integrate VestaCP with the Universal Module, but it would be amazing to have a VestaCP module directly from the Blesta devs.
 
Sidenote: You guys are amazing. Seriously, amazing.

Excellent, that's a beautiful combination.

The problem is that we do not have any set up to test other that cpanel. This is the main hurdle that prevented us in creating a generic module.
If someone has a testing environment we will be happy to extend it. 
We will make incrementally, let's say next DA then Webmin and so on .

I started mining bitcoins this weekend, wow the difficulty level has increased dramatically with these ASIC processors. I should have jumped on this bandwagon years ago.
 
Is there any interest in the hosting community for Litecoins (LTC)? Just curious, it seems to be the most popular altcoin.

Yeah, I noted that it should work in addition to maxmind, not one or the other.

This is only the beginning.

-facepalms- I should've realized that. Thanks for the pointer.
 
Changed my portal about to look much better. Man, I keep forgetting how customizable Blesta is... WHMCS is not exactly as easily customizable, really. Thanks for the guide to customizing the portal.

You need: http://docs.blesta.com/display/user/Universal+Module#UniversalModule-InputRules
 
In 3.1 they have improved it so much that I've heard.

You'll need SMTP not sure how you'd do that then mate. Paul and the guys might be able to help you

Are you using cPanel.
 
Make a email address via cPanel > Mail > Email Accounts.
 
Then go to the cPanel > Mail > Forwarders
 
Add forwarder
 
Then enter:
 
Address to Forward:  Emailaddress @domain.com
 
Advanced Options.
 
Pipe to a Program: /usr/bin/php /home/username/public_html/plugins/support_manager/pipe.php plugin/support_manager/ticket_pipe/index/1
 
Add Forwarder.
 
----
Make sure the department has it set-up:
 
Go to: admin/plugin/support_manager/admin_departments/
 
Edit the department
 
Email: youremail @domain.com (From above)
 
Select piping. 
 
Done.
 
----
 
On the templates just enter the email you wish them to come from. 

Yeah I understand mate, I try to put that on my website .

No problem glad to have been of assistance.
 

License to only shows the company name, in the settings.
 
 
1. Yeah I agree would be nice to show you that it's updated like we have on the reseller portal (License key updated: owned-000000000000000000)
 
2. Should be active else it will show a error that your not licensed.
 
3. If you by from a reseller like myself, we provide the support, and you get support here on the forum. If you are a Blesta customer you can contact them via the client area ticket system or here.
 
4. Same as 3.

My post was one of those that got ate. No big deal, I'll remake.
 
At least we had a recent backup to work with... so that's good to know. I was wondering why my post disappeared until I went and found my e-mail with the link, which directed me to here. Nice, that.

Zomex is doing Blesta designs and integrations?!
 
Awesome, I can keep my business with Zomex, then. I was hoping I wouldn't have to look elsewhere for a template.

Not sure if they have API docs. I suspect they do, also, apologies on the late response.
 
 
Yup, Russian. Though they're working on translating it into English and other languages. Good to know that you found the WHMCS one... I should've found that, myself. Obviously though, I didn't think about it. Heh.
 
Edit: Looking at the module in question, it's in English... and that is a very good thing. Also unencoded!
 
I imagine you could do a Blesta one, based on this...
 
Edit2:
 
Chrome auto-translated for me:
 
In the panel, it has a full API, but unfortunately, the documentation on how to use it is not ready yet. I'll try to briefly describe the key points, but if something is not clear, ask. in the folder / usr / local / vesta / bin scripts are located, which are both functions of the API. If you need to create a user, you need a script v-add-user, if you want to delete the database, it will make the script v-delete-database, and so on, by analogy. In other words, if you do ls / usr / local / vesta / bin, then you can get an idea of the options available. If you run the script without any parameters, it issues a statement on the use of:
 
[Root @ V-test ~] # V-Add-User Error: not enought arguments Usage: V-Add-User USER PASSWORD EMAIL [PACKAGE] [FNAME] [LNAME]  
Each script returns return_code. If return_code is 0, then the operation completed successfully. Any other number will indicate an error. Actual table return codes can always be found in the file / usr / local / vesta / func / main.sh
 
OK=0 E_ARGS=1 E_INVALID=2 E_NOTEXIST=3 E_EXISTS=4 E_SUSPENDED=5 E_UNSUSPENDED=6 E_INUSE=7 E_LIMIT=8 E_PASSWORD=9 E_FORBIDEN=10 E_DISABLED=11 E_PARSING=12 E_DISK=13 E_LA=14 E_FTP=15 E_SSH=16 E_DB=17 E_RRD=18 E_UPDATE=19 E_RESTART=20 UNIX API inspired ideas and therefore all information is stored in plain text files. Each script solves only one task. Upon successful completion of the script, for nothing is displayed. If an error occurs, the script immediately exits and displays a message on the screen. Returning to the creation of user and check the return code.
 
[Root @ V-test ~] # V-Add-User Error: not enought arguments Usage: V-Add-User USER PASSWORD EMAIL [PACKAGE] [FNAME] [LNAME] [root @ V-test ~] # echo $? 1 From Table 1 above it E_ARGS, which means that an insufficient number of arguments. Optional parameters are enclosed in brackets kvadtratnye. To successfully create a user need only 3 azadt argument - user name, password, and email address. If the package is not specified, will be replaced by the default package, which is called the default.
 
[Root @ V-test ~] # V-Add-User Demo d3mo0p4ssw0rd demo@vestacp.com [root @ V-test ~] # echo $? 0 In addition to the categories of scripts for creating and changing, there is a category for display, such sripta fall into the pattern v-list-*. Scripts can display information in several formats. Currently, these 3 formats: shell, plain and json. The first two are convenient to work from the command line.
 
[Root @ V-test ~] # V-list-users Shell USER PACKAGE U_DISK U_BANDWIDTH SUSPENDED DATE ----------------------------- ------------------------- admin Default no 2013-02-11 3 0 1 0 Default test no 2013-03-10 Demo Default 0 0 no 2013-03-18 The third format is used for the operation of the web interface, which work uses the same API. For the operation of the web-based interface to the system is installed an additional web server nginx and php-fpm, to handle php. All requests made ​​under the user interface admin, which is allowed to serve api via sudo. now specifically try to answer your question about the creation of users. There are 2 options: 1) You can ipolzovat api directly executing scripts in / usr / local / vesta / bin, as it makes the web interface 2) You can use the wrapper-om the web interface to access the api. In most cases, the second option would be relevant. Further about it. By the way, just recently been implemented billing system integration WHMSC its wrapper-a. In the module for whmcs implemented key features that interest you and probably. The module is able to: * Create Customer service area * delete users * change the user's password * add web / mail / dns domain to wrapper-u need to handle POST requests, passing the user name and password admin. Here are a few examples of the most vsotrebovannyh:
 
# Create user Add a user to a domain Delete user domains including its https://server-ip/api/?&user=admin&password=currentpwd&cmd=v-delete-user&arg1=demo  
And reproduced for you here, in English for the most part.

Hi, Blesta Devs!
 
It would be awesome if you guys could help the VestaCP developers create a method for Blesta to communicate with VestaCP, or vice versa.
 
VestaCP's website says they already work with WHMCS... though I don't have a WHMCS instance to test this claim. But I would suggest that this might be a good idea to have in place early.
 
Right now though, I'm working on figuring out how to integrate VestaCP with the Universal Module, but it would be amazing to have a VestaCP module directly from the Blesta devs.
 
Sidenote: You guys are amazing. Seriously, amazing.

Very interested here.

Hi, Blesta Devs!
 
It would be awesome if you guys could help the VestaCP developers create a method for Blesta to communicate with VestaCP, or vice versa.
 
VestaCP's website says they already work with WHMCS... though I don't have a WHMCS instance to test this claim. But I would suggest that this might be a good idea to have in place early.
 
Right now though, I'm working on figuring out how to integrate VestaCP with the Universal Module, but it would be amazing to have a VestaCP module directly from the Blesta devs.
 
Sidenote: You guys are amazing. Seriously, amazing.

It's a lot of work to make it part of the core software, I wouldn't say the time and effort would be worth releasing it free, which is why I suggested it should be a paid plugin like the licensing system.

Man, that is some beautiful work going on here, I'm seeing.
 
My gods, what a difference. Literally, what a difference. I'm seeing active support here on the module and genuine effort in making sure the importer/migrator works.
 
WHMCS does not do this publicly, whereas you guys do. Hell, you'd be very lucky to even get any support publicly. Such a world of difference. If I wasn't set on Blesta by this point, I am now. (but I already am, so no worries, there.)
 
Fortunately for me, I don't have to worry about importing from WHMCS... but still.

Not sure if they have API docs. I suspect they do, also, apologies on the late response.
 
 
Yup, Russian. Though they're working on translating it into English and other languages. Good to know that you found the WHMCS one... I should've found that, myself. Obviously though, I didn't think about it. Heh.
 
Edit: Looking at the module in question, it's in English... and that is a very good thing. Also unencoded!
 
I imagine you could do a Blesta one, based on this...
 
Edit2:
 
Chrome auto-translated for me:
 
In the panel, it has a full API, but unfortunately, the documentation on how to use it is not ready yet. I'll try to briefly describe the key points, but if something is not clear, ask. in the folder / usr / local / vesta / bin scripts are located, which are both functions of the API. If you need to create a user, you need a script v-add-user, if you want to delete the database, it will make the script v-delete-database, and so on, by analogy. In other words, if you do ls / usr / local / vesta / bin, then you can get an idea of the options available. If you run the script without any parameters, it issues a statement on the use of:
 
[Root @ V-test ~] # V-Add-User Error: not enought arguments Usage: V-Add-User USER PASSWORD EMAIL [PACKAGE] [FNAME] [LNAME]  
Each script returns return_code. If return_code is 0, then the operation completed successfully. Any other number will indicate an error. Actual table return codes can always be found in the file / usr / local / vesta / func / main.sh
 
OK=0 E_ARGS=1 E_INVALID=2 E_NOTEXIST=3 E_EXISTS=4 E_SUSPENDED=5 E_UNSUSPENDED=6 E_INUSE=7 E_LIMIT=8 E_PASSWORD=9 E_FORBIDEN=10 E_DISABLED=11 E_PARSING=12 E_DISK=13 E_LA=14 E_FTP=15 E_SSH=16 E_DB=17 E_RRD=18 E_UPDATE=19 E_RESTART=20 UNIX API inspired ideas and therefore all information is stored in plain text files. Each script solves only one task. Upon successful completion of the script, for nothing is displayed. If an error occurs, the script immediately exits and displays a message on the screen. Returning to the creation of user and check the return code.
 
[Root @ V-test ~] # V-Add-User Error: not enought arguments Usage: V-Add-User USER PASSWORD EMAIL [PACKAGE] [FNAME] [LNAME] [root @ V-test ~] # echo $? 1 From Table 1 above it E_ARGS, which means that an insufficient number of arguments. Optional parameters are enclosed in brackets kvadtratnye. To successfully create a user need only 3 azadt argument - user name, password, and email address. If the package is not specified, will be replaced by the default package, which is called the default.
 
[Root @ V-test ~] # V-Add-User Demo d3mo0p4ssw0rd demo@vestacp.com [root @ V-test ~] # echo $? 0 In addition to the categories of scripts for creating and changing, there is a category for display, such sripta fall into the pattern v-list-*. Scripts can display information in several formats. Currently, these 3 formats: shell, plain and json. The first two are convenient to work from the command line.
 
[Root @ V-test ~] # V-list-users Shell USER PACKAGE U_DISK U_BANDWIDTH SUSPENDED DATE ----------------------------- ------------------------- admin Default no 2013-02-11 3 0 1 0 Default test no 2013-03-10 Demo Default 0 0 no 2013-03-18 The third format is used for the operation of the web interface, which work uses the same API. For the operation of the web-based interface to the system is installed an additional web server nginx and php-fpm, to handle php. All requests made ​​under the user interface admin, which is allowed to serve api via sudo. now specifically try to answer your question about the creation of users. There are 2 options: 1) You can ipolzovat api directly executing scripts in / usr / local / vesta / bin, as it makes the web interface 2) You can use the wrapper-om the web interface to access the api. In most cases, the second option would be relevant. Further about it. By the way, just recently been implemented billing system integration WHMSC its wrapper-a. In the module for whmcs implemented key features that interest you and probably. The module is able to: * Create Customer service area * delete users * change the user's password * add web / mail / dns domain to wrapper-u need to handle POST requests, passing the user name and password admin. Here are a few examples of the most vsotrebovannyh:
 
# Create user Add a user to a domain Delete user domains including its https://server-ip/api/?&user=admin&password=currentpwd&cmd=v-delete-user&arg1=demo  
And reproduced for you here, in English for the most part.

It's all Russian lol but I think this is their WHM** one: click here.
 
But it's confusing: http://forum.vestacp.com/viewtopic.php?f=18&t=3657&sid=24c6c2cffec9fea8e34d283d2692747e#p5758 you'll need to use chrome or a good translator lol.

I haven't heard of VestaCP before, interestingly it's name is very similar to Blesta.
 
Just looking at their screenshots, while pretty basic it looks like an excellent open source Panel. Certainly if it works well. Do they have API docs?