bluesteam Posted August 8, 2025 Share Posted August 8, 2025 (edited) Hello Has anyone else experienced an issue where if you have a pending order in a client's profile or even a terminated or cancelled hosting service, and you click on Services -> My Services and then you click on a hosting package that is cancelled/terminated/pending, it throws the following SiteJet error: Quote Oops! Something went wrong and we couldn't process your request. Please go back to the previous page and try again. For additional assistance, please reference the WHMCS TroubleShooting Guide » TypeError: WHMCS\Product\Server\Adapters\SitejetServerAdapter::factory(): Argument #1 ($server) must be of type WHMCS\Product\Server, null given, called in /home/######/public_html/admin/vendor/whmcs/whmcs-foundation/lib/Service/Adapters/SitejetAdapter.php on line 0 and defined in /home/######/public_html/admin/vendor/whmcs/whmcs-foundation/lib/Product/Server/Adapters/SitejetServerAdapter.php:0 Stack trace: #0 /home/######/public_html/admin/vendor/whmcs/whmcs-foundation/lib/Service/Adapters/SitejetAdapter.php(0): WHMCS\Product\Server\Adapters\SitejetServerAdapter::factory() #1 /home/#####/public_html/admin/modules/servers/cpanel/cpanel.php(0): WHMCS\Service\Adapters\SitejetAdapter->getAvailableSitejetProductUpgrades() #2 [internal function]: cpanel_ClientArea() #3 /home/######/public_html/admin/vendor/whmcs/whmcs-foundation/lib/Module/AbstractModule.php(0): call_user_func() #4 /home/######/public_html/admin/vendor/whmcs/whmcs-foundation/lib/Module/Server.php(0): WHMCS\Module\AbstractModule->call() #5 /home/######/public_html/admin/vendor/whmcs/whmcs-foundation/lib/Service.php(0): WHMCS\Module\Server->call() #6 /home/######/public_html/admin/clientarea.php(0): WHMCS\Service->moduleCall() #7 {main} We do allow SiteJet on our cpanel servers but what's happening here is that this error throws on any hosting package that has no associated account on cpanel. If the account does exist on cpanel, the error is not thrown. I would think that if the account doesn't exist, it should not throw this error. This happens on default whmcs templates. I'm running WHMCS 8.13.1 with PHP 8.3 Edited August 8, 2025 by bluesteam More context in title 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Technical Analyst WHMCS JimmyW Posted August 10, 2025 WHMCS Technical Analyst Share Posted August 10, 2025 Hey@bluesteam, I have just attempted to replicate this scenario in my test environment, but have been unable to get the same result. I would recommend opening a support ticket, and someone can take a deep dive to see if we can get to the bottom of it with you. Regards Jimmy 1 Quote Link to comment Share on other sites More sharing options...
bluesteam Posted August 13, 2025 Author Share Posted August 13, 2025 (edited) Apologies please ignore this reply. Edited August 13, 2025 by bluesteam Response removed. made in haste. 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Product Manager WHMCS John Posted August 26, 2025 WHMCS Product Manager Share Posted August 26, 2025 Hi @bluesteam, We have logged this with the development team. The case number is WHMCS-22288. 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: https://changelog.whmcs.com/ I apologize for the inconvenience, and appreciate your patience as we work to resolve this. Thanks again for taking the time to report your findings. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.