Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 12/08/2015 in all areas

  1. smicroz

    Nginx And Blesta

    Hi, Finally I can be solved adding in directadmin cp, in custom hosts if (!-e $request_filename){ rewrite ^(.*)$ /index.php; } #Core rewrite location @blesta { rewrite ^(.*)$/index.php/(.*) /$1 permanent; } Thanks!!
    2 points
  2. Michael

    Fraud Record

    Fraud Record, for Blesta would be amazing in my opinion, it checks a database for unwanted customers, it's a bit like a neighbourhood watch team, but for webhosting. Any fraud gets submitted to the database, and you can check to ensure you don't get the same unwanted customers. Stop Fraud Clients, Report Abusive Customers. Combine your efforts to fight misbehaving clients. I used to use it on the last billing system I used and it helped much better than Maxmind, because bad clients are bad clients. http://www.fraudrecord.com/ API: http://www.fraudrecord.com/developers.php
    1 point
  3. DO NOT Ask for an Audit on any of CubeData's modules/plugins as sorry but if you are just one person asking for a audit sorry but we do not do audits unless a majority of our customers request that. This module for blesta is like our whmcs addon for the same purpose FraudRecord A Great addition to your arsenal of fraud prevention tools that ties directly into fraudrecord's api and blesta's fraud system. also stops vpn/proxies as well This module or fraud protection module ties directly into blesta and is added as a fraud module in blesta's antifraud folder like so /pathtoyourblesta/plugins/order/components/antifraud/fraudrecord this module allows you to leverage the ability and large db of bad clients in fraudrecord's db(database) to automatically screen orders and stop them and mark them for manual review stopping the order in their tracks if they are listed in the fraudrecord db. (due to the way blesta works it wasn't possible to mark them automatically as fraud like it is in whmcs sorry about that inconvenience.) and also it is configurable in the module to allow you to select the "max fraudrecord report score" to accept for example I could set it to 5 which is fraudrecord's report score scale from 1-10 and 5 being the best balance between 1-10. and it also uses getipintel.net's api to allow the module to screen for proxy's/vpn's/bad ip's/etc and also stop the order from being provisioned and marked for manual review. As this module for blesta the same for whmcs makes it automated to check the results from fraudrecord and stop them if listed and if they have points above the max point score you specified in the module settings. forget having to manually lookup someone in fraudrecord as this module bridges that gap by automatically looking them up and screening them for you(though cannot mark them as fraud automatically as explained above only can mark them for manual review as explained above.) Can be ordered at https://cubedata.net/order/main/index/cart for $3/month/domain Trial License is available at the same link for 14-15 days after 14-15 days or on 14-15 days the license will automatically terminate. Extended Trial Licenses can be also given for people who need extended time to see if it fits their needs(but must be reasonable though as there is no way I would issue 1 year trial licences so just putting that out there incase anyone comes up with a idea like that.) V1.2 has been released and now includes using blesta's licensing system instead of whmcs's it took a while like two days or more to figure it out but I am happy to say it uses blesta's licensing manager now and I use blesta as well now instead of whmcs for two reasons the owned license was cheaper then whmcs and also I already had existing clients info in my blesta install so it seemed like a no-brainer. v1.4.3 has been released including fraud screening on each & every order(required a core edit but it works) Legacy(Blesta v3) Screenshots: V4 Screenshots: Blesta v4 Screenshots: Coming Soon!
    1 point
  4. Tyson

    Problem After Upgrade To 3.6.1

    Do have support tickets in your system? If so, then there should be records in the `support_replies` table. If they are missing, they were somehow inadvertently deleted. In this case, it would be best to restore the table from a backup, if you have one. If you do have a record resulting from this query: SELECT * FROM `email_groups` WHERE `action` = 'SupportManager.staff_ticket_assigned'; ..then your SupportManager was successfully upgraded to add the new email templates. For whatever reason, then, the only thing that appears to be missing is the contact_id field for the `support_replies` table. You can try to resolve that issue manually by running this query: ALTER TABLE `support_replies` ADD `contact_id` INT(10) UNSIGNED NULL DEFAULT NULL AFTER `staff_id`; After you do that, try to see if you encounter an error when you view support tickets in Blesta.
    1 point
  5. smicroz

    About Language

    Definitions Translated: 249 of 8296 (3%)
    1 point
  6. Tyson

    The Form Token Is Invalid

    I forgot to mention you can have the gateway return the client (success/failure page) to the return URL given to you in the buildProcess method. i.e. $this->ifSet($options['return_url']); I'm a little surprised the email is not included. We should probably add that. However, you can query for it yourself: public function buildProcess(array $contact_info, ...) { Loader::loadModels($this, array('Contacts')); $contact = $this->Contacts->get($contact_info['id']); $email = $contact->email; ... }
    1 point
  7. If you say you're using XAMP then you already have MySQL bundled and should use 'localhost' for your database connection. That would definitely speed things up. Blesta runs pretty well on a Raspberry Pi so it's not likely your machine slowing things down. But if you do run your database from localhost and you still experience slowness, then there's definitely something going on with your server. Like maybe you're infected with a trojan mining bitcoins or sending out spam.
    1 point
  8. Your license is valid for whatever term you ordered it for (monthly/yearly/etc.), so no, it will not be terminated. The only potential issue is if you reinstall Blesta in a different location (different domain, subdomain, or directory), then you will likely need to re-issue the license so that it will then be tied to your new install location. You can login to your account with us and re-issue the license yourself at any time by clicking "Manage" next to your license in the Services table. Then check the "Reissue" checkbox and save. When you try to login to your Blesta installation it will validate the new license location and you can login.
    1 point
  9. Canceling a service is a detrimental unrecoverable action. Perhaps in the future when additional functionality is added to allow for (partially) uncanceling a service this can be revisited. The Auto Cancel plugin, however, will perform the action you're looking to accomplish. Ideally, the core should be an extensible framework which supports integrating additional features via plugin. Simply adding everything to the core is the approach we want to avoid. From our experience, most customers that have a suspended service for several days end up coming back to reactivate it, and canceling it instead can be much more of an inconvenience for them than keeping it suspended. A VPS service, for example, could be removed and all content deleted on cancelation, and its data may not be recoverable if the customer needs it afterward.
    1 point
  10. I setup imap ssl 993 and works well.
    1 point
  11. timnboys

    Fraud Record

    okay I have finally finished it michael dance it is available here: https://my.cubedata.net/cart.php I will make a topic in the marketplace forums announcing it.
    1 point
  12. Michael

    Nginx And Blesta

    I recommend you follow: http://www.blesta.com/forums/index.php?/topic/2769-blesta-nginx-the-easy-way-tutorial/
    1 point
  13. When you have a blesta setup with relatively high client volume, you may want to periodically check if everything is OK, or clean up things that should not be there (i.e: data that is not automatically removed by blesta/plugins). I've come up to this queries which I use periodically: - Show users that have at least 1 active service and more than 3 unpaid invoices: This may happen when a provision plugin is not suspending a service, or just human mistake (useful to find customers that are not paying because of not having their services suspended) SELECT many_invoices_customers.id 'customer_id', services.id_value 'service_id' from (SELECT i.client_id 'id', count(*) 'c' FROM invoices i, clients c WHERE c.id = i.client_id AND i.status != 'void' and i.paid != i.total GROUP BY i.client_id HAVING c > 3) many_invoices_customers, services WHERE services.client_id = many_invoices_customers.id AND services.status = 'active'; - Show users that have more than 3 unpaid invoices and at least 1 suspended service: let's you clean up users that don't pay anymore (and manually cancel them) SELECT many_invoices_customers.id 'customer_id', services.id_value 'service_id', many_invoices_customers.c 'invoices_number' from (SELECT i.client_id 'id', count(*) 'c' FROM invoices i, clients c WHERE c.id = i.client_id AND i.status != 'void' and i.paid != i.total GROUP BY i.client_id HAVING c > 3) many_invoices_customers, services WHERE services.client_id = many_invoices_customers.id AND services.status = 'suspended' ORDER BY many_invoices_customers.c DESC; I haven't implemented auto service cancel yet, but maybe is useful to someone here *Those queries are meant to be executed directly into your blesta MySQL DB.
    1 point
  14. You can move services via the services table search the client ID (ID in the url) and then change the client ID on the service ID you wish to move.
    1 point
×
×
  • Create New...