Illegal scheme supplied, only alphanumeric characters are permitted in Magento 1.8

Illegal scheme supplied, only alphanumeric characters are permitted in Magento 1.8

August 17, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Illegal scheme supplied, only alphanumeric characters are permitted in Magento 1.8

Solving “Illegal scheme supplied” Error in Magento 1.8

Introduction

Magento is a powerful e-commerce platform that allows you to create complex online stores with ease. However, even the most robust systems can encounter issues from time to time. One common problem faced by Magento users is the “Illegal scheme supplied, only alphanumeric characters are permitted” error.

In this article, we’ll guide you through identifying and resolving this issue in your Magento 1.8 installation.

Understanding the Error

The error occurs when Magento attempts to validate the base URL provided in the core_config_data table against a regular expression that only allows alphanumeric characters (letters A-Z, numbers 0-9, and the underscore character). If the URL contains any other special characters or spaces, it will fail this validation.

Locating the Issue

The error log provides valuable insights into where the issue is originating:

#0 /home/innobmme/public_html/ayurvedachary.com/app/code/local/BTS/1610Fix/Model/Store.php(30): Zend_Uri::factory('localhost/ayurv...')
#1 /home/innobmme/public_html/ayurvedachary.com/app/code/core/Mage/Core/Controller/Varien/Front.php(313): BTS_1610Fix_Model_Store->isCurrentlySecure()
#2 /home/innobmme/public_html/ayurvedachary.com/app/code/core/Mage/Core/Controller/Varien/Front.php(161): Mage_Core_Controller_Varien_Front->_checkBaseUrl(Object(Mage_Core_Request_Http))
#3 /home/innobmme/public_html/ayurvedachary.com/app/code/core/Mage/Core/Model/App.php(354): Mage_Core_Controller_Varien_Front->dispatch()

The core issue appears to be in the Store model of a third-party extension (BTS 1610Fix). This suggests that the extension might be attempting to validate the URL against its own rules, leading to a conflict with Magento’s built-in validation.

Resolving the Issue

Step 1: Verify the Base URL

The first step is to ensure that your base URL in core_config_data is indeed correct and matches what you expect. To do this:

  • Log into your MySQL database using a client like phpMyAdmin.
  • Navigate to the core_config_data table.
  • Find the record where path = "web/unsecure/base_url" or web/secure/base_url.
  • Double-check that the value matches your actual URL structure. It should look something like this: https://www.example.com.

Step 2: Temporarily Disable the Extension

Since the error seems to be related to a third-party extension, let’s disable it temporarily:

  1. Log into your Magento admin panel.
  2. Navigate to “System” -> “Configuration”.
  3. Click on “Advanced”.
  4. Under “Advanced”, click on “Disable Modules Output”.
  5. Find “BTS 1610Fix” in the list of modules and check the box next to it.
  6. Save your changes.

Step 3: Clear Magento Cache

Sometimes, the issue can be resolved simply by clearing the cache:

  • In your admin panel, go to “System” -> “Cache Management”.
  • Click on “Flush Magento Cache”.
  • Verify that all cache types are enabled and click “Save Cache”.

Step 4: Update or Contact the Extension Developer

If disabling the extension doesn’t resolve the issue, it’s likely a bug in the extension itself. You can try reaching out to the developer for support or check if there is an updated version of the extension that fixes this problem.

Conclusion

The “Illegal scheme supplied” error in Magento 1.8 typically occurs due to a misconfiguration with the base URL or a conflict with a third-party extension. By following these steps, you should be able to identify and resolve the issue quickly.

Remember to always ensure your Magento installation is kept up-to-date for optimal performance and security. For more advanced troubleshooting techniques and best practices in e-commerce development, consider exploring our Magento Development Services at Laravel Company.

Magento 1 Database Configuration Errors

Our network