Shared and Business Hosting Services
By Staff
By Staff
Article and details on our Shared and Business Hosting services
What does Entry Process mean?
An "Entry Process" is how many PHP scripts you have running at a single time. Our standard shared hosting for example has a limit of 30 PHP scripts executions at a single time. Every time a request to a PHP script on the websites in your hosting account is made, a new program is started to execute this PHP code. This process then executes your code, sends the response to the visitor, and finally quits. Is it the limit of the visitors on my website per second? Usually, an "Entry Process" only takes around a second to finish, therefore most people get it confused with how many visitors they can have on their website at a given time. A 30 limit Entry Process for example doesn't mean only 30 people can be on your website at once because the likelihood of all 30 people hitting your website at the exact same second is less likely to happen (provided your website is a small or mid-sized blog/store/portal etc). When a visitor browses any web page of your website, the web server starts serving that request. While this request is being served, it will use one entry process. Once this request has been served, the web server will quit the entry process and the entry process count would get decreased by 1. Please note that cron jobs, shell scripts, MySQL requests, and other commands also use entry process for the duration of the time they are running. On average, an entry limit of up to 30 usually handle 50-60 visitors on your website at once. If you have a generally low traffic website but you see constant hits of the Entry Processes limit, this indicates something wrong with your scripts being hanging around longer than they should. How do I reduce my entry process usage? - Make sure static files (like pure HTML files) don't have the .php file extension, because all requests to files with the .php extension generate entry processes, even if there is no actual PHP code in the file. - Reduce usage of AJAX and other background requests. If your website has code that constantly refreshes the page in the background (to check for changes or new messages), this can easily cause high entry process usage with few visitors. - Implement cache mechanisms whenever possible. Why we have this limit on shared hosting? We have created entry process limitations to ensure that no single user consumes all server resources and to prevent DDoS attacks against the web server. Entry process will limit the number of concurrent connections to web server, thus preventing our server against malicious traffic.
About PHPMail on Shared and Business Hosting
The PHPMail() functionality is disabled by default on all new accounts. PHP scripts or applications relay email from the server directly when using the PHPMail() function, which does not make use of our MailChannels features. On the other hand, while using SMTP to send email, this ensures that your messages are relayed through our premium delivery solution, MailChannels without additional cost. It also increases the chances of your mail reaching the recipient's inbox, reducing the risk of messages being rejected or delivered in spam on the basis of the RBL listings / IP blacklists. You have the choice, between enabling the option to use PHPMail() and missing a lot on MailChannels email relaying features, or otherwise configuring your PHP scripts to use SMTP (recommended). a. Using SMTP to Relay Emails: This is of course the recommended approach, while it takes a little extra step, it ensures your mail reaches the recipient, reducing the risk of the messages being rejected on the basis of the RBL listings / IP blacklists. Important Note: this approach assumes that your domain is using our default name servers for Shared hosting plans: https://dash.wevrlabs.net/knowledgebase/4786/ - First, go to your cPanel, and create an email account (learn more on how to create a new email account on cPanel via this link here: Create New Email Account on cPanel) ... Make it something like [email protected] ... We will you this as an example here, but you can also use any email address which you have previously created in cPanel. - Setup SMTP on your application. We will be taking WordPress as an example here, using a plugin called WP Mail SMTP and configure this plugin to use the "Other SMTP" option. - the SMTP host would be something like mail.yourdomain.com ... and you will replace the yourdomain.com part with your actual domain name. - for Encryption, use TLS - for SMTP Port, use `587``` - Fill out the rest of the info and click save. - the SMTP Username is the email address you created earlier, and the SMTP Password is the password of that email. b. Enabling PHPMail Function: This option is not recommended, because for example, if you have contact forms on your website, they're subject to bots and contact forms scraping programs that scan the internet 24/7 for contact forms to send bulk spam messages, effectively harming the reputation of the IP address of the server hosting the website, if those messages were sent directly from it (which is the case with the PHPmail() function). As stated before, if the messages were relayed via a premium spam filtering service like MailChannels, first these bulk spam messages would be filtered out before even making their way to destinations, and secondly, even if some of them found their way to destination email addresses, the originating IP address would be from MailChannels IP pools, effectively reducing the risk of blacklisting hosting server IP. However, if you'd still want to use the PHPmail() function, keep in mind that if abuse was detected from your account (which is very common on outdated and compromised WP sites), we will sadly be forced to disable the function permanently on your account. To enable PHP function, go to your cPanel account (learn more on how to access cPanel via this link: How to Login to cPanel). Next, go PHP Select Version section ... and once there, open the Options tab: Follow the steps in the picture below to enable mail sending via PHPmail() ... Just choose the option /usr/sbin/sendmail -t -i from the dropdown and you are all set.
How to View Nameservers and Other Service Information
Sometimes you may need to view name servers for linking your domain with your shared or business hosting plan, such as when you order a domain from another provider and wish to link it with a shared or business hosting plan you ordered from us. It is always advised to first look at the specific information of the service before using the name servers above, that's because sometimes, the name servers for a specific shared or business hosting plan may be unique to that service, this info and other related information is displayed in the service details page. To view information of a specific service, visit your dashboard homepage at https://dash.wevrlabs.net/clientarea.php then locate the service for which you want to view the details, and click on it. Service information: Here you can view your cPanel username and direct login link as well as other information such as the IP of the server where your hosting is present, and its hostname. You can also view the nameservers that you should use to link your domain with the hosting.
Email Sending Limits
All outbound emails are sent through a premium relay service, included free of charge with every account. This ensures that all messages are delivered, irrespective of any potential 'blacklist' issues with the IP addresses on your hosting account. Our hourly sending limits vary by plan and have been outlined below. Shared Hosting Plans 150 (Per Domain/day) Elite Pro 150 (Per Domain/day) Elite Business 250 (Per Domain/day) Elite Enterprise 350 (Per Domain/day) Please Note: - These limits are subject to change/modification anytime without notice. - there is an 'overage' buffer of 25%, which will queue messages above the set hourly thresholds. - The email facilities in shared and business hosting plans are not suitable for marketing campaigns. Instead, it is recommended that you use a dedicated Email Marketing solution for this purpose, such as SendGrid or MailChimp.