We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Search found 33 matches
- Tue Jun 09, 2015 3:42 pm
- Forum: General Discussion
- Topic: New release for 2015 ?
- Replies: 176
- Views: 140173
Re: New release for 2015 ?
any update? Monday has passed
- Tue Jun 09, 2015 3:42 pm
- Forum: General Discussion
- Topic: New release for 2015 ?
- Replies: 176
- Views: 140173
Re: New release for 2015 ?
any update?
- Mon Jun 08, 2015 5:15 pm
- Forum: General Discussion
- Topic: New release for 2015 ?
- Replies: 176
- Views: 140173
Re: New release for 2015 ?
it's moday. kindly update whether installer is ready or not?
- Sat Jun 06, 2015 12:15 pm
- Forum: General Discussion
- Topic: New release for 2015 ?
- Replies: 176
- Views: 140173
Re: New release for 2015 ?
Thx much. Looking forwardimperio wrote:Mondayarmyboylegend wrote:when will nginx only and php-fpm installer be ready?
- Sat Jun 06, 2015 3:27 am
- Forum: General Discussion
- Topic: New release for 2015 ?
- Replies: 176
- Views: 140173
Re: New release for 2015 ?
when will nginx only and php-fpm installer be ready?
- Wed Jun 03, 2015 8:38 am
- Forum: Web Server
- Topic: Apache Upstream Error
- Replies: 2
- Views: 3004
Re: Apache Upstream Error
Try different Boxbilling module - https://forum.vestacp.com/viewtopic.php?f=18&t=8474 Author on this forum and there is support for module. Other modules have no actual support (I think). Its not the module issue.. i am already using latest module V2.. error clearly says there upstream server issue...
- Tue Jun 02, 2015 4:05 pm
- Forum: Web Server
- Topic: Apache Upstream Error
- Replies: 2
- Views: 3004
Apache Upstream Error
I found this error in apache/domain logs while integrating with vetsa with boxbilling.. had same error while integrating WHMCS.. m using Ubuntu 12.04 32-bit. 2015/06/01 17:57:56 [error] 5384#0: *1 upstream prematurely closed connection while reading response header from upstream, client: xx.xx.xx.xx...
- Mon Jun 01, 2015 4:07 pm
- Forum: Scripting / API
- Topic: Boxbilling-VestaCP-Module-v2
- Replies: 18
- Views: 27958
Re: Boxbilling-VestaCP-Module-v2
only error i found in apache/domain logs is this 2015/06/01 17:57:56 [error] 5384#0: *1 upstream prematurely closed connection while reading response header from upstream, client: xx.xx.xx.xx, server: xxxxxxxx.com, request: "GET /manager/index.php/api/admin/order/activate?id=2 HTTP/1.1", upstream: "...
- Mon Jun 01, 2015 4:03 pm
- Forum: Scripting / API
- Topic: Boxbilling-VestaCP-Module-v2
- Replies: 18
- Views: 27958
Re: Boxbilling-VestaCP-Module-v2
thanks a lot for quick support on fix.. thanks much. vesta.php shows in server manager and configurable now.. only issue i have now is that when i activate order, it creates all things in vesacp panel through API but gives BAD GATEWAY error in the end. vesta error logs are also empty means module is...
- Mon Jun 01, 2015 2:04 am
- Forum: Scripting / API
- Topic: Boxbilling-VestaCP-Module-v2
- Replies: 18
- Views: 27958
Re: Boxbilling-VestaCP-Module-v2
yes old vesta.php works