SiteJet fatal error on unprocessed/terminated/cancelled orders

[bluesteam]

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 by bluesteam
More context in title

[WHMCS JimmyW]

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

[bluesteam]

Apologies please ignore this reply.

Edited yesterday at 05:56 AM by bluesteam
Response removed. made in haste.