I will fix your Joomla website issue

Hey there, I am ready to do it for you, Please buy my gig from fiverr
 
Click Here or On Banner

 

I will migrate your joomla website from old version to joomla 3

Hey there, I am ready to do it for you, Please buy my custom gig from fiverr

Click Here or On Banner

How to CHMOD all files to 644 and all Directories to 755 via SSH

Often we find ourselves needing to bulk change all file permissions or all directory permission for an entire site or directory.
To do this with your individual ftp client is time consuming and some of the ftp software clients try to recursively change everything to the same file permission, including directories. Yes, I am talking to you WinSCP.
To separate these out you just need to log into your server or hosting account via SSH, navigate to the directory you want to start the change in and type:

find . -type d -print0 | xargs -0 chmod 0755 # For directories
or
find . -type f -print0 | xargs -0 chmod 0644 # For files

This will recursively find and apply the CHMOD accordingly for the file types. F = Files & D = Directories respectively.
If you need to change ownership of files, it is just as easy to do.
From the directory you want to start the command from you type:

chown -R username:usergroup *

This will recursively change file and directory ownership for all files and directories starting where you typed this command.
If you merely want to change ownership on a directory – you specify that as:

chown -R username:usergroup directory

or

chown -R username:usergroup directory/sub-directory/yet-another-sub-directory

That’s it – it is easy. If you need to hire some help for this – just contact us today.

How to open Exim port 26 on cPanel via SSH

It's no secret that ISP’s will sometimes limit traffic on the common SMTP ports (25 & 587). The result is that clients will constantly contact you because they are unable to send mail. The fix is normally to switch to the alternate port i.e. from port 25 to 587 and vice-versa. This however is only a temporary fix and the client will soon contact you (slightly more frustrated) again with the same problem.
Luckily, cPanel makes it easy to add additional ports for Exim to listen on. By opening for example port 26 on the server and asking your client to use that port instead, your "outgoing mail issue" calls will soon be a thing of the past.
In WHM, it is as simple as logging in, navigating to Service Manager and enabling the “Exim Mail Server (on another port)” option. But what if you have multiple servers? If that is the case, it is easier to do this via the command line (SSH) since you can create a script  to open the port throughout your entire cPanel cluster.
This is how you open port 26 via SSH on a cPanel server:

Step 1

Edit your exim.conf file

vi /etc/exim.conf

Find the following line. Note that the port numbers may not be in this order.

daemon_smtp_ports = 587 : 25 : 465

Now add port 26 as follows

daemon_smtp_ports = 587 : 25 : 465 : 26

Once changed, save and exit the file.

Step 2

Before you can rebuild the exim config, you need to add this entry to exim.conf.local as well, otherwise cPanel will simply override this entry when you rebuild the config.

vi /etc/exim.conf.local

Add the line to the file under the @CONFIG@ section

daemon_smtp_ports = 587 : 25 : 465 : 26

Save and exit the file

Step 3

Rebuild exim config and restart the exim service

/usr/local/cpanel/scripts/buildeximconf
service exim restart

Step 4

Open port 26 on your server firewall. This will mostly be CSF on cPanel servers.

vi /etc/csf/csf.conf

Find the “Allow incoming TCP ports” section and add port 26 as per the example below.

# Allow incoming TCP ports
TCP_IN = "20,21,25,26,53,80,110,143

Save the config file and restart CSF

csf –r

That’s it, Exim will now listen on port 26. To ensure that the port is open, you can telnet from another server to port 26 on the server where you opened the port as follows.

telnet server_ip 26

You should see something like this.

Trying server_ip...
Connected to server_ip.
Escape character is '^]'.
220-server_ip ESMTP Exim 4.87 #1 Mon, 06 Jun 2016 08:57:49 +0200 
220-We do not authorize the use of this system to transport unsolicited, 
220 and/or bulk e-mail.

Although the method in this tutorial will take much longer on a single server as supposed to doing it via WHM, it will be MUCH faster if you have to do it on 100 servers via a simple bash script.
Enjoy your reduced client contact!

How to Fix Permissions on Files and Directories by SSH

Sometimes plugins or other features can mess up the permissions for a file or directory(folder) on your site and make it impossible for you to access something or upload something. The easiest way to fix this is with SSH access. If you do not have SSH access, contact your host and see if they allow it and can enable it for you.

To get SSH access enabled on BlueHost, see: http://helpdesk.bluehost.com/index.php/kb/article/000180

You can use the following two lines to reset your permissions. Note that the default directory permissions are 755 and the default file permissions are 644, so that is what I will show here, however, if your webhost says you need other permissions for something, then you can change the numbers. Beware of 777 permissions though, as they are a security threat! If you are told to use 777, first try it with 755 and 644, if that doesn’t work, then carefully add 777 permissions only where you need it.

Here are the SSH commands to fix your permissions on a mass level:

find ~/public_html -type d -exec chmod 755 {} \;

find ~/public_html -type f -exec chmod 644 {} \;

Basically, the format is to find, or look, in the path of ~(which means home) and then in public_html. (If you want to look in a different directory, you can change this. e.g. ~/public_html/myblog) And then it looks for the document type, be it directory (d) or file (f), and executes the chmod(change mode) command to change the permissions on all results.

Be very careful with these commands!
If you accidentally break something, it can be difficult to fix. For example, if you have cgi or perl files, they will need 755 permissions instead of 644 in order to operate properly. If you have questions in regards to this, you might want to ask first.

Be Sociable, Share!

How should I disable the enabled xdebug in wamp server

Goto

wamp > bin > php > php5.5.12 > php.ini

wamp > bin > apache > apache2.4.9 > bin > php.ini

Find for

[xdebug]

zend_extension ="D:/wamp/bin/php/php5.4.45/zend_ext/php_xdebug-2.3.3-5.4-vc9.dll"

All you need to do is add a comment character (;) to that line like this

[xdebug]

;zend_extension ="D:/wamp/bin/php/php5.4.45/zend_ext/php_xdebug-2.3.3-5.4-vc9.dll"

That's all :)

How can I put my email with one host and website with another

Nowadays there are a ton of options when researching what an “ideal” web hosting solution should be. You might find that you’ve outgrown your current platform, or perhaps you want to go with something a bit more simplistic like dragging and dropping rather than teaching yourself HTML or CSS.
After you decided to take the plunge of switching hosting providers, you find yourself researching how to make transition as smooth as possible. You’ve accomplished updating the “A records” to the servers’ new home and breathe a sigh of relief only to realize that you’re inbox has become silent and refuses to cooperate.
Doh! “What about the email servers? Do I have to switch email over to the new hosting provider?” you ask yourself. The answer is “no.” You can manage your email the way you always have, but your new hosting provider’s DNS needs to know where to find it.
Assuming you chose to keep your email provider (server) just the way it was and not migrate your email over to your new hosting provider, then there are key steps you must take to ensure your email stays intact while the website’s domain thrives in its new habitat.
What often happens is that the Mail Exchanger (MX) record is pointing to yourdomain.com – but because you just changed yourdomain.com to point somewhere else (remember when you updated the A record so the web domain will have a new home?) @yourdomain.com is no longer working for email.
No need to panic. You don’t have to be a DNS guru to split your email from your website hosting. It’s actually quite painless, read on…
So How Can I Keep My Email Provider Separate From Web Hosting Provider?
For those of us who don’t go underneath the DNS hood every day, there are two key pieces you need to know if you want your email provider to reside separately from your website hosing provider.

1. The mail server must know about the new name server (the DNS server keeping track of the domain names and IP addresses). So we must define your “A (host) record” for mail, which we’ll explain in detail in a moment.
2. The Internet must know where the email is being  processed (this is the job of the MX record)

Let’s walk through a real world scenario:
Say you were using a hosting provider which also included email) but decided to switch to a different hosting company (e.g. Weebly*) and wanted to leave email with the current hosting company.
To accomplish this, you would just change your A records for www.yourdomain.com (and the non-www version, yourdomain.com) to the IP address of your new hosting provider (which they provide) but don’t stop there. To ensure email works the way it always has, you must ensure mail.yourdomain.com is pointing to its existing IP address AND then change the MX record to now point to mail.yourdomain.com.
In your DNS Zone Editor Section, you can make updates to your DNS records.
Screenshot shows example IP addresses (be sure to use your own IP addresses accordingly):

Will this work on Email Hosted By Godaddy, InMotion, JustHost, or HostGator?
Yes – regardless of the email provider or web hosting provider, the rules described above are the same. DNS settings containing your A records and MX records are universal (if they weren’t, then the Internet would not have grown beyond a laboratory of a few computers).
How Long Does It Take Before I Start Seeing My Email Again?
After updating the MX record and A record, propagation (the fancy word which simply means “for the rest of the Internet to catch up”) can take as little as 3 hours but as many as 48 hours. It varies, so you’re not seeing the results you expected, be sure to give it the full 48 hours.
Tip: You can check how other servers around the world are acknowledging your changes (DNS propagation) by using a free DNS checker found at http://www.whatsmydns.net/.


*If really using Weebly, keep in mind they don’t host email, and I advise against using their recommendation of the costly Google Apps that run $60/year per mailbox!