Filezilla will not connect to server using Secure File Transfer Protocol (SFTP)

Filezilla will not connect to server using Secure File Transfer Protocol (SFTP)

Symptom(s):

Filezilla is unable to connect to the server using the Secure File Transfer Protocol (SFTP), however regular file transfer protocol (FTP) works fine. Additionally, you have confirmed that the required ports for the Secure File Transfer Protocol have been enabled on the firewall. The generic port for SFTP is port 22 and the port for FTP is 21, port 20 may be required if the server is running the ftp services in passive mode.

Solution(s): 

  1. SSH into the server and edit the /etc/ssh/sshd_config file, if your config is in another location you can use the “locate sshd_config” to identify that location.
  2. Once in the file find the following commented out line: #Subsystem sftp /usr/lib/openssh/sftp-server Leave the line commented out, if its not commented, go ahead and comment it out using a hash tag (#).
  3. Below the commented out line add: Subsystem sftp internal-sftp  then reboot the server.
  4. Your Filezilla should now be able to connect.

Sending’ reported error (0x80040119): ‘The message cannot be saved to you IMAP e-mail account Sent Items folder, because Outlook is offline or the e-mail server doesn’t allow items to be saved to the Sent Items folder’

 

Symptom: Outlook reports the following error – Sending’ reported error (0x80040119): ‘The message cannont be saved to you IMAP e-mail account Sent Items forlder, because Outlook is offline or the e-mail server doesn’t allow items to be saved to the Sent Items folder’

Solution:

  • Go to File-> Account Settings-> Account settings-> (YOUR EMAIL ACCOUNT) -> Change…-> More Options…-> Advanced
  • Set Root folder path to “Inbox” and force a Send/Receive

This fix should allow you to now automatically sync with Squirrelmail, Round Cube, or Horde.

 

SpamAssassin not Filtering certain domains

Problem: Spamassassin is not properly filtering domains such as link, click, xyz, science, and similar.

Solution: Your Registrar Boundaries file is out of date.

In Ubuntu, go to /usr/share/perl5/Mail/SpamAssassin/Util/

Use: wget svn.apache.org/repos/asf/spamassassin/trunk/lib/Mail/SpamAssassin/Util/RegistrarBoundaries.pm  (It will probably download as RegistrarBoundaries.pm.1)

cp RegistrarBoundaries.pm to RegistrarBoundaries.pm.old

cp RegistrarBoundaries.pm.1 to RegistrarBoundaries.pm

sudo service spamassassin restart

Enjoy!

 

phpBB upgrade gets stuck during the database upgrade process when upgrading from 3.0.* to 3.1.*

phpBB upgrade gets stuck during the database upgrade process when upgrading from 3.0.* to 3.1.*

Symptom(s):

The phpBB automatic upgrade appears to get stuck during the database upgrade process when upgrading from version 3.0.* to 3.1.* and never proceeds on refresh.  No error is given since the issue is occurring within the configured folder and file permissions assigned to the Apache Web Server.  The error can actually be located in the Apache Server error log file.

Solution(s):

  • If you check the Apache logs, which are typically located in the /var/log/httpd or /var/log/apache2 directories, its actually a directory permissions / owner issue.
  • When files are uploaded by a user account the control panel assigns user permissions instead of Apache permissions.  The script needs to run as Apache since it is running locally on the web server itself and not as the user whose permissions it was assigned.

Solution #1:  If you have root access:  Change the owner of Cache and Store folders located under your phpBB installation to www-data:www-data (Or psacln if plesk) using the chown command from the shell prompt, (i.e. chown www-data:www-data /Your-php-install/cache), then refresh the upgrade screen to complete the upgrade.

Solution #2: If you do NOT have root access: Temporarily set the folders of Cache and Store to 0777, continue the upgrade and then restore permissions to 0755. This can be done by using the chmod command from the shell prompt, (i.e. chmod -R 0777 /your-php-install/cache),  then refresh the upgrade screen to complete the upgrade.  Once completed make sure you run the command again using chmod -R 0755 /your-php-install/cache and store folders respectively.  The -R denotes “recursive”, which means all the permissions are changed for all files and folders recursively under the cache directory.

Note: In all Apache installs where files will be accessible to the internet, the best settings for permissions are to set 0644 for all files within the directory and to set permission 0755 for all directories that will be accessed externally or on the Internet.  0644 basically means that www-data or Apache can read and write to the file and everyone else including the Internet can only read the file and nothing else.   0755 means that www-data or Apache can read, write, and execute the file, but everyone else including the Internet can read and execute the file, which is required for directories to work properly.

Magento – Forbidden 403

Symptoms: When you attempt to browse to your Magento installation or Magento directory you receive a 403 Forbidden Error.

Solution: This is a normal web server response when the requesting user does not have the rights to access the content it is trying to access. To resolve this issue check the following information:

1. Check the owner of the folder for /httpdocs/ and all subdirectories for the magento installation. The correct owner should be as follows:  username:usergroup

In a Plesk 11.5 hosted environment this would be:  yourusername:psaserv

If the user is root (which often happens with command line installation) change the owner of the files in httpdocs or the subfolder with the magento installation using SSH and type:  chown -R yourusername:psaserv httpdocs/*

JFolder::create: Infinite loop detected

SYMPTOMS: You are trying to install a plugin or component using the extension manager in Joomla 1.5 or higher and receive JFolder::create: Infinite loop detected

SOLUTION: Your TMP directory is not set correctly. In many server configurations open_basedir is set to a specific folder in your php.ini settings. Try changing the tmp directory path from /var/www/yoursite/httpdocs/tmp to just /tmp in the Joomla global configuration.

RSA server certificate CommonName (CN) `plesk’ does NOT match server name!?

Problem: RSA server certificate CommonName (CN) `plesk’ does NOT match server name!?

Solution: The RSA certificate is being referenced back to the server’s control panel, as such, the domain name doesn’t match the server name. Please note this message is harmless and can be ignored.

STEP 1:

1. Under your Plesk Control Panel, go to Websites & Domains > Secure Your Sites > Add SSL Certificate

2. Name your certificate

3. Make sure the domain name matches your site, remove www.

4. Click Self-Signed, your SSL Certificate has now been generated. Please note, this is a self-signed unsecure certificate, do not use this for PCII.

STEP 2:

1. Under your Plesk Control Panel, go to Websites & Domains, Click on Show Advanced Operations on the bottom of the screen.

2. Select Website Scripting and Security

3. Under Security, make sure Enable SSL Support is checked, in the pull down select the certificate you just created.

4. Click OK.

This should resolve the error message 🙂


Options FollowSymLinks or SymLinksIfOwnerMatch is off which implies that RewriteRule directive is forbidden

Symptoms:Options FollowSymLinks or SymLinksIfOwnerMatch is off which implies that RewriteRule directive is forbidden

Either the .htaccess file is missing the followsymlinks option or another .htaccess is overriding the options.

NOTE: There are TWO Solutions to this problem, I recommend trying Solution #2 first.

Solution #1:

Add: 

Options FollowSymLinks

Above:
RewriteEngine On
RewriteBase /

(Note: you must have “AllowOverride Options” in effect to permit the use of the “Options” directive in .htaccess files.)

If you are trying to access a pearl type file in a cgi-bin or other directory that does not require the rewrite rule, add an .htaccess file with RewriteEngine off.  This will prevent the above error from occurring.

It is best to add this solution to the httpd.conf file if you have access, the how-to on that file can be found here:

http://httpd.apache.org/docs/current/howto/htaccess.html

 Solution #2:

Modify the dir.conf in apache.

Step 1: From root SSH: vi /etc/apache2/mods-enabled/dir.conf

Step 2 Change:

DirectoryIndex at_domains_index.html index.html index.cgi index.pl index.php index.xhtml index.htm index.shtml index.cfm

to:

DirectoryIndex at_domains_index.html index.html index.cgi index.php index.pl index.xhtml index.htm index.shtml index.cfm

A Simple change in order fixes the symlinks issue.

Special Thanks to XAMeLeOH for posting this for the community.


Connection reset by peer: mod_fcgid: error reading data from FastCGI server

Symptoms: The following errors are found in the web server error logs:

Connection reset by peer: mod_fcgid: error reading data from FastCGI server

Premature end of script headers: index.php

Solutions:  This is one of those frustrating errors that can take a long time to fix and may be dependent on multiple problems.  The solution that worked in my case was adding:

ini_set(‘zend.enable_gc’, 0); <<Below the <?php tag in the index.php

Why does this work?  There are known conflicts between zend and APC, if both are installed you may receive the above error, adding the above code into your php file should resolve your issue.

Other possible solutions:  Modify your php.ini to increase max_execution_time, post_max_size, and max_input_time :: IMPORTANT – Make sure you maintain a limit, no limit could result in massive resource usage.