I’m really new to setting up web servers in general. I’ve got IIS 8 on Windows 8, and I’m trying to set up a little site locally, while doing some development. In IIS I choose Add Site, give a name, points to a location where I have a index.html file (I’ve tried different locations, latest in a c:inetpubwwwroottest -folder) and otherwise use all default settings. However, when I try to browse to localhost I get
HTTP Error 503. The service is unavailable.
I’ve verified the pool is started, and I’ve given IIS_IUSRS Full Control on the target folder
I’ve search around but not found anything that solved my issue, and there’s nothing helpfull in the EventLog or in the C:WindowsSystem32LogFilesHTTPERR folder
Could anyone tell me what’s wrong?
weir
4,4322 gold badges27 silver badges41 bronze badges
asked Nov 10, 2012 at 14:33
4
It could be that the user identity is outdated, especially if you’ve tried starting a stopped app pool and the next request again fails.
In IIS, go to the Application Pools under the Server, then find the correct Application Pool for your web site, and click on it. On the Advanced Settings menu to the right, select Identity and change it and enter new user and password. Click on your Application Pool again, and select Recycle to restart it.
You can also try looking at the error message in Event Viewer, under Windows Logs, Application, Details tab.
Broots Waymb
4,6553 gold badges30 silver badges51 bronze badges
answered Oct 30, 2013 at 13:02
live-lovelive-love
46.3k22 gold badges227 silver badges197 bronze badges
8
Other answers are fine. But in my case, I was working on a Windows box that already was running some old IIS, IISExpress or any other web site. What happened is urls ACLs where reserved somehow in the system. So, you might want to check this.
Here is the console command to dump all URL acls:
netsh http show urlacl
Check what’s returned here, and if anything matches the url you are testing, here is the command to delete one URL acl (for example):
netsh http delete urlacl url=http://localhost:2018/
(beware to carefully note what you do here in case it was not related to the original problem)
answered Jan 16, 2015 at 14:11
Simon MourierSimon Mourier
128k20 gold badges246 silver badges291 bronze badges
5
In my case the problem was the DefaultAppPool. I changed the «Load User Profile» to false and now it works. However, I don’t know if there are side effects to this.
Further reading on setting the Load User Profile option: What exactly happens when I set LoadUserProfile of IIS pool?
TylerH
20.5k62 gold badges75 silver badges97 bronze badges
answered Apr 18, 2014 at 16:54
2
Check your application’s respective Application Framework Pool — it could be stopped. If it is, start it and check again.
If you’re still experiencing issues you can also check out Event Viewer to find the cause of that error in order to troubleshoot more.
Robotnik
3,5452 gold badges32 silver badges48 bronze badges
answered Oct 25, 2013 at 10:20
ScoolsamScoolsam
5714 silver badges3 bronze badges
1
If the app pool is running under some specific user identity, then go to the advanced settings and update the username and password again to ensure they are correct.
TylerH
20.5k62 gold badges75 silver badges97 bronze badges
answered Aug 16, 2013 at 15:17
0
If the app pool immediately stops after you start it and your event log shows:
The worker process for application pool ‘APP_POOL_NAME’ encountered an
error ‘Cannot read configuration file ‘ trying to read configuration
data from file ‘?’, line number ‘0’. The data field contains
the error code.
… you may experiencing a bug that was apparently introduced in the Windows 10 Fall Creators Update and/or .Net Framework v4.7.1. It can be resolved via the following workaround steps, which are from this answer to the related question Cannot read configuration file ‘ trying to read configuration data from file ‘\?<EMPTY>’, line number ‘0’.
- Go to the drive your IIS is installed on, eg.
C:inetpubtempappPools- Delete the directory (or virtual directory) with the same name as your app pool.
- Recycle/Start your app pool again.
I have reported this bug to Microsoft by creating the following issue on the dotnet GitHub repo: After installing 4.7.1, IIS AppPool stops with «Cannot read configuration file».
EDIT
Microsoft responded that this is a known issue with the Windows setup process for the Fall Creators Update and was documented in KB 4050891, Web applications return HTTP Error 503 and WAS event 5189 on Windows 10 Version 1709 (Fall Creators Update). That article provides the following workaround procedure, which is similar to the one above. However, note that it will recycle all app pools regardless of whether they are affected by the issue.
- Open a Windows PowerShell window by using the Run as administrator
option.- Run the following commands:
Stop-Service -Force WASRemove-Item -Recurse -Force C:inetpubtempappPools*Start-Service W3SVC
answered Nov 27, 2017 at 15:33
weirweir
4,4322 gold badges27 silver badges41 bronze badges
1
Or if none of the current solutions work, look in your website’s directory for a file called app_offline.htm. That basically tells IIS that your site is unavailable and to show this page instead.
To fix it, either delete it or rename it to app_offline.htm.bak.
In my case, I added it while showing a colleague how to use that to prevent traffic to the site temporarily and then forgot that I did that on my box. Sigh.
answered Oct 15, 2015 at 14:50
HallmanacHallmanac
5292 gold badges8 silver badges14 bronze badges
0
Start by looking in Event Viewer, either under the System or the Application log.
In my case the problem was that no worker process could be started for the App Pool because its configuration file couldn’t be read — I had included an extra ‘.’ at the end of its name.
answered Mar 22, 2013 at 15:36
Samuel JackSamuel Jack
32.3k16 gold badges117 silver badges155 bronze badges
It is possible that your domain requires the account used for running the AppPool to have batch logon rights. In which case you will see this same error message. The way you can tell if that is the case, is by looking at the System events in the Event Viewer. There should be an event saying that the account being used with the App Pool has either ‘the wrong password or does not have batch logon rights’.
This is why developers quite often use IIS Express on their development machine, since it by passes the batch logon rights issue.
answered Jan 30, 2013 at 14:56
Hashim AkhtarHashim Akhtar
7772 gold badges10 silver badges16 bronze badges
I ran into the same issue, but it was an issue with the actual site settings in IIS.
Select Advanced Settings... for your site/application and then look at the Enabled Protocols value. For whatever reson the value was blank for my site and caused the following error:
HTTP Error 503. The service is unavailable.
The fix was to add in http and select OK. The site was then functional again.
answered Oct 17, 2013 at 20:31
atconwayatconway
20.3k28 gold badges153 silver badges226 bronze badges
2
For my case, My Default Application Pool was offline.
To troubleshoot the problem, I checked the IIS logs located in C:WindowsSystem32LogFileHTTPERR. Scroll down to the most recent error logs, this will show you problems with IIS if any.
My Error was «503 1 AppOffline DefaultPool»
Solution
- Open IIS Manager
- Click on Application Pools, this lists all application pool to your right.
- Check if the application pools hosting your api or site has a stop sign on it. If so, right click the application pool and click start.
- Try again to access your service from the client
Ryan M♦
17.3k30 gold badges60 silver badges71 bronze badges
answered Jun 22, 2018 at 14:54
mut tonymut tony
3377 silver badges9 bronze badges
Check Event Viewer — Windows — Application. If there is a red Error line made from IIS-W3SVC-WP and the message is like The Module DLL C:Windowssystem32inetsrvrewrite.dll failed to load. The data is the error. then you are missing some Windows Setup features.
In Windows Server 2012 go to Server Manager, Add Roles and Features, Web Server (IIS) and add the matching feature. Usually, most of the Application Development section is installed. Here is a complete list of IIS features and their associated DLL to help in diagnosis.
After going through a few iterations of that I ended on the error message above regarding «rewrite.dll». This led to a direct download and install of Microsoft URL Rewrite tool. Finally all websites came to life.
answered Nov 10, 2014 at 19:25
SushiGuySushiGuy
1,49317 silver badges20 bronze badges
2
Our server ran out of disk space on Sunday afternoon which led to an application suddenly failing and returning HTTP error 502. The logs were empty so it had to be something that was occurring before IIS even did anything.
A swift look at the event viewer(WIN+R > eventvwr) exposed the issue.
It’s a good idea to filter out the output of the System and Application windows to WAS since it can get pretty verbose in there.
The application depended on another one which was disabled. Therefore keep in mind an application can go down indirectly if one of it’s dependent processes has gone down. We simply re-enabled the .NET application pool and our other application started running normally again.
answered Feb 27, 2017 at 17:05
Patrick.SEPatrick.SE
4,3635 gold badges33 silver badges44 bronze badges
If you have IIS URL Rewriting installed it could be to do with that. I suffered issues after a Windows 10 Update.
This StackOverflow post helped me.
Go to Windows Control Panel > Programs and Features > IIS URL Rewrite Module 2 > Repair.
answered Apr 25, 2016 at 11:23
ᴍᴀᴛᴛ ʙᴀᴋᴇʀᴍᴀᴛᴛ ʙᴀᴋᴇʀ
2,7341 gold badge26 silver badges38 bronze badges
1
In my case, the problem was that another application was using the port that I had bound to my web site.
I found it by running the following command from a command line, which lists all of the listening ports and the executable involved:
netstat -b
answered Mar 25, 2016 at 21:23
AvalanchisAvalanchis
4,4713 gold badges37 silver badges47 bronze badges
If you have McAfee HIPS and if you see the following error in event viewer application log:
The Module DLL C:WindowsSystem32inetsrvHipIISEngineStub.dll failed to load.
The data is the error.
Then this workaround on McAfee.com resolved the issue in my case.
Quote from the page:
- Click Start, Run, type explorer and click OK.
- Navigate to: %windir%system32inetsrvconfig
- Open the file applicationHost.config as Administrator for editing in Notepad.
Edit the <globalModules> section and remove the following line:
<add name=»MfeEngine» image=»%windir%System32inetsrvHipIISEngineStub.dll» />Edit the <modules> section and remove the following line:
<add name=»MfeEngine» />- After you have finished editing the applicationHost.config file, save the file, then restart the IIS server using iisreset or by restarting the system.
Stacked
6,6246 gold badges55 silver badges73 bronze badges
answered Dec 28, 2014 at 15:01
Orhan CelikOrhan Celik
1,49315 silver badges12 bronze badges
0
Actually, in my case https://localhost was working, but http://localhost gave a HTTP 503 Internal server error. Changing the Binding of Default Web Site in IIS to use the hostname localhost instead of a blank host name.
tname for http binding
answered Aug 30, 2018 at 14:58
Tore AurstadTore Aurstad
2,94224 silver badges21 bronze badges
This could also happen if any recent installs or updates happened with .NET framework and/or ASP.NET. If you are unsure of what happened recently and if all your apps use ASP.NET version 4, you can try reset them by running the following commands in command prompt in administrator mode.
cd C:WindowsMicrosoft.NETFramework64v4.0.30319
aspnet_regiis -i
This makes sure to install or reinstall ASP.NET 4 and updates existing applications to use ASP.NET 4 version of the app pool. It updates both IIS Classic and Integrated mode handlers and script mappings in the IIS metabase. It also recreates ASP.NET v4.0 and ASP.NET v4.0 Classic app pools, and sets .NET framework 4 to DefaultAppPool and Classic .NET app pools.
answered Mar 31, 2016 at 15:59
Prabu ArumugamPrabu Arumugam
1,9192 gold badges15 silver badges19 bronze badges
I changed the port from 80 to 8080, that’s why this error occur. I write localhost/ in search bar then this error occur. My problem is resolved by writing localhost:8080/ in the search then local host open.
answered Aug 1, 2019 at 5:22
1
This happened to me on a server on our intranet. After browsing through blog posts and Windows logs, it turned out that a few days before Christmas 2015 (related to a Windows Update?) my web site application pool wanted to create a config file in folder c:inetpubtempappPools, but access to this folder was restricted. This caused the application pool to be disabled.
After adding Full control to Everyone on this temp folder, I restarted the Windows Process Activation Service and everything went online again.
If I’d been a little more elegant, it would probably had been enough to grant the AppPool user full control to the folder, but I never seem to remember how the app pool name and app pool user relates to eachother…
answered Jan 20, 2016 at 15:41
Daniel PerssonDaniel Persson
2,1511 gold badge17 silver badges24 bronze badges
Same thing with IIS Express 10.0 after upgrading Windows 7 to Windows 10.
Solution: go to IIS and enable all disabled websites and reinstall ASP.NET Core.
answered Jul 22, 2016 at 11:14
1_bug1_bug
5,3374 gold badges49 silver badges57 bronze badges
Also check the address bar and make sure the page is in the right location.
This error can be returned instead of the 404 (Page not found). In my case, it was a bad link on the page that didn’t have a subfolder included.
answered Dec 3, 2015 at 21:15
Tony L.Tony L.
16.8k8 gold badges68 silver badges65 bronze badges
I was having this problem when cleaning up my IIS on dev machine, and I had somehow created a virtual folder for a subfolder of my actual development web that I couldn’t clear and was creating conflicts.
To clear it I had to use
C:WindowsSystem32inetsrvappcmd.exe list vdir
and then individually remove the problem virtual directories using
C:WindowsSystem32inetsrvappcmd.exe delete app /app.name:"Default Web Site"/{name of virtual directory}
answered Dec 2, 2019 at 10:23
SiemsenSiemsen
1991 gold badge3 silver badges13 bronze badges
For me the solution is to change Enable 32-bit Applications to False
None of the answers worked for me. So I’d like to share what I found after hours of research..
Keep seeing this message from event logs: The Module DLL C:Windowssystem32RpcProxyRpcProxy.dll failed to load. The data is the error. Turns out that dll is 64bit and cannot be loaded into 32bit process.
answered Nov 10, 2020 at 15:44
Rohim ChouRohim Chou
7679 silver badges16 bronze badges
You can also try the following.
Right-click on the site and ‘Basic Settings…’
Click on ‘Connect As…’
Click on Specific User and give the new credentials.
Now it should work.
answered Feb 19, 2021 at 9:57
In my case, I had to change my userPass of network because company policies. So, you need to edit your AppPool:
click on Application Pools. Select your pool, ‘advanced Settings…’ go to ‘Process Model’ click on ‘Identity’ and Click on Specific User and give the new credentials.
Dharman♦
29.3k21 gold badges80 silver badges131 bronze badges
answered Apr 7, 2021 at 8:40
This might be because of number of connections to the database. I had such a situation and so, wrote a de-constructor and killed db open connection and it resolved.
answered Feb 27, 2014 at 12:34
1
Обновлено 03.07.2020
Добрый день! Уважаемые читатели и гости одного из крупнейших IT блогов России Pyatilistnik.org. В прошлый раз мы с вами научились чинить две вещи в Windows 10, это пресловутый черный экран и ошибку запуска в приложениях из-за отсутствия библиотеки vcruntime140.dll. Двигаемся дальше и сегодня решим еще один интересный пазл с веб сервисом IIS и ошибкой «HTTP Error 503. The service is unavailable«. Думаю, что мои грабли будут вам весьма интересны.
Описание ошибки 503 на IIS
Не так давно я устанавливал отказоустойчивую службу Remote Desktop Services High Availability на базе Windows Server 2019. Сами роли установились корректно и без ошибок в мастере, я успешно создал коллекцию, опубликовал RemoteApp приложения и хотел их протестировать, но какого же было мое удивление, когда я в место привычной формы авторизации увидел ошибку:
Service Unavailable: HTTP Error 503. The service is unavailable.
Причины ошибки HTTP Error 503. The service is unavailable
Сразу могу сказать, что данную проблему вы можете встретить в любом продукте компании Microsoft, где в качестве веб движка используется служба IIS (Internet Information Services). Из популярных:
- RDS фермы
- Share Point
- Exchange
- Просто сайты на IIS
Сама проблема связана в связке IIS и Net.Framework. Обычно ошибка указывает на то, что веб-страница или запрос ресурса понятен серверу, но последний не может выполнить его по той или иной причине, или же из-за банальной перегрузки, когда не хватает ресурсов.
Методы устранения ошибки 503 на IIS
Сразу скажу, что вам придется в большинстве случаев попотеть, чтобы найти причину падения вашей службы, но обо всем по порядку. Из причин можно выделить:
- Отсутствие прав у учетной записи, которая запускает пул приложений
- Вы запускаете пул в режиме 32 бита
- У вас просто не работает пул приложений
- Проблема с NET.Framework
- Проблема на уровне операционной системы из-за ошибок целостности
Переустановка системы
Как бы это смешно не звучало, но в последнем случае у меня после того, как я все перепробывал чтобы устранить ошибку 503 на IIS, уже кончились идеи и я просто снес все так как система была чистая и поставил заново, но уже более свежий дистрибутив и о чудо проблема ушла.
Не знаю, в чем было дело, то ли глюки при обновлении Windows Server 2019, то ли что-то со сборкой которая у меня была, не могу точно сказать. До переустановки у меня была версия Windows 1809 (Сборка ОС 17763.1282)
После переустановки я поставил версию от июня 2020. Когда я уже в ней запускал сайт RDweb на ферме RDS, то сервис ответил корректно и HTTP Error 503 я не увидел.
Так, что если у вас только, что установленная Windows Server 2019, то попробуйте ее снести и установить заново, это может быть куда быстрее чем заниматься траблшутингом, самое ценное это ваше время, лучше уж провести его полезнее.
Проверка работы NET.Framework
По умолчанию в Windows Server 2019 при установке добавляется NET.Framework версии 4.7. Очень часто он может быть добавлен кривовато. В случае с Remote Desktop Services мне пришлось:
- Удалить роль IIS и RDS
- Удалить компонент NET.Framework
- Скачать NET.Framework версии 4.7. Скачиваем потому, что после его удаления у вас не будет работать диспетчер серверов и установка из PowerShell.
- Установить NET.Framework версии 4.7
- Устанавливаете IIS
- Устанавливаете RDS
В результате данного шаманства в сможете запустить RDweb на вашей RDS ферме минуя ошибку «Service Unavailable: HTTP Error 503. The service is unavailable».
Но перед всеми этими рокировками я вам советую, как и в случае с зависанием пула IIS обратиться к логам и попытаться там найти, что-то что даст нам направление для поиска информации. Напоминаю посмотреть логи Windows вы можете через оснастку «Просмотр событий» или веб-сервис Windows Admin Center. Советую смотреть четыре журнала. Первые два стандартные, это «Система» и «Приложения». Например вы можете увидеть вот такое событие с предупреждением:
Код ID 1309: Event code: 3005
Event message: Возникло необработанное исключение.
Event time: 30.06.2020 18:34:41
Event time (UTC): 30.06.2020 15:34:41
Event ID: aa3cbb1255f3432d813e6c5cb75395ed
Event sequence: 14
Event occurrence: 1
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/ROOT/RDWeb/Pages-2-132380048755425068
Trust level: Full
Application Virtual Path: /RDWeb/Pages
Application Path: C:WindowsWebRDWebPages
Machine name: RDSH03
Process information:
Process ID: 3416
Process name: w3wp.exe
Account name: IIS APPPOOLRDWebAccess
Exception information:
Exception type: NullReferenceException
Exception message: Ссылка на объект не указывает на экземпляр объекта.
в Microsoft.TerminalServices.Publishing.Portal.FormAuthentication.TSFormAuthTicketInfo..ctor(HttpContext objHttpContext)
в ASP.ru_ru_default_aspx.<GetAppsAsync>d__0.MoveNext()
— Конец трассировка стека из предыдущего расположения, где возникло исключение —
в System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
в System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
в System.Web.UI.PageAsyncTaskManager.<ExecuteTasksAsync>d__3.MoveNext()
— Конец трассировка стека из предыдущего расположения, где возникло исключение —
в System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
в System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
в System.Web.UI.Page.<ProcessRequestAsync>d__554.MoveNext()
Request information:
Request URL: https://rdsh03.root.pyatilistnik.org:443/RDWeb/Pages/ru-RU/Default.aspx
Request path: /RDWeb/Pages/ru-RU/Default.aspx
User host address: 192.168.31.100
User:
Is authenticated: False
Authentication Type:
Thread account name: IIS APPPOOLRDWebAccess
Thread information:
Thread ID: 7
Thread account name: IIS APPPOOLRDWebAccess
Is impersonating: False
Stack trace: в Microsoft.TerminalServices.Publishing.Portal.FormAuthentication.TSFormAuthTicketInfo..ctor(HttpContext objHttpContext)
в ASP.ru_ru_default_aspx.<GetAppsAsync>d__0.MoveNext()
— Конец трассировка стека из предыдущего расположения, где возникло исключение —
в System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
в System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
в System.Web.UI.PageAsyncTaskManager.<ExecuteTasksAsync>d__3.MoveNext()
— Конец трассировка стека из предыдущего расположения, где возникло исключение —
в System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
в System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
в System.Web.UI.Page.<ProcessRequestAsync>d__554.MoveNext()
Custom event details:
Из которого понятно, что у меня не запущен пул. Откройте оснастку IIS и перейдите в раздел «Пулы приложений». Далее найдите нужный, в моем примере это RDWebAccess. Как видно у него статус «Остановлено», попробуйте его запустить.
Если пул не запускается, то я вам советую активировать в просмотре событий два дополнительных журнала:
- Microsoft-Windows-IIS-Configuration/Administrative
- Microsoft-Windows-IIS-Configuration/Operational
Так же что-то полезное вы можете найти в текстовом файле располагающемся по пути:
C:WindowsSystem32LogFilesHTTPERR
Как видно из файла у меня был выключен пул «2020-07-01 08:34:12 ::1%0 62570 ::1%0 443 HTTP/2 GET /RDWeb 5 503 1 Disabled RDWebAccess». У вас может быть тут другая ошибка.
Вы можете выполнить в PowerShell вот такой запрос по получению информации из данного файла, только для 503 кода.
Get-ChildItem -Path ‘C:windowssystem32LogFilesHTTPERR’ -Include *.log -Recurse | Where-Object LastWriteTime -gt (Get-Date).AddDays(-7) | Select-String -SimpleMatch ‘ 503 ‘
Отключение 32 битного режима на пуле IIS
В журнале Microsoft-Windows-IIS-W3SVC-WP вы можете увидеть ошибку с кодом события: 2282, где:
Не удалось загрузить модуль DLL из-за ошибки в конфигурации. Текущая конфигурация поддерживает только загрузку образов для x86 архитектуру процессора. Поле данных содержит номер ошибки.
По умолчанию 32-разрядная поддержка отключена в пулах приложений. Если не требуется поддержка 32-разрядных, проверьте параметры каждого из пулов приложений убедитесь, что значение Разрешить 32-разрядные приложения имеет значение False.
Откройте дополнительные параметры у нужного пула, через контекстное меню.
Еще раз проверьте что параметр Enable32bitAppOnWin64 (Разрешить 32-разрядные приложения) имеет значение «False».
Подробнее об этом вот тут — https://support.microsoft.com/ru-ru/help/2619402/error-503-service-unavailable-when-you-browse-windows-sbs-websites
Проверка учетной записи от которой запускается пул
Я очень часто встречал безалаберных системных администраторов, которым было лень создавать отдельные учетные записи для каждой службы или сервиса с которой они работают. Они делали просто, запускали все из под себя с максимальными правами или для теста так делали и забывали, что так оставили. Потом с течением времени учетную запись могут отключить или сменить пароль, что сразу делает ваш пул неработоспособным, он просто не может запустить его. Исходя из этого проверьте данную ситуацию. В дополнительных параметрах найдите раздел «Удостоверение» и посмотрите от имени кого у вас запущен ваш пул, по умолчанию должна быть встроенная учетная запись «ApplicationPoolidentity».
При необходимости вы можете выбрать другую учетную запись для запуска пула. После изменения, обязательно перезапустите пул, а лучше саму службу IIS.
Отключение Load User Profile на пуле IIS
Когда пользователь входит в систему в интерактивном режиме, система автоматически загружает профиль пользователя. Если служба или приложение олицетворяет пользователя, система не загружает профиль пользователя. Поэтому служба или приложение должны загрузить профиль пользователя с помощью LoadUserProfile .
Службы и приложения, которые вызывают LoadUserProfile, должны проверить, есть ли у пользователя временный профиль. Если пользователь имеет перемещаемый профиль, указать путь к нему в качестве lpProfilePath члена PROFILEINFO.
Для IIS этот параметр указывает, должна ли служба загружать профиль пользователя для удостоверения пула приложений. Если значение этого параметра «True», то служба IIS загружает профиль пользователя для удостоверения пула приложений. Если необходимо поведение IIS 6.0 без загрузки профиля пользователя для удостоверения пула приложений задайте значение «False«. Так, что если получаете «HTTP Error 503. The service is unavailable» и ничего не помогает, то пробуем его отключить.
Не создает временный файл конфигурации пула
Ошибку «Service Unavailable: HTTP Error 503. The service is unavailable» вы легко можете ловить из-за того, что ваш пул по какой-то причине не может создать временный файл конфигурации и об этом может свидетельствовать предупреждение в логах:
Службе активации процессов Windows не удалось создать файл конфигурации пула приложений для пула приложений < DefaultAppPool >. Тип ошибки: «5». Чтобы решить эту проблему, убедитесь, что файл applicationhost.config указан правильно, и повторите последние изменения конфигурации. Поле данных содержит номер ошибки.
Подробнее об этом на — https://support.microsoft.com/en-in/help/4050891/error-http-503-and-was-event-5189-from-web-applications-on-windows-10
Все происходит по причине того, что служба активации Windows (WAS) создает временный файл конфигурации для каждого пула приложений IIS в папке C:inetpubtempappPools во время обычной работы.
На начальном этапе обновления «Центр обновления Windows» сканирует существующие папки и файлы и записывает их пути для восстановления после обновления. Однако, поскольку файлы конфигурации являются временными, они удаляются при остановке WAS.
На следующем этапе Центра обновления Windows эти ранее отсканированные файлы и папки копируются во временную папку обновления. После обновления Windows «Центр обновления Windows» создает символическую ссылку на каждую папку, которая была скопирована во временное местоположение обновления, прежде чем он пытается восстановить эти файлы и папки в их исходное местоположение.
Однако поскольку эти временные файлы конфигурации больше не существуют, Центр обновления Windows не удаляет символические ссылки.
Когда WAS пытается запустить как рабочий процесс IIS, он не создает временную папку для записи конфигурации из-за символических ссылок. Поэтому Http.Sys возвращает ошибку HTTP 503.
Чтобы решить эту проблему, вручную удалите символические ссылки, созданные «Центром обновления Windows». Для этого выполните следующие действия:
- Из командной строки от имени администратора
net stop WAS /y
rmdir /s /q C:inetpubtempappPools
net start W3SVC
- Из оболочки PowerShell в режиме администратора
Stop-Service -Force WAS
Remove-Item -Recurse -Force C:inetpubtempappPools*
Start-Service W3SVC
Два сайта на 443 порту
Был интересный случай в прошлом, мне нужно было перенести один сайт с IIS на другой сервер. После переноса вместо сайта я видел уже вам известную ошибку «Service Unavailable: HTTP Error 503. The service is unavailable». Самое интересное, что ошибка была только для HTTPS, в то время как HTTP работал нормально. Напоминаю, что по умолчанию https использует порт 443, зная это я решил посмотреть, что слушает порт, можно было конечно воспользоваться утилитами netstat или TCPView, но я пошел в тот момент через PowerShell. Введите команду, чтобы посмотреть, что порт слушается.
Get-NetTCPConnection -LocalPort 443 -State Listen
Как видно сервер слушается.
Если вы когда-нибудь столкнетесь с такой проблемой как 503 ответ, то попробуйте остановить службу веб-публикации
Stop-Service -Name w3svc -PassThru
И после этого опять запустить команду на прослушивание, если и в этом случае вы видите, что 443 порт ответил, то поздравляю у вас есть другой сервис мешающий IIS.
Если это сервер, который вы унаследовали, может быть нелегко определить, что прослушивает этот конкретный порт. Я установлю модуль PowerShell с именем Carbon (https://www.powershellgallery.com/packages/Carbon/) из галереи PowerShell, чтобы определить, что происходит.
Install-Module -Name Carbon -Force -AllowClobber
Когда веб-сервер не-IIS установлен в Windows, он устанавливает ACL для порта, который будет прослушивать. Вы можете увидеть ACL, который ссылается на порт 443.
То же самое через cmd — netsh http show urlacl
На самом деле, есть две записи для порта 443. Тот, у кого GUID все в порядке, так как он предназначен только для конкретного приложения через заголовок узла, а не по всему пространству имен.
Второе я вычислил через TCPView, это было приложение Dell EqualLogic SAN Headquarters, установленное на этом конкретном сервере, оно вызывало проблему, поэтому я решил удалить его, так как оно больше не нужно.
Хоть я и удалил Dell EqualLogic SAN Headquarters с сервера, это не удалило ACL, назначенный порту 443.
Поскольку деинсталляция приложения не решила проблему, я решил принудительно удалить ACL
Revoke-HttpUrlPermission -Url https://+443/ -Principal ‘NT AUTHORITYSYSTEM’
То же самое через cmd — netsh http delete urlacl url = [вставить URL]
После удаления этой записи и перезапуска веб-службы проблемы с прослушиванием IIS через порт 443 были решены.
Кстати можно в логах посмотреть кто установил ACL, но там не всегда все подробно. Выполните:
Get-WinEvent -FilterHashtable @{LogName=’System’;ProviderName=’Microsoft-Windows-HttpEvent’;Level=4} -MaxEvents 1 | Select-Object -Property Message
Дополнительные методы
- Перезагрузить сайт, через клавиши CTRL+F5
- Перезагрузите модем или компьютер
- Очистить кеш браузера
- Проверьте настройки прокси
- Если ошибку получаете в каком-то сервисе на телефоне, то попробуйте обновить приложение
- Проверка диска C: на ошибки
Contents
- Cause of HTTP Error 503
- Rapid-Fail Protection
- Debugging HTTP Error 503
- Fixing HTTP Error 503
- Common 503 substatus codes
- Conclusion
- Author
- Recent Posts
Surender Kumar has more than twelve years of experience in server and network administration. His fields of interest are Windows Servers, Active Directory, PowerShell, web servers, networking, Linux, virtualization, and penetration testing. He loves writing for his blog.
Latest posts by Surender Kumar (see all)
- Extending LVM space in Ubuntu — Thu, Feb 2 2023
- Backup in Proxmox VE — Thu, Jan 26 2023
- Snapshots in Proxmox VE — Wed, Jan 25 2023
Cause of HTTP Error 503
HTTP Error 503 is another very common error you might face with an IIS-hosted website in addition to the 500 – Internal server error.
HTTP Error 503. The service is unavailable
The primary reason for this error is a stopped or disabled application pool. The application pool is the IIS component that initiates a worker process, which then allows the web server to process incoming requests for a website. When something is wrong with the application pool, the web server throws an HTTP Error 503.
Rapid-Fail Protection
There can be various reasons for an application pool failure, such as an unhandled exception in the code, an expired password for the application pool identity, or something else. By default, IIS is configured to disable a malfunctioning application pool if its worker process faces five consecutive crashes within a period of five minutes. This setting is known as Rapid-Fail Protection, which is available under the Advanced Settings of an application pool. This is shown in the following screenshot:
Viewing or modifying the rapid fail protection setting for an application pool
- Enabled—The value True indicates that the rapid-fail protection feature is active, which is the default. Set the value to False to disable it.
- Failure Interval (minutes)—The time interval to specify the number of minutes (by default, 5) to count the failures for a process.
- Maximum Failures—The maximum number of failures that are allowed within the time interval mentioned above (by default, 5).
While troubleshooting an application pool-related problem, you can modify these parameters, if needed.
Debugging HTTP Error 503
To determine the exact reason why the application pool is disabled or stopped, open the Event Viewer, navigate to the System log, and look for error or warning events whose source is Windows Process Activation Service (WAS). WAS is responsible for starting/stopping the application pool and keeping track of worker processes in the IIS.
The following screenshot shows that the application pool is disabled because its identity is invalid:
Checking the system log to identify the cause of application pool failure
If you couldn’t find anything in the System log, take a look in the Application log since the ASP.Net-related exceptions are logged there. As discussed above, when a worker process experiences five fatal errors or exceptions within five minutes, rapid-fail protection kicks in and automatically disables the faulting application pool.
Based on event logs, if you conclude that the reason for application pool failure is a bug in the application code, but you still want to keep the application pool running until your developer fixes it, you could temporarily adjust the behavior of rapid-fail protection, either by increasing the Maximum Failures or the Failure Interval to a higher value. You could even disable this feature by using the following PowerShell command:
(Get-IISAppPool awesomewebsite.com).failure.rapidFailProtection Set-WebConfigurationProperty '//*[@name="awesomewebsite.com"]//failure' -Name rapidFailProtection -Value $False
Viewing and disabling the rapid fail protection for an application pool with PowerShell
Remember that the rapid-fail protection feature is there for the safety of the web server, so disabling it shouldn’t be considered a solution to the problem. Instead, fixing the underlying cause (or bug causing the behavior) in the application code is really important. Anyway, disabling it sometimes comes in handy if developers are taking longer to fix the bug; meanwhile, you want to keep the web application up and running. Once rapid-fail protection is disabled, the web server won’t disable the faulting application pool, and visitors will no longer see HTTP Error 503.
Fixing HTTP Error 503
A simple resolution for HTTP Error 503 is to start the application pool corresponding to your website. If you get an application pool identity-related error or warning, make sure the username and password for the identity are correct. If a custom username is used, make sure its password is not expired. If possible, set the password to never expire for that user.
If the application pool stops repeatedly but there is no application pool identity-related error in the system log, the issue is likely due to some fatal error or unhandled exception in the code. In that case, the application log can give you some useful insights. The following screenshot shows a typical error logged in the application log that occurred due to an unhandled exception:
Checking the application log to identify the cause of application pool failure
If you see such errors or warnings, notify your application developers, and ask them to fix the exception. If needed, share the detailed error message recorded in the event log.
Common 503 substatus codes
The following table covers the common HTTP 503 substatus codes, along with their possible causes and troubleshooting advice:
| Status Code | Possible Cause | Troubleshooting Advice |
| 503.0 | The application pool is unavailable | The application pool is either stopped or disabled. To fix this error, start the application pool corresponding to your website. If it fails repeatedly, check the event log to understand why it is failing. We covered how to fix this error above. |
| 503.2 | The concurrent request limit has exceeded | The appConcurrentRequestLimit is a serverRuntime attribute that specifies the maximum concurrent requests (with a default value of 5000) that can be queued for application. The 503.2 error indicates that this limit has been exceeded. To resolve this error, you can increase the value using the following command:
%SystemRoot%System32inetsrvappcmd.exe set config /section:serverRuntime /appConcurrentRequestLimit:100000 If you get ERROR ( message:Unknown attribute «appConcurrentRequestLimit». Replace with -? for help. ) while running this command, use the following command instead: %SystemRoot%System32inetsrvappcmd.exe set config /section:system.webserver/serverRuntime /appConcurrentRequestLimit:100000 |
| 503.3 | The ASP.NET queue is full | The requestQueueLimit attribute specifies the maximum number of requests (with a default value of 1000) that can be queued by the ASP.NET process. When this queue is full, the 503.3 error is returned. To resolve this error, set the Queue Length attribute to a higher value in the application pool’s advanced settings. See this image for reference. Usually, exceeded queue length is a sign of a server unable to keep up with the requests. Therefore, you could use performance counters to understand why the server is struggling. |
| 503.4 | The FastCGI queue is full | This error occurs when the FastCGI process queue is full. To fix this error, increase the value of the Queue Length attribute for your FastCGI process. To do so, open the IIS Manager, click the server name, and double-click FastCGI Settings. Now, double-click the FastCGI process for the particular PHP version that your application is using, and increase the value of Queue Length. See this image for reference. |
Subscribe to 4sysops newsletter!
Conclusion
You can see that, like most IIS errors, HTTP Error 503 can be fixed with the help of detailed errors and failed request tracing. However, in the event of application pool-related errors, the HTTP.sys driver throws the 503.0 error because the application pool isn’t available to handle the request. Thus, the detailed error or failed request tracing rule is not even triggered. In such situations, you can rely on Windows event logs to troubleshoot.
In our role as Web support engineers, we resolve and prevent service errors in both Linux and Windows servers. Recently we were contacted by a Windows server owner who was getting “HTTP Error 503. The service is unavailable” in his websites.
Upon examining the EventViewer logs, we could see the error “A process serving application pool ‘plesk(default)(4.0)(pool)’ suffered a fatal communication error with the Windows Process Activation Service”.
See how we help web hosting companies
Today we’ll see what causes IIS “HTTP Error 503. The service is unavailable.” error and how we resolved it.
Our Windows server experts noted that all the domains in the server were using the same application pool [ie. ‘plesk(default)(4.0)(pool)’]. In our experience handling such errors, the following causes have been noted for this error.
- Application Pool of the corresponding Wep Application is Stopped – In an IIS server, the domains are assigned to application pools, some dedicated and some shared. If the associated application pool for a domain is in stopped or disabled state, it would cause the website to show “HTTP Error 503. The service is unavailable.” message.
- Any misconfiguration in the application pool or site settings, such as spawning applications in 32-bit mode, that can tamper with its proper functioning, can cause error in the site. Improper IIS configuration have noted to cause the worker process to fail. Process crashes also happen due to incorrect application logic. In some cases, the web server protocol may not be enabled in the site settings, and the site can show up ‘HTTP Error 503.’
- Issues related to the user Identity of application Pool – An application pool is associated with a user identity, which allows you to run that application pool under a unique account. This user account can get locked at times, can have its password expired, or may not have adequate privileges to run the application pool. Any of these issues can tamper with the website functioning.
- Application pool running out of RAM or other server resources, causing it to crash, often lead to ‘HTTP Error 503.’
- Server migrations have also seen to have caused such errors in the website, if the IIS configuration settings of two servers are not compatible with each other, which can affect domain performance.
[ You don’t have to lose your sleep over server errors. Our expert server support specialists monitor & maintain your servers 24/7/365 and keep them rock solid. ]
How to resolve IIS “HTTP Error 503. The service is unavailable.” error
To pinpoint the actual cause of the 503 error, we examine the System event logs, which gives a hint towards what is the reason for the error. Based on that, we follow various debugging methods to resolve it.
If the error is due to a stopped application pool, then usually starting it would resolve the issue. From the IIS Manager -> Application Pools node, right click on the DefaultAppPool to check the status.
On noticing that the service is stopped, we start it. If the service is running, we try restarting it and the error would be gone. But in most cases, the fix may not be as simple as that.
In cases where the application pool crashes frequently, restarting it all the time is not the right way to fix it. We monitor the server and debug further into what is causing the application pool to crash.
For websites that are resource-intense, it is always better to assign a dedicated application pool for that domain. Another aspect we check and fix the settings of application pool and site, such as enabling the relevant protocol.
One of the key issues many fail to notice, is the user identity settings. We check the account settings and password of the identity and confirm that it is working fine. If mismatch noted, we would update the settings.
However, in this specific scenario, the issue was due to inadequate permissions of the application to run, which caused the error. By reconfiguring the application pool to run with a higher privileged identity, we were able to resolve the issue.
To avoid resource crunch leading to application crashes, we also optimized the IIS server and could see improvement in the capacity to handle connections with lesser CPU usage.
[ Use your time to build your business. We’ll take care of your servers. Hire Our server experts to resolve and prevent server issues. ]
At Bobcares, our 24/7 Support Engineers constantly monitor all the services in the server and proactively audit the server for any errors or corruption in them.
With our systematic debugging approach for service or other software errors, we have been able to provide an exciting support experience to the customers.
If you would like to know how to avoid downtime for your customers due to errors or other service failures, we would be happy to talk to you.
PREVENT YOUR SERVER FROM CRASHING!
Never again lose customers to poor server speed! Let us help you.
Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure./p>
SEE SERVER ADMIN PLANS
var google_conversion_label = «owonCMyG5nEQ0aD71QM»;
Ошибка 503 Service unavailable (сервис недоступен) — означает, что данный сайт к которому вы подключаетесь, недоступен. Связано это с тем, что сервер на котором находится данный сайт, не может обработать количество одновременных запросов в базе данных. Это также могут быть технические работы на хостинге или просто перезагрузка сервера. В большинстве случаях, пользователь не причастен к этой ошибке, так как эта ошибка на стороне сервера. Нужно всего лишь подождать и перезагрузить страницу, чтобы ошибка 503 исчезла. Тем не менее, существуют ситуации, когда возникает ошибка 503 по вине системы Windows 10.
Как исправить ошибку 503 service unavailable
- Откройте другой сайт и проверьте работает ли он.
- Обновите страницу данного веб-сайта Ctrl+F5.
- Перезагрузите модем и компьютер.
- Если вы используете сторонние программы или расширения для браузера как VPN, прокси, то удалите их.
- Если вы веб-мастер, то попробуйте зайти с другого устройства и браузера. Проверьте свой сервер на доступность (обратитесь в тех.поддержку хостинга). Скорее всего он перестал работать из-за большого количества запросов к базе данных. Возможна Ddos-атака на ваш сайт.
Ошибка HTTP Error 503 The service is unavailable с кодом события WAS 5189
Если используете компьютер под управлением Windows 10 или Windows Server 2016 с включенными службами IIS (Internet Information Services), и вы обновляете систему до более новой версии, то некоторые веб-приложения могут не запуститься и выдавать ошибку 503. Если вы посмотрите журнал событий, можете обнаружить код события WAS 5189, который говорит, что не удалось создать файл конфигурации пула для приложения.
Как это работает?
Ошибка 503 возникает из-за того, что служба активации процессов Windows (WAS) создает временный файл конфигурации для каждого пула приложений IIS в папке по пути C:InetpubTempAppPools во время работы. На начальном этапе обновления, «Центр обновления Windows» сканирует существующие папки, файлы и записывает их пути, которые будут восстановлены после обновления. Однако, поскольку файлы конфигурации являются временными, они удаляются при остановке службы WAS. Далее отсканированные файлы и папки копируются во временную папку обновления. После обновления Windows, «Центр обновления Windows» создает символическую ссылку на каждую папку, которая была скопирована во временное местоположение обновления, прежде чем он пытается восстановить эти файлы и папки в их исходное местоположение. Получается, что эти временные файлы конфигурации больше не существуют и «Центр обновления Windows» не удаляет символические ссылки. Когда WAS пытается запустить как рабочий процесс IIS, он не создает временную папку для записи конфигурации из-за символических ссылок. Поэтому http.sys возвращает ошибку HTTP 503.
Microsoft рекомендуют удалить эти ссылки, чтобы решить эту проблему. Для этого откройте командную строку от имени администратора и введите следующую команду целиком:
net stop WAS /y
rmdir /s /q C:inetpubtempappPools
net start W3SVC
Примечание: Вы также можете вручную удалить эти ссылки C:inetpubtempappPools.
Смотрите еще:
- Как исправить ошибку 502 Bad Gateway в браузере
- Код ошибки 105 ERR_NAME_NOT_RESOLVED в Google Chrome
- Обновление функции до Windows 10. Ошибка 0x80d02002
- Как заблокировать доступ к сайту в Windows 10 без программ
- Как создать и настроить FTP-клиент для Windows 10
[ Telegram | Поддержать ]
Learn how to get rid of this error for good
by Milan Stanojevic
Milan has been enthusiastic about technology ever since his childhood days, and this led him to take interest in all PC-related technologies. He’s a PC enthusiast and he… read more
Updated on January 26, 2023
Fact checked by
Alex Serban
After moving away from the corporate work-style, Alex has found rewards in a lifestyle of constant analysis, team coordination and pestering his colleagues. Holding an MCSA Windows Server… read more
- Browsers are essential tools for surfing the Internet, they are the middleman between your computer and the websites you visit.
- There are plenty of different browsers on the market, each targetting specific user needs, but there is one thing that browsers have in common: error 503.
- HTTP error 503: The service is unavailable is one of the most frequent error codes affecting browsers.
- Easy migration: use the Opera assistant to transfer exiting data, such as bookmarks, passwords, etc.
- Optimize resource usage: your RAM memory is used more efficiently than in other browsers
- Enhanced privacy: free and unlimited VPN integrated
- No ads: built-in Ad Blocker speeds up loading of pages and protects against data-mining
- Gaming friendly: Opera GX is the first and best browser for gaming
- Download Opera
HTTP errors usually come in the form of status codes which are standard response codes that help you identify the cause of the problem given by a website server when either a web page or other resource fails to load properly while online.
Whenever you get an HTTP status code, it comes with the code itself, and the corresponding explanation such as HTTP error 503: The service is unavailable.
Something else you may want to keep in mind is that each of these codes, also known as browser errors, Internet error codes or Internet connection errors have its groups.
What is the HTTP error 503?
The HTTP 503 error falls under the 5xx server error group of HTTP status codes. They usually indicate that the web page or resource request is understood by the server, but the latter cannot fill it for one reason or another.
However, the HTTP error or status codes shouldn’t be confused with Device Manager errors or system error codes, because the latter is associated with different errors and meanings altogether.
When you get HTTP error 503, this usually points to the website’s server, which may have been compromised by an overload (temporarily) or it is too busy, or there’s some ongoing such as scheduled maintenance.
Fortunately, although this error comes up often, there are fairly quick solutions to fix the issue and get the website back online.
What is HTTP error 503 and how can I fix it?
- Preliminary checks
- Close your proxy server
- Start the destination application pool
- Change Load User Profile
- Change Identity in Application Pool
1. Preliminary checks
Whether the issue is with the server or your computer, there are some things you can try and check before fixing HTTP error 503: The service is unavailable. You could start by retrying the URL from the address bar by reloading or refreshing the page.
You can also restart your modem and router, then restart your computer or device – this is especially so if you see the ‘service unavailable – DNS failure’ message. If this doesn’t fix the error 503 DNS issue, pick new DNS servers and change them on your PC or router.
Check with the website itself directly for assistance as they may be aware of the error 503, so they may let you know if it is an issue that’s with everyone, not just you. Sometimes waiting it out is the easiest fix to this error.
- ALSO READ: 4 best browsers with built-in VPN you should use today
2. Close your proxy server
Perhaps you use a VPN or a proxy server, in which case, you need to check whether the connection is working the way it should, or properly. If the proxy server is down, then you may end up getting the HTTP error 503: The service is unavailable message.
This usually happens with free proxy servers, but if you do not use a proxy server, you can disable it and then try to open the website that is showing the HTTP error 503 the service is unavailable.
3. Start the destination application pool
If the application pool of the corresponding web application is stopped, or disabled, it causes the website to show HTTP error 503: The service is unavailable.
Additionally, any misconfiguration in the application pool or site settings can cause an error on the site. Process crashes also happen due to incorrect application logic.
Sometimes the user account related to the user identity of an application pool can be locked or has an expired password or even inadequate privileges which tamper with the functioning of the website.
Some PC issues are hard to tackle, especially when it comes to corrupted repositories or missing Windows files. If you are having troubles fixing an error, your system may be partially broken.
We recommend installing Restoro, a tool that will scan your machine and identify what the fault is.
Click here to download and start repairing.
If the application pool runs out of RAM or other resources, it can crash and lead to HTTP error 503, plus server migrations also lead to such errors.
If HTTP error 503 the service is unavailable is caused by a stopped application pool, starting it would resolve the issue.
- Click Start
- In the search bar, type Windows Features
- Select Turn Windows Features on or off
- Locate Internet Information Services and check the box – this will install everything you need to use IIS
- Go to Control Panel
- Select View By and click Large Icons
- Click Administrative Tools
- Find IIS Manager and double-click on it
- Select Application Pools node
- Right-click on DefaultAppPool to check the status. If it is stopped, start it. If it is running, restart it and see if HTTP error 503 the service is unavailable is gone.
- ALSO READ: 3 best browsers with VPN that don’t slow down Internet connection
4. Change Load User Profile
If the problem is the DefaultAppPool, change the ‘Load User Profile’ to false by doing the following:
- Go to Control Panel
- Select View By and click Large Icons
- Click Administrative Tools
- Find IIS Manager and double click on it
- Select Application Pools node
- Click on DefaultAppPool to select or highlight it
- On the right pane, select Advanced settings
- Find Process Model
- Go to Load User Profile
- Change from True to False
5. Change Identity in Application Pool
- Go to Control Panel
- Select View By and click Large Icons
- Click Administrative Tools
- Find IIS Manager and double-click on it
- Select Application Pools node
- Find the correct Application Pool for your website and click on it
- Click Advanced Settings
- Under Process Model, select Identity and change it, then enter a new user and password
- Click on your Application Pool again and select Recycle to restart it.
- Reload the website
- Restart your modem and your computer
- Clear the browser cache
- Check your proxy settings
- Restart the DefaultAppPool
- What does service temporarily unavailable mean?
The error message Service temporarily unavailable indicates the server is not available either due to overloading issues or scheduled maintenance work. This is only a temporary issue, the service should get back online once the problem has been solved.
How can I fix error 503 on specific services?
1. Fix Tachiyomi HTTP error 503
This error affects Manga fans since Tachiyomi is a popular Manga reader for Android. PC users can also use this app with the help of an emulator or a bootable USB device. Here’s how to fix error 503 on Tachiyomi:
- Update the app, and make sure you’re using the latest version.
- Reset your Internet connection, and restart your modem and computer.
- Go back to the chapter menu, reload a new chapter and resume reading.
- Open a manga from the catalog throwing error 503. Click on the menu and select the option that allows you to open it in the browser. Close the browser and the source should be fixed now.
2. Fix HTTP error 503 the service is unavailable in IIS
To fix error 503 on IIS, you can do so through the built-in Application Pool. IIS stands for Information System Security and can be easily modified through the following steps.
1. Enable IIS
- Press the Windows Key and type windows features in the search box.
- Click on the result to open the Windows Features tab.
- Check the box next to Internet Information Services to enable it.
2. Start the Application Pool
- Press the Windows Key and type control panel.
- Click on the result to open Control Panel.
- Select Administrative Tools from the list.
- Find IIS Manager and click on it.
- Click on View Application Pools from the actions tab.
3. Change the AppPool username and password
- Go to Server, select the Application Pools and select the Application Pool of your website.
- Go to Advanced Settings and select Identity.
- Enter a new username and password, click on your Application Pool again.
- Select Recycle to restart it.
4. Tweak the Load User Profile
- Open the Advanced Settings of the DefaultAppPool.
- Change the Load User Profile option to false as shown at step 4.
5. Delete the URL ACL
If the URL’s ACL is reserver somewhere else in the system, you’re bound to get error 503. Here’s how to fix that:
- Open the console command and enter the netsh http show urlacl command to dump all URL ACLs.
- If the command returns the URL that triggered error 503, delete it using the netsh http delete urlacl url=[Insert URL] command.
3. Fix urllib.error.httperror: http error 503: service unavailable
Here’s what you can do to fix urllib 503 errors:
- Reset your Internet connection. Or connect to a different network (eg: temporarily switch to your mobile hotspot).
- Replace urllib by curl
4. Fix www.netflix.com is currently unable to handle this request. HTTP error 503
We’re sure one of these solutions will help you fix the problem:
- Try a different Internet connection if available.
- Make sure your firewall settings are not blocking Netflix.
- Sign in to your Netflix account using another device.
- Clear your browser’s cache and cookies.
You may also want to try the solutions listed in this Netflix site error troubleshooting guide.
5. Fix Subsonic HTTP error 503
To fix error 503 on Subsonic, follow these steps:
- Clean your Subsonic database. But first, do keep a copy of your database folder. Then, open the subsonic.data file and deleted all the media entries. Keep only the settings.
- Reinstall the player.
Did any of these solutions help fix HTTP error 503? Let us know by leaving a comment in the section below.
Newsletter
- Remove From My Forums
-
Question
-
Hello,
I’m trying to run my web applications on IIS 10 on Windows 10 Pro, but the browser display following error — HTTP Error 503. The service is unavailable. Moreover, in the IIS Manager console, in the Application pool section — the application pools for corresponding
web application are in «stopped» state — these stopping immediately when I try to run whatever application. I reviewed the Windows Event Viewer, Windows Logs, the Application log — there are many records reporting same error:The worker process for application pool ‘DefaultAppPool’ encountered an error ‘Cannot read configuration file’ trying to read configuration data from file ‘\?<EMPTY>’, line number ‘0’. The data field contains the error code.
This happened after the Windows was automatically updated to the «Feature Update 1709».
More info:
<Provider Name=»Microsoft-Windows-IIS-W3SVC-WP» Guid=»{……}» EventSourceName=»W3SVC-WP» /> — for the reported error.OS: Windows 10 64 bit Pro Version 1709 Build 16299.19
OS: Original before the last update — Build 1703
IIS version 10.0.16299.15
Installed: MS Visual Studoio 2015 & 2017 Community editions
IIS URL rewrite module 2 — version 7.2.1980Could anyone help me?
-
Edited by
Monday, October 23, 2017 1:08 PM
-
Edited by
Answers
-
Try this solution: https://superuser.com/questions/1260805/iis-10-cannot-read-empty-configuration-file/1260830
-
Proposed as answer by
Joy-Qiao
Tuesday, October 24, 2017 9:15 AM -
Marked as answer by
gkirov
Tuesday, October 24, 2017 6:55 PM
-
Proposed as answer by
-
Hi,
Microsoft released a related article about your issue named as Web applications return HTTP Error 503 and WAS event 5189
on Windows 10 Version 1709 (Fall Creators Update) last week.Please check if you have the same symptom in event log «WAS event 5189» as recorded in this upper article.
If the symptom is same with you, please try the solutions and feedback the result.
To resolve this problem, manually delete the symbolic links that are created by Windows Update. To do this, follow these steps.
Note Symbolic links can be deleted the same as regular files.
Open a Windows PowerShell window by using the Run as administrator option.
Run the following commands:
Stop-Service -Force WAS
Remove-Item -Recurse -Force C:inetpubtempappPools*
Start-Service W3SVCBests,
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com.-
Proposed as answer by
Joy-Qiao
Tuesday, October 24, 2017 9:15 AM -
Marked as answer by
gkirov
Tuesday, October 24, 2017 6:55 PM
-
Proposed as answer by