Recently one of our clients reported the error below and it’s one of the known WHMCS Order Issues.

oops something went wrong and we couldn’t process your request

Reasons behind such error

Recent Migration or System updates can cause such issues. We had a case where the client switched his service to HostPoco. The client noticed an error after a decrease in order flow for his website. The change in the document path of the domain has caused the issue. The client’s site was using the path as /home2/user/public_html earlier and migration of service have changed the path to /home/user/public_html and you can make required changes under the storage system to fix the issue.

Here are steps to determine the exact cause of oops something went wrong

This is the simplest way to find out what’s causing it. What is causing this error? These steps are easy to follow and can be done quickly without any programming knowledge.

Step 1. Log in to the WHMCS Admin Area.

Step 2. Navigate Setup Tab, then click on General Setting Tab, then click on Another tab.

Step 3. Click on the checkboxes to reload the page that is giving you the error. You will be able to see the error.

Summary

Always make sure to tests the things after any action with the website or with WHMCS panel. Such oops something went wrong errors can harm your business and it’s required to take quick action against such errors.

The post oops something went wrong and we couldn’t process your request! appeared first on .

Today, we will discuss the possible causes and fixes for the WHMCS Connection Timed Out Issues.

When such WHMCS connection timed out issues occur?

Connection time-out error itself gives the idea that a connection request sent to a particular server was not processed within the timeout limit set by the particular device. It generally happens while accessing websites from the browser or performing a script etc.

WHMCS regular users would have seen such issues or errors. Different processes can trigger this issue in WHMCS. This varies from creating an account to adding servers.

Firewall restrictions and DNS issues can be possible reasons

RegisterDomain/EPP: Error connecting to tls://epp.xxx.xxx:700 – Connection timed out

The above commands can give an idea about the server ports which are able to listen to inbound and outbound connections. We can add the config file by editing it, in case they are not opened.

We recently received multiple support requests where the client was unable to access the domain registrar panel. It gave the error –

Firewall restriction is the common reason for the connection time-out issues. The first step in the troubleshooting part is to ensure that the port through which connection attempts occur is open and able to make the connection. Our case was for whm based client, our techs have instantly cross-checked that the CSF configuration file to confirm if port 700 is able to listen to the connection.

root#grep TCP_IN /etc/csf/csf.conf

root#grep TCP_OUT /etc/csf/csf.conf

root#nano /etc/csf/csf.conf

Make sure to add the port number to the list of open ports. Restart CSF firewall after adding and saving changes under config file.

root#csf -r (restart firewall)

If you are having Iptables, then Add the commands below will help to fix the error:

root#iptables -L //to list the rules

root#iptables -A INPUT -p tcp –dport xxxx -j ACCEPT //to open port xxx

root#service iptables save

Also, initiate a test connection to a server under whmcs or make a telnet connection to ensure that the IP address of the server is not blocked in the receiver end.

Delay In DNS propagation triggers WHMCS connection timed out issues

We received connection time-out issues in different cases while adding a server to WHMCS. The error observed was :

Curl error: [7] Failed to connect to xxxxxx.com port xxx: Connection timed out.

This scenario is a little different from regular firewall blocks. Here, xxxxxx.com was the hostname of the server. The A record entry of the hostname was still under propagation as it was added recently. Hence, there was an issue with the identification of IP address by WHMCS and found a connection. You can allow sufficient time for the propagation to get finish or can reduce the TTL value of the record.

Connection Time Out Issues After Enabling Cloudflare

This has been a regular issue noticed after enabling Cloudflare for the particular website. Missing a particular WHMCS associated subdomain or domain can cause such errors. Also, SSL redirection can play a role in it.

Further, Cloudflare allows 100 seconds with a basic plan for sessions. You will find regular time-out issues after enabling Cloudflare. You can either finish tasks within this limit or can upgrade Cloudflare to a higher plan.

Apart from this, sometimes WHMCS Store Bug or outdated WHMCS version can cause such errors.

Conclusion

Firewall restrictions or recent activities related to the domain can cause such WHMCS connection timed out issues. Cloudflare can also trigger such scenarios. We discussed different possibilities for time-out-related issues and how our techs fix them.

The post How to Fix WHMCS Connection Timed Out Issues! appeared first on .

To explain brief, client X is having web hosting site with hosting store. Interested candidate has visited to his Linux reseller hosting page and clicked on Order Now but that page got redirected to Linux Shared hosting product page. At last respective candidate failed to buy service and somehow client has lost one client and business.

Always Perform Regular Checkup’s Against WHMCS Store Bug:

I wish to get you alert about such possibilities for your valuable hosting sites. In the above case, client came to know about the issue only when one of his candidate contacted him through live chat. The respective client was not sure from when that got affected and he almost lost hundreds of dollars due to this.

Test Orders:

I am sure that most of clients are using WHMCS billing application for web hosting sites. Its easy to understand and having multiple best features which are required to make things simple to accept orders and manage clients. It is our responsibility to perform regular test orders for our products listed on our website. This is the simple and best process to check if there are any issues with our hosting cart and help to find if there is any WHMCS store bug.

I have also published some important topics like WHMCS Price Hack, Clean of Hacked Word Press Site and you can go through them for more information:

• Process To Clean Up Your Hacked WordPress Site

• Important Pricing Update For WHMCS Price Hike

• Factors behind Fasted WordPress Hosting

Steps To Fix WHMCS Store Bug:

We have fixed this issue by performing steps given as below:

– Login into Admin login of your whmcs billing panel

– Click on option named System Settings Available Settings section

– Click on Ordering Section available under General Settings

– Change/Set Default Order Form Template to > Standard Cart (Default)

This will help you to fix your issue. You can also switch your websites with hugely demanding shared/reseller hosting service of Hostpoco where you will get high resource hosting packages with managed solutions.

Summary:

Our suggestion for such cases to perform regular checkups instead of business loss due to such bugs. It take’s few seconds only but it costs much if any client reports about this. So keep yourself invested and achieve the best.

The post WHMCS Store Bug | Standard Cart Template | Redirection of any product group to product Group 1! appeared first on .