Jump to content


WHMCS Technical Analyst
  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About WHMCS Dan

Recent Profile Visitors

702 profile views
  1. This will be set based on the order value, can you provide further details on why you need to change this?
  2. If you're looking to create your own module for this, you can then use hooks to trigger sending a SMS upon different actions occurring: https://developers.whmcs.com/hooks/hook-index/
  3. Can you clarify which init variable you mean - Do you mean the stripe public key?
  4. This is not recommended, we recommend the cronjob be set to execute every 5 minutes. This ensures the cron can handle tasks throughout the day and will then process the daily tasks at the time set under Automation Settings. We have further details on this in our docs here: https://docs.whmcs.com/Crons
  5. This would be a great Feature Request, you can raise this here so we can gather community votes and feedback: https://requests.whmcs.com
  6. This appears to be a cPanel error which can arise when trying to create an account with a domain which already exists on your server / DNS Cluster. You would need to remove the existing account/domain before you can add a new account with this domain.
  7. This can occur if the product is set to auto terminate, have you enabled this option perhaps? https://docs.whmcs.com/Products_and_Services#:~:text=Auto Terminate%2FFixed Term — You,number of cycles before stopping. If you're still stuck, don't hesitate to raise a support ticket and one of the team can help get to the bottom of this for you. 🙂
  8. Hello, This can occur for a few reasons, not just a sessions issue - if you enable Display Errors under Setup > General Settings > Other, then open up the Developer Tools window and go to the network tab. Search for something in the intellisearch and you should see an AJAX request in the network list, if you click it and view the response this should show a more detailed error to help debug further. If you need any help debugging this, please feel free to raise a support ticket, including your WHMCS & cPanel login details and one of our team can take a look and help get this working.
  9. After further researching some of the inconsistencies described in this thread, I was able to reproduce that when searching for some extensions such as .co.uk this appears to be logged in the WHOIS Log despite being supported by the NameSpinner service. I have now raised case #CORE-14854 with our developers in order to have this inconsistency reviewed for future releases. Whilst I cannot provide an estimated time for completion for this, once we resolve cases and push features they are available at our change log, here: http://changelog.whmcs.com/
  10. Thanks for raising the inconsistency with our docs page, I've gone ahead and amended our docs to make clear it is WHOIS Lookups which are logged, not domain lookups to help avoid confusion in future. I can also see we don't seem to have an explanation of the WHOIS fallback checking when using WHMCS NameSpinning or a registrar lookup provider, so I've raised a case internally to get this documented and I'll explain how this works briefly here. When you select WHMCS Namespinning or a registrar lookup provider, often these will not support all TLDs and so we fallback to using WHOIS lookups to check if the domain is available. Because this is a WHOIS lookup, this is then logged, but the domains which are checked via WHMCS Namespinning or a registrar lookup provider are not logged as this uses a different method to check the availability. This fallback functionality is actually the result of another feature request: https://requests.whmcs.com/topic/lookup-provider-fallback-to-classic-whois-lookup I have discussed this with my manager to confirm, but as adding logging for non-WHOIS lookup providers would be new functionality a Feature Request is the best way to get this raised so we can track interest and consider putting this on the development schedule.
  11. I can certainly understand why you'd want to see a log of domain searches, this can be useful data to understand your clients. The best thing to do here would be to raise a Feature Request for this here: https://requests.whmcs.com we can then gather community support for such a feature and look at implementing this in a future release.
  12. It sounds like your clients may not be selecting the "Use custom nameservers (enter below)" option when entering their nameservers. If the radio option is set to "Use default nameservers", even if the client enters custom nameservers in the fields then your default nameservers would be applied instead of the custom ones they entered.
  13. The WHOIS log only shows WHOIS checks performed, as noted by @brian! other lookup providers such as registrars or WHMCS Namespinner use alternative methods to check domain availability so the checks will not be logged in the WHOIS Log.
  14. I can see there was an issue related to this which was resolved in WHMCS 7.10+, are you using the latest version of WHMCS when seeing this error?
  15. Have you checked and verified the other steps mentioned in our guide are in order? https://help.whmcs.com/m/troubleshooting/l/802231-troubleshooting-a-redirect-loop If these are all set correctly, please feel free to drop us a support ticket and we can investigate further.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated