Jump to content

Jason

Members
  • Posts

    35
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by Jason

  1. I am a web designer and I host many of my client's website.

    I am using Namesilo as registrar and Blesta domain manager for the domains.

    I set a renewal date in Blesta, that may or may not align with the actual renewal date in Namesilo. These are longer term clients, so I set the domains to auto-renew in Namesilo so we don't lose the domain if a client forgets to pay.

    This has worked fine for years. However, recently (I assume after my latest upgrade of Blesta), it no longer sends out invoice for the domains.

     

    As an example ...

     I have a domain "sampledomain.com." The namesilo renewal date is 11/1/2023. The renewal date in Blesta is 11/15/23. It will send out upcoming renewal notices, etc, just fine. But after 11/1/23, once it is has renewed at Namesilo,  it won't send out an invoice to the client, because it sees the domain is no longer expiring. How do I get Blesta to still send an invoice each year, even if the domain is already renewed in Namesilo?

    I want blesta to bill based on the renewal date I set, regardless of what the actual renewal date is. And I want Namesilo to renew regardless of whether or not the person pays in Blesta. This has worked for years, why has it stopped working??

    Thanks,
    --Jason

  2. I can't figure out what is going on. I have multiple servers and manage them via the cPanel module. Adding a new service works perfectly on all of them except one. And on this one server it connects and adds the account, but instead of showing a "success" notice and the blesta admin page, it delivers a 404 error.

    Services can be removed and managed fine on this server via the blesta admin. So it has a good connection and can edit the server accounts, but if I add a new service, on this specific server, it will pump out a 404 error even though it still adds the new cpanel account to the server.

    It is almost like it sends the command to the server to create the account and is waiting to hear back, but doesn't. So it stalls out and dies to a 404 page.  For any of the other servers it works fine, the error is limited to one server.

    Any suggestions?

    --Jason
     

    P.S. Tried upgrading to new version of Blesta and that didn't fix the issue.

  3. I think I may have found the issue. My hosting provider, in trying to diagnose another problem in Blesta, had turned on debugging. I turned it off and did a test run and I think it is working correctly now.
    Not sure why turning on debugging would stop the payment process from working, but I think that was the issue.

    Appreciate your help!!

  4. 25 minutes ago, Paul said:

    Are you using Stripe or Stripe Payments and did you switch/migrate from Stripe to Stripe Payments? What version of Blesta did you upgrade from? Are the errors occurring with only new or only existing payment accounts, or both? What version of PHP are you running and did you change it, or change anything else on the server recently?

    Thanks.

    I am using Stripe Payments (not a migration from the previous Stripe version).

    Version of Blesta is 5.2.2, I believe I upgraded from 5.1.x.

    Errors occur with existing accounts. It may happen with new accounts too, but it is happening on accounts that have paid via stripe in the past.

    I am unaware of any changes with the PHP 7.4 settings (although it is possible that something was adjusted - e.g. I am on a managed VPS).
    --Jason

  5. Customers are getting an error message when paying through Stripe. I only started having this issue after upgrading to Blesta 5.2.2. Not sure that has anything to do with it, but I did upgrade recently.

    The error log says, ""array_key_exists(): Using array_key_exists() on objects is deprecated. Use isset() or property_exists() instead";}"

    Anyone else having this issue?

     

  6. On 1/27/2022 at 7:22 PM, Paul said:

    The API response is logged to the module log under Tools > Logs > Module tab. Click the row for the API call to expand it and see the raw input/output from the API call. Usually the output will provide more information.

    If there is some kind of PHP error, it would be logged to the file logs under ../logs_blesta (Path defined under Settings > System > General) so you may want to check this also. Only errors written during the registration attempt would be relevant.

    This is super helpful! Thanks for the info.

  7. Just in case anyone ever runs into this type of issue and is looking for a solution. The problem ended up being an issue on Namesilo's side which they have fixed.

    We were able to figure out the issue by determining that:
    1. The domains at the old registrar could indeed be transferred by manually transferring one of them into Namesilo. Thus eliminating the issue of the old registrar not releasing the domain.
    2. We sent a properly formatted API call via SSH to Namesilo bypassing Blesta. We grabbed the error code/issue from the Namesilo API response.
    3. The response was basically saying we had already started the transfer when we had not. So we contacted Namesilo's support and they were able to fix the issue on their end.

    Thanks to @knownhost for their help on the server side narrowing down what the error code actually meant (FYI, having the actual error code/description listed in the Blesta admin side would have saved a lot of time with diagnosing this issue) and thanks to @namesilo for their help fixing the API issue.


     

  8. 5 hours ago, Paul said:

    What version of Blesta are you running? Namesilo requires that you have a payment ID and a verified payment method to register/renew/transfer domains over the API. That is the most common reason it does not work as expected. It is possible to manually renew/transfer/register domains with Namesilo through their interface without a verified payment ID, but not over their API.

    I was using 5.1 but I upgraded to 5.2 today to try and see if that would fix it, but unfortunately I am still getting the same error.
    Is there a log file that will tell me "why" it isn't registering the domain name? For example, what the response from the API is?

    Or can I capture what it is sending to the API to try and diagnose what the error is? NameSilo offered to look at the API call, but I don't know what Blesta is sending them, so they can't diagnose it on their end.


     

  9. All of a sudden, I can no longer transfer in a domain name in Blesta.

    I add the domain transfer info like normal and now it is giving me the message, "This domain cannot be transferred at this time."

    I can transfer a domain directly from Namesilo. Once a domain is registered, I can add it in Blesta as long as I don't select "use Module" when adding it. Once the domain is added, I can interact with Namesilo inside of Blesta to adjust the WHOIS, etc. I just simply can't register it. In other words, the API is connecting fine to adjust domains, but I am unable to transfer/register them.

    There is no hint why it won't register and it is happening on more than one domain name. Is there a way to track down a reason "Why" a domain can't be transferred? I have been using the NameSilo module since before there was a domain manager, so this issue is new and I have no idea why it is happening.

    Any help would be greatly appreciated,

    Thanks,
    Jason

  10. I am using the Domain Manager and NameSilo. Is there a way to set the domain name renewal date in Blesta to bill it at the same time as a hosting package, but have it renew the domain name with NameSilo even if the domain name doesn't technically renew till a later date?
    Thanks,
    --Jason

  11. I was using the Namesilo domain plugin and just upgraded to the newest version of Blesta with domain manager.

    When I go to add a new service to a user it is displaying three .org, .com and .net options. I can't find any way to remove the "extra" packages. In the Domain packages section it only shows the three main TLDs.

    How do I eliminate the extras/duplicates?

    Screenshot attached so you can see what I am talking about.

    screenshot.jpg

    screenshot-2.jpg

  12. Just in case anyone down the road runs into the same issue ...

    I never really found a solution to this issue. I did get NameSilo working by not including a payment ID and instead have it default to using account funds deposited with NameSilo. I think there must be a bug either in the module or the API that isn't parsing or sending/matching the payment account ID correctly, but at least it allows me to put in orders now.
     

  13. OK. Glad I am not the only one that is struggling to find a solution to this.

    For now it looks like I will have to set up free domains manually using an internal coupon. Kind of defeats the point of an automated billing system, but at least I can set the domain name cost to $0 so that it doesn't bill the client. It just means I will have to manually onboard bundled accounts (which in my situation isn't too terrible since I am working one-on-one with most of my clients anyways).

    Looking forward to seeing this option become available in Blesta.

  14. Has anyone figured out a way to offer a free domain name with a hosting package? I am not sure why this is such a complicated thing to implement. I would love to bundle a domain registration with the hosting purchase, but this seems completely impossible with Blesta since it looks at those as completely different and unassociated products. Please tell me there is a workaround for this ...
    FYI, I am using NameSilo for registrations.

    --Jason

  15. I have the NameSilo Module configured in Blesta, but when I place an order I get an error that says, "The provided credit card profile either does not exist, or is not associated with your account."
    I added a second payment account, and verified it. Swapped out Payment ID's in the module and still get the error.

    Anyone else ever run into this? What was the solution?

    Thanks,
    --Jason

  16. When I install the NameSilo module, I get stuck where the "pricing" doesn't display the selected tld extensions. I need to be able to price the various extensions differently, but on my system it is only showing the standard pricing chart. It does have the additional "renewal price" field, so I know it is pulling in the module pricing chart, but it doesn't appear to show the tld pricing option.

    For reference: https://docs.blesta.com/display/user/Namesilo

    Thanks,
    --Jason

  17. I upgraded blesta this week from 4.x to 5.x, but it appears something is off with the layout. I am attaching a screenshot. I have tried switching themes, I even re-uploaded the entire "App" folder, but it still isn't showing up correctly. Any suggestions?
    --Jason

    *** UPDATE ***
    The issue was a custom template. I didn't realize there was a "template" and a "theme" that needed selected.
    All is good now :-).

    Thanks!

  18. On 2/25/2021 at 11:42 AM, Haris said:

    Hi, sorry for this newbie questions. For the card payment using stripe, if the user did not tick the save card details during the first purchase, will blesta can automatically Autodebit from the user's card on service renewal?

    Because my understanding, if no save card info, deduction only happen for that one time purchase session. And when renewal is due, system can't autodebit, just send renewal invoice asking for payment only...

     

    Did you ever find the answer to this? I was wondering the same thing ...
    --Jason

  19. Wanted to follow up with the solution I used.

    Thanks so much for pointing me in the right direction @Jono!  I moved a variation of my the code to the CreateInvoices.php page (core/Automation/Tasks/Task/CreateInvoices.php) and that has worked perfectly (so far).

    In case anyone else was curious what I did ... I added an if statement after "private function process() {" that blocked the creation of the invoices on weekends. The invoice for the service is still created, but pushed until a later day. It didn't alter the service renewal dates, it simply altered when the invoice was created/sent.

    No guarantee it will work for anyone else, or that it won't have unintended consequences, but it seems to work perfectly for what I needed.
    Thanks again @Jono and @Paul for the help!

      private function process()
        {
    		
    		//  Don't process renewal invoices if it is Saturday, Sunday or Christmas 
    		if ((date('N') >= 6) || (strtotime(date('Y-12-25')) == strtotime(date('Y-m-d'))) ) { $output = ""; } else {
    			
    
                // Create invoices for renewing services
                $this->createRenewingServiceInvoices();
    
                // Create recurring invoices
                $this->createRecurringInvoices();
    
    		}
    }

     

  20. 2 hours ago, Jono said:

    That private method no longer exists in the current version of Blesta.  Cron tasks have been moved to their own classes.  See core/Automation/Tasks/Task/CreateInvoices.php  Specifically see the run() and isTimeToRun() and createRenewingServiceInvoices() methods

    Thanks! I will check that out and see if I can figure out a solution.
    I really appreciate the help! Will post back here if I am able to get it working.
    --Jason

  21. I am trying to keep it from generating the invoices and sending out emails on the weekend, but then complete those tasks on Monday.
    I don't remember what version of Blesta is was, but it worked for several versions. I may have had to move where the line of code was located, but I was able to successful utilize the code through a couple of different releases/version. I believe the workaround was in place somewhere from around 2016 till 2018 or 2019 before it stopped working.

    I grabbed some of the code from a backup file I have from a previous version where I had used the code...

    	private function createRenewingServiceInvoices() {
    		
    if (date('N') >= 6) { $output = ""; } else {
    	
    		$this->uses(array("ClientGroups", "Coupons", "Invoices", "Services", "PackageOptions"));

    and of course I closed the if statement lower on down after the function was finished. It isn't pretty but it worked as expected.

    I also extended it to include Christmas as a day not to send invoices.

    $month = date('n');
    $day = date('j');
    if ((date('N') >= 6) || (strtotime(date('Y-12-25')) == strtotime(date('Y-m-d'))) ) { $output = ""; } else {

    The idea was to simply have it skip creating the invoice on those days, the following day it would see the invoices had not been created and voila it would create it as it was supposed to.

    As for why ... I observe Sunday as a day of rest for religious reasons, and didn't want the billing system sending out bills to my clients on that day. I am also primarily a web designer, so while I do host websites, having them only billed Monday through Friday lowers the amount of potential questions and emails on the weekend :-).

  22. I am looking for a way to limit invoices to sending during weekdays. In older versions of Blesta I added a line or two of php to cron.php to check if the day of the week was Saturday or Sunday and if it was to simply skip creating the invoice.

    if ((date('N') >= 6) .....

    Since I upgraded a while back my code no longer works. I added it where I thought it should be, but it hasn't kept the system from sending invoices. So I am either adding it in the wrong spot, or Blesta no longer uses the cron.php file to determine if an invoice is sent. Any ideas how I could accomplish this?

    Thanks,
    --Jason

  23. On 8/11/2016 at 10:24 AM, Licensecart said:

    I provided you this tag:

    
    {transaction.amount | currency_format transaction.currency}

    Which converts it from $24.0000 to $24.00

    Thanks Licensecart and Paul. I didn't realize the extra part of the tag was actually formatting info. I used the tag as you listed it and the email sends out the correct decimal points now. I appreciate your help and your patience!!!!!

×
×
  • Create New...