Troubleshooting Common Problems

Debugging technical issues on-line can be tricky. There are many moving pieces; it can be an isolated network connection with the ISP, an issue with your server.

If your AbanteCart stopped functioning do not panic. AbanteCart application is running on the server operating system and many small things that can cause issues for all your web applications.

 Follow this steps and identify problem you might have and quick resolution. Go though this list and understand what is happening.

Note

Majority of unexpected issues are happening due to hosting/server related issues/changes or code modifications.

Mod_security is an apache module that helps to protect your website from various attacks. mod_security has certain rules for the words "pattern" used in requested URL's. If any pattern match with the requested URL under your site mod_security false positive and deny the access to it. Many people are experiencing problems because of this. Problems include "406 Not Acceptable error", 403", "500", "501 Method Not Implemented" or access denied errors (forbidden access), login problems, and similar.

 Ask your hosting support to disable individual mod_security rules or try to disable it manually.
We strongly recommend you contact your hosting provider and work with them to resolve the server module issue.
Try adding this in a .htaccess file

<IfModule mod_security.c>
SecFilterInheritance Off
</IfModule>
  • A

    Find link to admin

    The correct ink to admin is based on what is set during installation process of the AbanteCart.
    yourdomainname.com/index.php?s=[your_admin]
     [your_admin] is provided during installation and can be located in system/config.php AFTER installation.
  • B

    Login fail may be caused if server is unable to create a session

    Please contact with your hosting support or modify session path on shared hosting by creating/editing a php.ini file
    Include this in your file: session.save_path = "/tmp"
    or session.save_path = /tmp/php_sessions;
  • С

    Login may fail in your browser only

    Try to login in other browsers. Follow this guide to fix browser related issues

Note

If you lost your password try to reset it. In case your cannot restore your email try this tip

Most of the time, a 503 error occurs because the server is too busy or because there's maintenance being performed on it.

 Contact your hosting provider and work with them to resolve the server issue.
PHP accelerators can substantially increase websites speed but apparently caching plugins sometimes causes problems with shopping carts.

 Contact your hosting provider and work with them to resolve the server issue.
If you're making changes to the static content cached with CDN on your site, including changes to JavaScript, CSS or images, it can be very easy to forget that you need to purge CDN cache. The content delivery network “CDN” (Cloudflare, MaxCDN) will deliver cached images and other bits of your website to your visitors from one of the several data-centers located around the world instead of from your web-server. Some minifications and asynchronous loading added by CDN can break your web-pages.

 To resolve issues purge all CDN cache in the CDN admin panel and try to set caching level to cache static content only: images and css. Make sure you have disabled javascript and css Auto Minify.
If you can not login or products are not stored in the shopping cart or get errors in the log like 'session_start failed', 'Failed to write session data', 'save_path is not writable', 'Invalid token session. Please login again'. Session_save_path is a PHP variable that is set in php.ini, and on many shared hosting setups it’s actually set to a location that’s not writable.

 Contact your host to solve this.
This issue and issues like App Error: AbanteCart core v.1.2 Resize image errorrelated to limited memory set on your server or host. The standard PHP memory requirements for AbanteCart are a bare minimum. Try to increase the memory to 128M or more.

  If you have access to the server's php.ini please edit the memory_limit parameter.
php.ini file

memory_limit = 128M  ;
        
If there is no section already for this, place the above line at the end of the file.
In case PHP is running as an Apache module you may try to edit .htaccess file
.htaccess file

php_value memory_limit 64M
        
This will not be possible in some shared hosting environments, though your host may be able to adjust it for you.
Error means that the server has run out of disk space, so AbanteCart can't save files.

 Clean your log-files, old backups or contact your host to solve this.
Your email provider has SPF policy (Sender Policy Framework) verifying the FROM address and other mail parameters. With SPF policy, you cannot put anything you want in the FROM field, it needs to match your account address or at least your email domain.

 Contact your host to solve this.
This warnings appear in your admin messages when AbanteCart's System Check is Enabled. To disable it go to the Admin > System > Settings > System.
Each file and directory on your server is assigned access rights for the owner of the file, the members of a group of related users, and everybody else. Rights can be assigned to read a file, to write a file, and to execute a file (i.e., run the file as a program). This is important because AbanteCart may need access to write to files to enable certain functions or disable access to write for the public users (world).

Note

If you installed AbanteCart yourself, you likely DO need to modify file permissions. Some files and directories should be "hardened" with stricter permissions, specifically, the /system/config.php and /index.php files. This file should be set with 644 or 640 permissions (444, or 400 depending on your server setup).
See video how to check and change permissions AbanteCart system check

To change permissions use your hosting cPanel file-manager or an FTP Client. FTP programs ("clients") allow you to set permissions for files and directories on your remote host. This function is often called chmod (chmod is a unix command that means "change mode" on a file.) or set permissions in the program menu. Right-click 'file' and select 'File Permissions'

Permissions will be different from host to host, so this only general principles.

  7       5     5
 user   group  world
 r+w+x  r+x    r+x
 4+2+1  4+0+1  4+0+1  = 755
        

Value Meaning

777

(rwxrwxrwx) No restrictions on permissions. Anybody may do anything. Generally not a desirable setting.

755

(rwxr-xr-x) The file's owner may read, write, and execute the file. All others may read and execute the file. This setting is common for programs that are used by all users.

700

(rwx------) The file's owner may read, write, and execute the file. Nobody else has any rights. This setting is useful for programs that only the owner may use and must be kept private from others.

666

(rw-rw-rw-) All users may read and write the file.

644

(rw-r--r--) The owner may read and write a file, while all others may only read the file. A common setting for data files that everybody may read, but only the owner may change.

600

(rw-------) The owner may read and write a file. All others have no rights. A common setting for data files that the owner wants to keep private.

Typically, all files should be owned by your user (FTP) account on your web server, and should be writable by that account. Any file that needs write access from AbanteCart should be owned or group-owned by the user account used by the AbanteCart (which may be different than the server account). For example, you may have a user account that lets you FTP files back and forth to your server, but your server itself may run using a separate user, in a separate user-group, such as Apache or nobody. If AbanteCart is running as the FTP account, that account needs to have write access, i.e., be the owner of the files, or belong to a group that has write access. In the latter case, that would mean permissions are set more permissively than default (for example, 775 rather than 755 for folders, and 664 instead of 644).

 Use FTP client to change permissions or contact your host to solve this.

This warnings appear in your admin messages when AbanteCart's System Check is Enabled in Admin > System > Settings > System.
Each file and directory on your server is assigned access rights for the owner of the file, the members of a group of related users, and everybody else. Rights can be assigned to read a file, to write a file, and to execute a file (i.e., run the file as a program). This is important because AbanteCart may need access to write to files to enable certain functions or disable access to write for the public users (world).

Note

/system/cache/ directory should be set with 777 permissions.

To change permissions use your hosting cPanel file-manager or an FTP Client. FTP programs ("clients") allow you to set permissions for files and directories on your remote host. This function is often called chmod (chmod is a UNIX command that means "change mode" on a file.) or set permissions in the program menu. Right-click 'file' and select 'File Permissions'

 Use FTP client to change permissions or contact your host to solve this.
First of all please check your enabled payment methods settings in Admin > Extensions > Payments:
  • Total Order Minimum/Maximum - values should be empty to allow any order amount to checkout with your Payment
  • Payment Location setting - please set it to 'All Locations', in case you need to limit Payment checkout for some location - make sure your customer address is within selected Location.
  • Check all your Shipping methods installed because every shipping methods has 'Allowed payments' settings - if you limit your shipping methods to work on only with selected payments this can be reason why your payment method not shown at checkout.
  • And the last one - please check your AbanteCart error log (Admin > System > Logs) for the payment related errors.
 Check your settings.
If you have Fatal error: Call to undefined function mb_internal_encoding() or similar this mean mbstring module is not installed on you server. If it was installed, it would be displayed on your phpinfo page Admin > System > Settings > System >  PHP Info

 You must explicitly enable the module on server configuration or contact your host to solve this.