The server encountered an internal error or misconfiguration and was unable to complete your request

Internal Server Error — The server encountered an internal error or misconfiguration and was unable to complete your request

Создание и настройка своего сайта является приятным моментом для вебмастеров. Но иногда они могут сталкиваться с ошибкой «Internal Server Error – The server encountered an internal error or misconfiguration and was unable to complete your request». Что она означает и как её устранить вы узнаете, прочитав эту статью.

Причины ошибки

Данная ошибка в переводе звучит так: внутренняя ошибка сервера . Система обнаружила внутренний сбой или неверные настройки и не смогла сформировать запрос. Это значит, что какие-то настройки загруженного движка или других файлов неверна, из-за чего и происходит ошибка. Одной из распространенных причин данной проблемы сервера являются ошибки файла .htaccess . Это дополнительный файл для предоставления определенных команд для серверов, в частности Apache.

Многим вебмастерам удается исправить ошибку «Internal Server Error», исследовав внимательной этот файл. В нем может быть указан неверный домен или вовсе запрещен доступ к сайту. Файл .htaccess дает возможность: изменять настройки для всего сайта, защищать определенные каталоги паролем, создавать черные списки из URL, разрешать доступ только избранным сайтам и многое другое.

Где в панели администратора найти .htaccess

Для того, чтобы отредактировать файл, его нужно найти в вашей админ-панели. На хостинге, который имеет cPanel и в движке WordPress этот файл расположен в каталоге public_html .

  1. Выберите каталог, и найдите файл.
  2. После этого в контекстном меню выберите «Редактировать». Он может находится в скрытых файлах.
  3. Вам нужно их отобразить, найдите кнопку «Настройки» и измените пункт «Отобразить скрытые файлы».
  4. Если его вообще нет, вы можете создать его самостоятельно. Нажмите в файловом менеджере кнопку «Файл» вверху и создайте файл .htaccess.

Устранение ошибки сервера

При внимательном изучении файла .htaccess можно определить из-за чего появляется сообщение Internal Server Error. Иногда пользователям удается определить наверняка, что ошибка в файле .htaccess. Для этого нужно удалить все содержимое из него и сохранить в другой текстовый файл, чтобы не потерять. После этого нужно открыть сайт, если ошибки не возникает, значит причина в файле.

Для начала попробуем отыскать параметры файла, которые могут вызывать эту ошибку. Найдите в своем .htaccess такие строки:

Их необходимо закомментировать. Для этого в начале строки, которая содержит эти параметры нужно поставить знак решетки — #. Закомментированная строка будет выглядеть так: # php_value. Между решеткой и следующим символом необходимо ставить пробел. Для WordPress может понадобиться еще закомментировать следующие параметры: SecFilterEngine Off и SecFilterScanPOST Off.

Возможно в вашем файле нужно установить кодировку, попробуйте закомментировать следующую строку: AddDefaultCharset WINDOWS-1251. Попробуйте изменить на UTF-8. Также нужно найти (если есть) в файле строку # RewriteBase / и убрать из него символ решетки. Просмотрите ссылки в тексте .htaccess, возможно они неверны.

Другие способы устранить The server encountered an internal error

Найдите в своем файле .htaccess строку AllowOverride All. Если здесь стоит решетка (#), уберите её.

    Необходимо также проверить, что для домена существует следующая запись VirtualHost. В качестве примера можно посмотреть на скриншоте как выглядит запись;

Запись VirtualHost в файле .htaccess

  • Убедитесь, что конфигурационный файл содержит хостнейм сервера (обычно указывается в виде домена или IP-адреса);
  • Попробуйте запретить доступ всем входящий IP-адресам с целью проверить работу .htaccess — Deny from all.
  • Как создать черный список в .htaccess

    Вы можете создать свой список из IP-адресов, которые не смогут попасть на ваш сайт. Для этого нужно найти файл .htaccess и отредактировать его. Следующий код, который будет блокировать адреса нужно вводить с новой строки.

    1. Можно в начале кода поставить знак комментария #, чтобы пояснить для себя на будущее для чего он. Например, # Черный список для хамов;
    2. Первой строкой разрешаем посещение для всех адресов — allow from all;
    3. Следующий код будет блокировать указанный адрес — deny from86.164.01;
    4. Добавляем еще один IP-адрес — deny from484.015.44.

    Этот список может продолжаться бесконечно. Если вы не знаете, какой адрес у назойливых комментаторов, их можно подсмотреть в логах вашего сервера. В разных движках есть свои методы определения адресов. Это могут делать и сторонние скрипты PHP. Универсальным способ для всех движков определить IP-адрес — найти соответствующий раздел «Логи сервера». На платформе cPanel — это раздел «Посетители». Для того, чтобы избавиться от ошибки «Internal Server Error – The server encountered an internal error» можно воспользоваться онлайн-сервисами проверки конфигурационных файлов.

    Источник

    The server encountered an internal error or misconfiguration and was unable to complete your request

    I have been using Firefox for years. Suddenly today I can no longer access Pay Pal via any site (Ebay, Vitacost, etc) to make online payments through PayPal. I loaded in Google Chrome and I CAN access Pay Pal so it appears to be a Firefox issue. The ‘warn me when websites try to redirect’ in UN-checked, so this is not the issue from what I can see. There seems to be some redirect issue. I tried going directly to www.paypal.com and received the same message (see below). Firefox is preventing a redirect to PayPal. Please advise and provide detailed steps to correcting this issue. Thanks. 🙂

    This is the message I am receiving: Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, webmaster@paypal.com and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log.

    Chosen solution

    Since the error message is generated from the server, Firefox may be sending an inappropriate or corrupted cookie, or some aspect of a typical web request (such as the URL of the referring site) might be blocked.

    READ  Standard linear regression error

    To address that first one: Remove your paypal cookies — save any pending work first. While viewing a page on the site, try either:

    • right-click and choose View Page Info > Security > «View Cookies»
    • (menu bar) Tools > Page Info > Security > «View Cookies»
    • click the padlock or globe icon in the address bar > More Information > «View Cookies»

    In the dialog that opens, you can remove the site’s cookies individually.

    Then try reloading the page. Does that help?

    The second issue is trickier because you need to see what kind of request Firefox is sending. But first you might check this setting:

    (1) In a new tab, type or paste about:config in the address bar and press Enter. Click the button promising to be careful.

    (2) In the search box above the list, type or paste refer and pause while the list is filtered

    (3) If the network.http.sendRefererHeader preference is bolded and «user set» to a value other than 2, right-click > Reset the preference so that Firefox sends the Referer header in all relevant cases

    If you changed that, does it make a difference in using PayPal?

    All Replies (3)

    Chosen Solution

    Since the error message is generated from the server, Firefox may be sending an inappropriate or corrupted cookie, or some aspect of a typical web request (such as the URL of the referring site) might be blocked.

    To address that first one: Remove your paypal cookies — save any pending work first. While viewing a page on the site, try either:

    • right-click and choose View Page Info > Security > «View Cookies»
    • (menu bar) Tools > Page Info > Security > «View Cookies»
    • click the padlock or globe icon in the address bar > More Information > «View Cookies»

    In the dialog that opens, you can remove the site’s cookies individually.

    Then try reloading the page. Does that help?

    The second issue is trickier because you need to see what kind of request Firefox is sending. But first you might check this setting:

    (1) In a new tab, type or paste about:config in the address bar and press Enter. Click the button promising to be careful.

    (2) In the search box above the list, type or paste refer and pause while the list is filtered

    (3) If the network.http.sendRefererHeader preference is bolded and «user set» to a value other than 2, right-click > Reset the preference so that Firefox sends the Referer header in all relevant cases

    If you changed that, does it make a difference in using PayPal?

    If the above didn’t help then also check for issues caused by extensions.

    You can inspect and manage permissions for the domain in the currently selected tab via these steps:

    • Click the «Site Identity Button» (globe/padlock) on the location/address bar
    • Click «More Information» to open «Tools > Page Info» with the Security tab selected
    • Go to the Permissions tab (Tools > Page Info > Permissions) to check the permissions for the domain in the currently selected tab

    You can allow third-party cookies only from visited domains.

    • Tools > Options > Privacy > Firefox will: «Use custom settings for history»

    Clear the cache and remove cookies only from websites that cause problems.

    «Clear the Cache»:

    • Firefox/Tools > Options > Advanced > Network > Cached Web Content: «Clear Now»

    «Remove Cookies» from sites causing problems:

    • Firefox/Tools > Options > Privacy > «Use custom settings for history» > Cookies: «Show Cookies»

    Start Firefox in Safe Mode to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem.

    I have been using Firefox for years. Suddenly today I can no longer access Pay Pal via any site (Ebay, Vitacost, etc) to make online payments through PayPal. I loaded in Google Chrome and I CAN access Pay Pal so it appears to be a Firefox issue. The ‘warn me when websites try to redirect’ in UN-checked, so this is not the issue from what I can see. There seems to be some redirect issue. I tried going directly to www.paypal.com and received the same message (see below). Firefox is preventing a redirect to PayPal. Please advise and provide detailed steps to correcting this issue. Thanks. 🙂 This is the message I am receiving: Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, webmaster@paypal.com and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log.

    You are amazing. The issue is solved and I am grateful for your insight and direction. 🙂

    Источник

    И за чего могла возникнуть ошибка Internal Server Error?

    Internal Server Error
    The server encountered an internal error or misconfiguration and was unable to complete your request.

    Please contact the server administrator at webmaster@i8y6o20x.idua.org to inform them of the time this error occurred, and the actions you performed just before this error.

    More information about this error may be available in the server error log.

    Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

    В чем может быть проблема? может я что-то не так сделал при переносе? Подскажите, пожалуйста, как решить?

    • Вопрос задан более трёх лет назад
    • 1102 просмотра

    Простой 5 комментариев

    Ошибка 500 чаще всего возникает из-за того, что в файл .htaccess вносятся директивы, которые явно противоречат настройкам веб-сервера или их дублируют. Записи о подобных ошибках будут внесены в лог ошибок сайта (в ISPManager, например, в разделе “Журнал”). В частности, это могут быть директивы для изменения настроек php — тогда строка будет начинаться с
    php_flag
    или
    php_value

    Поскольку на хостинге php работает в режиме fastCGI, а не mod_apache, то настройки php подобным образом выполнять недопустимо — их следует вносить в файл php.ini

    А также директивы связанные с работой с симлинками: к примеру, Options +SymLinksIfOwnerMatch будет выдавать ошибку, строку следует заменить на Options +FollowSymLinks

    Эта ошибка может возникнуть и при попытке обработать слишком большой файл, — в этом случае проверьте папки вашего сайта, хранящие логи.

    Лучше всего дебажить ошибку через логи веб-сервера, рекомендую погрузится в журналы сервера и детально почитать о чем пытается сообщить веб-сервер.

    На крайний случай обратитесь в поддержку хостинга, часто провайдеры помогают перенести сайты на свою площадку, мигрируют как на shared-хостинг так и на виртуальные сервера или выделенные физические железки.

    READ  Iphone model a1688 прошивка

    Источник

    How to Fix the Internal Server Error in WordPress

    If you’ve ever encountered sporadic errors in your WordPress site, you’ve come to the right place. WordPress errors can be quite infuriating, but there’s always a way to overcome them – and in most cases, a several different solutions exist.

    Some users find that on trying to access their WordPress admin panel, they’re presented with an internal server error that goes something like this:

    The server encountered an internal error or misconfiguration and was unable to complete your request.

    This particular error has people racking their brains out to figure out what’s wrong with their site and how they can fix it. In this article, I’ll go over a few simple solutions you can try out to diagnose the error and resolve it.

    Let’s get right to it!

    How Does This Error Occur?

    As the name suggests, internal server errors aren’t WordPress-specific errors. They can occur due to a fault with other services and software running on the same server as your WordPress site. Assuming you’re hosting on a shared server, internal server error in WordPress is more common than you might think.

    The error itself and the message it displays is not specific in the very least. There’s practically no way of finding out exactly how the error came from reading the internal server error message. However, when this error occurs on a WordPress site, we can narrow down its causes to:

    1. Functions of themes.
    2. Functions of plugins.
    3. Corrupted .htaccess files.
    4. PHP memory limit reached.

    More often than not, users will be trying to access their WordPress admin area when they encounter the internal server error. In such cases, it’s common for the rest of the website to work as usual while access to the site’s admin area is restricted.

    Now let’s look at a few ways we can fix this issue.

    How to Fix the Internal Server Error

    As discussed above, there’s no real way of finding out exactly what’s wrong with your WordPress site and why it’s giving an internal server error every time you try to login to the WordPress admin area.

    It is common sense to take a method and try it. If it fails, admit it frankly and try another. But above all, try something. – Franklin D. Roosevelt

    As Mr. Roosevelt ever so delicately puts it, we’ll apply the trial and error approach step-by-step to resolve this issue. If one method doesn’t fix it, move on to the next!

    1. Ensure .htaccess File Works Properly

    The first thing we’re going to do is ensure our WordPress site’s .htaccess file isn’t corrupt and is doing what it intended. Follow these simple steps to check for your .htaccess file’s status:

    • Login to your WordPress site’s FTP client.
    • Navigate to the File Manager under the Files
    • Find your site’s .htaccess file and rename it e.g. .htaccess_original
    • Try accessing your website and the WordPress admin area.
    • If everything works fine now, navigate to Settings >Permalinks from your site’s Dashboard.
    • Click the Save button.

    By saving these settings, you’ll generate a new .htaccess file that contains the correct rewrite rules. These new rules will guarantee that your site’s post pages don’t return errors when accessed.

    If your .htaccess file was causing the internal server error, it should be fixed now. However, if you found the error was still in place on re-loading your site and WordPress admin area, then move on to the next step in which we’ll show you how to increase your site’s PHP memory limit.

    2. Increase PHP Memory Limit

    If the internal server error persists even after you’ve checked your .htaccess file, it could be because you’re hitting the memory limit. Often when this is the case, you’ll also come across an error that reads:

    The uploaded file exceeds the upload_max_filesize directive in php.ini

    when you’re trying to upload a file to your Media Library. Or perhaps it could be something more like this:

    Fatal error: Allowed memory size of 1234567 bytes exhausted (tried to allocate 87654321 bytes) in /home/your-username/public_html/wp-includes/plugin.php on line 1234

    Those who encounter this error every time you try logging into your site’s admin panel or uploading a file/image to your WordPress site can follow any of the following methods to increase the PHP memory limit. (Don’t let the codes scare you, I promise it’s not that hard!)

    Editing Your wp-config.php File

    By adding this one line of code to your WordPress site’s wp-config.php file, you can increase the memory limit to a more suitable value. In the following steps, I’ve increased it to 64M (M stands for megabytes).

    • Login to your WordPress site’s FTP client.
    • Navigate to your site’s root directory and find the wp-config.php file.
    • Inside the tag, add the following line of code:

    This simple, one-liner is my go-to method whenever I have to increase the memory limit — it works every time!

    Updating the php.ini File

    If you have trouble finding the wp-config.php file, try looking for the php.ini file instead! This method goes a bit deeper into the memory limit by allowing you to increase several different values at the same time. Let’s take a look.

    • Login to your cPanel and navigate to Files >File Manager.
    • Find the wp-admin folder and locate your php.ini file. (If the file doesn’t exist, create one by clicking on the New File button.)
    • Once you’ve found/created the file, open it and edit/add the following lines of code:
    • Save the updated file and clear your browser’s cache.

    Editing the .htaccess File

    Assuming you were unable to locate the wp-config.php file or the php.ini file you can always alter the old .htaccess file by adding a few lines of code at the bottom. This method always works for me!

    • Login to your WordPress site’s FTP client.
    • Navigate to the File Manager under the Files
    • Find your site’s .htaccess file and edit/add the following code at the end of the file:
    • Save the updated file and clear your browser’s cache.

    If you’re still not sure about getting into your site’s core files and updating them for whatever reason, you can alternatively install the Increase Max Upload Filesize plugin to get the job done.

    READ  Netsh command failed returned error code 1 openvpn

    These changes are easy to incorporate and will hopefully solve the internal server error you’re experiencing. Once you’re done increasing the PHP memory limit using any one of the three steps outlined above, try re-loading your WordPress site and accessing the admin area.

    If you’re still prompted with the error screen, get ready for the next step — things are about to get serious now.

    3. Deactivate Your Plugins

    At this stage, it’s safe to assume that you’re in for a lot of work. There’s a high chance that the error is caused by a plugin installed on your WordPress site. Even plugins with great reviews and five-star ratings can be the root cause in this scenario. Here’s how:

    • Scenario 1: The plugin isn’t compatible with your version of WordPress.
    • Scenario 2: The plugin isn’t compatible with the theme you’re running.
    • Scenario 3: The plugin isn’t compatible with another plugin you have installed.

    Plugins extend and add to the functionality of your WordPress site. They’re fun to install, they save you a ton of time and make work super easy. The only problem is that they might end up causing errors — no matter how well they score. There is no pragmatic approach or a carefully laid out formula you can follow to avoid running into an internal server error with plugins. Ironically enough, finding such an error caused by a faulty plugin or plugin-theme combination is a trial and error technique!

    To resolve this issue, you’ll have to deactivate all of the plugins you have installed on your site and then activate them repeatedly. Let’s simplify the process and give it some logical structure so it doesn’t seem as chaotic:

    Using the WordPress Dashboard

    The easiest way to deactivate all of your plugins is through your WordPress Dashboard.

    Deactivate plugins from your WordPress Dashboard.

    • Login to your WordPress site’s Dashboard.
    • Navigate to Plugins >Installed Plugins.
    • Click the Deactivate link below each plugin.

    However, if you can’t access your WordPress Dashboard, you can deactivate the plugins through an FTP client. Here’s how:

    Using the FTP Client

    Deactivating plugins using the FTP client isn’t as easy as through the Dashboard but it’s entirely possible.

    Renaming the plugins folder.

    • Login to your site’s FTP client or cPanel.
    • Navigate to the /wp-content/ folder.
    • Find the plugins folder and rename it to deactivated-plugins.

    Once you do this, all of your site’s plugins will be deactivate. This approach is much faster but requires you logging into an FTP client or the file manager provided by your hosting service.

    Once you’ve deactivated all of the plugins using either of the above-mentioned methods, it’s time to go back to your WordPress Dashboard and activate them again.

    • Login to your WordPress site’s Dashboard.
    • Navigate to Plugins >Installed Plugins.
    • Starting from the top, click the Activate link below the first plugin.
    • Reload your site and admin area to ensure it still works.
      • If your site and admin area work i.e. they don’t give an internal server error, continue to activate the next plugin.
      • If your site or admin area crashes, you’ll know that the last activated plugin is causing the internal server error.

    Once you find the faulty plugin, deactivate it again and report it to the plugin’s author, if possible, along with a list of plugins you have installed, the theme you’re currently running and your WordPress site’s version.

    Note: It’s important that you re-activate all of your plugins one by one even after you’ve found the faulty plugin. It’s possible that more than one plugin caused the error due to incompatibility issues.

    3. Contact Your Hosting Provider

    Here you are seemingly all out of options to fix the dreadful internal server error on your WordPress site. What do you do when you can’t do something about it yourself?

    If you recall, we started out by explaining what an internal server error is and stated that it occurs on the server level. The best thing to do at this stage is contact your hosting provider and report the issue to them. Your hosting providers have access to the server error logs on which your WordPress site is hosted. They can go through the logs, identify when and how the issue occurred and hopefully do something about it.

    There are a few things you should definitely mention in your email to the hosting provider:

    • Your website’s URL.
    • When you first came across the internal server error.
    • What you were trying to access when you came across the error e.g. the website, the admin area, etc.
    • The list of plugins you have installed on your site.
    • The theme you’re currently running.
    • The version of your WordPress site.
    • How you’ve tried to rectify the problem yourself.

    Between the information you give and whatever they find in the server error logs, you can rest assured that your site will be up and running without any errors in no time.

    In the worst case, if they are unable to solve the problem, they’ll, at least, be able to offer you advice and suggest appropriate measures you can take to resolve the issue altogether.

    Wrapping It Up

    There you have it — three simple, sequential techniques you can adopt to solve the internal server error on your WordPress site. The internal server error is quite common in WordPress sites, especially if your site is hosted on a shared platform.

    We provided three quick solutions to fix the error and depending upon the root cause, one of them should work for you. Hopefully, you’re in a better place to take things further and try out the techniques explained in this article.

    Have you ever encountered the internal server error? How did you fix it? Did any of the techniques we detailed above help you resolve the issue? Let us know in the comments section below!

    Similar error you might cafe in WordPress is “error establishing a database connection” you can read more about this error on how ti fix it here.

    Источник

    Smartadm.ru