Reporting services – The request failed with HTTP status 503 Service Unavailable
The other day, I have powered ON my Configuration Manager lab after long a time to test something on the reporting and found that, the reporting URL does not work.
Browsing the reports URL leads to service unavailable with http error 503, The service unavailable.
I have verified that, the SQL server reporting services is running fine and i have restarted the service as well to check if this works or not but no luck.
I have realized that, there is something seriously wrong and took sometime to troubleshoot further.
The first log to check is srsrp.log (ConfigMgr log) for reporting services located in your configMgr installation directory\logs folder.
The log has the following errors:
The request failed with HTTP status 503: Service Unavailable.
(!) SRS not detected as running
Failures reported during periodic health check by the SRS Server CMserver.domain.name
I have also checked the reporting server configuration manager, everything seems to be fine.
The next is to look at the SQL server reporting services log located in
C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\LogFiles
The log has the following error messages:
configmanager!DefaultDomain!5018!04/04/2021-14:23:28:: e ERROR: Error loading configuration file: The evaluation period for this instance of Microsoft SQL Server Reporting Services has expire d. A license is now required.
appdomainmanager!DefaultDomain!5018!04/04/2021-14:23:28:: e ERROR: Appdomain:1 DefaultDomain failed to initialize. Error: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. ---> Microsoft.ReportingServices.Diagnostics.EvaluationCopyExpiredException: The evaluation period for this instance of Microsoft SQL Server Reporting Services has expired . A license is now required..
AS you can see in the log, the license has expired for SQL server reporting services.
When you install the SQL server reporting services, you will be asked for the trail of 180 days or input the license key of the SQL server.
If you choose trail, then after 180 days, you will have the same issue like mine.
So now, we found that, the license for the SQL server reporting services is expired, how do we activate it now?
The only way that I could find is to reinstall the reporting services.
Run the SQL server reporting services installation wizard (I did 2019), you will see the following options. Choose upgrade, you will be asked for the key to activate it.
Once the installation is completed, wait for the reporting services to check the license status and rebuild the reports (there wont be any changes your default/custom reports) and after sometime, your reporting URL will be up and running.
hope this helps!
Enhancing Troubleshooting with Verbose Logging in SCCM
Troubleshooting Co-Management wufb Workloads and the WMI StateMsg Namespace
SCCM Right Click Tool Managed workloads of co-managed device
Streamlining Primary User UPN Fix in Intune Using PowerShell
Post comment cancel reply.
Save my name, email, and website in this browser for the next time I comment.
Notify me of follow-up comments by email.
Notify me of new posts by email.
SQL Server Reporting Services Web Portal URL returns a 503 error
Article id: 226059, updated on:, issue/introduction.
Accessing the SQL Server Reporting Services (SSRS) Web Portal URL while troubleshooting reports displays no content and returns a 503 error. The following error is captured in the SSRS server log:
ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: Invalid PBI Configuration, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. ;
To troubleshoot this error, follow this procedure:
- Locate the SSRS configuration file rsreportserver.config on the server hosting SSRS; e.g., %SystemDrive%\Program Files\Microsoft SQL Server\MSRS13.<instance name>\Reporting Services\ReportServer\rsreportserver.config
- Open the file with a text editor
- Inspect the <URLReservations> key for duplicate <Application> keys; e.g., <Name>ReportServerWebApp</Name>
- If duplicates are found, delete the duplicate entry or entries
- Save and close the file
- Restart the SQL Server Reporting Services service
- If no duplicates were found in step 4, open Reporting Services Configuration Manager (RSCM)
- Connect to the server and instance hosting the IT Analytics reports
- Select the Encryption Keys page
- Click the Delete button to Delete Encrypted Content
- Click the Yes button to confirm the deletion
- Click the Exit button to close RSCM
- Open the IT Management Suite console
- Navigate to Settings > Notification Server > IT Analytics Settings > Connections > Symantec CMDB
- Click the Update Dependencies button
- Navigate to Settings > Notification Server > IT Analytics Settings > Configuration
- Select the pencil icon to edit the Report Server Virtual Directory URL
- Click the Verify Connection button to verify the ReportServer Virtual Directory URL
- Edit the Authentication Type to use stored credentials and enter the credentials of the account specified as the Service Account identity in RSCM
- Navigate to Settings > Notification Server > IT Analytics Settings > Reports and install the reports you wish to use
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
SSRS web portal not working .Service unavaialble 503
I have installed SSRS 2016 and 2019. But 2019 is not working when i try to access from the browser. i am getting service unavailable 503 error. I have restarted service and all. but no luck. When i check the log. I found this :
2022-05-29 08:10:00.1663|INFO|1|File Logger created: C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\LogFiles\RSHostingService_2022_05_29_08_10_00.log - level Info, will roll at 32 Mb, process id 36452 2022-05-29 08:10:00.1863|INFO|1|Current Directory : C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\RSHostingService 2022-05-29 08:10:00.2263|INFO|6|Updating application config files 2022-05-29 08:10:00.2263|INFO|6|Syncing service machine key 2022-05-29 08:10:00.3163|INFO|6|Launching Process : Management Service 2022-05-29 08:10:00.3163|INFO|6|Starting Process: C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\Management\RSManagement.exe 2022-05-29 08:10:00.3163|ERROR|6|Exception starting process.System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo) at Microsoft.BIServer.BIService.ProcessLaunchers.DefaultProcessLauncher.Start() 2022-05-29 12:24:08.0776|INFO|1|Logger shutting down
SQL Server Reporting Services A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports. 2,600 questions Sign in to follow
A 503 Service Unavailable Error indicates that a web server is temporarily unable to handle a request. That could be the web server you’re trying to access directly, or another server that web server is in turn trying to access. It’s called a 503 error because that’s the HTTP status code that the web server uses to define that kind of error. The error can occur for a number of reasons, but the two most common reasons are that the server is overwhelmed with requests or is having maintenance performed on it.
I refer to this thread：https://www.howtogeek.com/360903/what-is-a-503-service-unavailable-error-and-how-can-i-fix-it/
Base on my understanding, one SQL Server corresponds to one SSRS , do you use two SSRS on the same SQL Server? I guess It may be that the two SSRS are somewhat conflicting.
Best Regards, Isabella
If the answer is the right solution, please click " Accept Answer " and upvote it. If you have extra questions about this answer, please click " Comment ". Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Yes. Both SQL server 2016 and 2019 are in one server
KB2285517 - FIX: "HTTP 503: Service unavailable" error message when you execute a report in SQL Server 2008 R2
Microsoft distributes Microsoft SQL Server 2008 R2 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release.
When you execute a report in SQL Server 2008 R2, you may receive an “HTTP 503: Service unavailable" error message. In this scenario, the ReportingServicesService.exe process crashes and you cannot connect to Microsoft SQL Server Reporting Services. If you examine the System log when this issue occurs, you find an error messages that resembles the following: Log Name: System Source: Service Control Manager Date: <Date Time> Event ID: 7031 Task Category: None Level: Error Keywords: Classic User: N/A Computer: <Computer Name> Description: The SQL Server Reporting Services (MSSQLSERVER) service terminated unexpectedly. It has done this <number> time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
SQL Server 2008 R2
The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2261464 Cumulative update package 3 for SQL Server 2008 R2Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packagesFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Need more help?
Want more options.
Explore subscription benefits, browse training courses, learn how to secure your device, and more.
Microsoft 365 subscription benefits
Microsoft 365 training
Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.
Ask the Microsoft Community
Microsoft Tech Community
Microsoft 365 Insiders
Was this information helpful?
Thank you for your feedback.
Feb 8, 2022 • Knowledge
When dragging and dropping items from the BizInsight Navigation Pane or refreshing a BizInsight report, users receive the following error:
The request failed with HTTP status 503: Service Unavailable.
This error occurs when either the SQL Server and/or the SQL Server Reporting Services services are not running or cannot be accessed. There are two possible causes for this issue.
- Start the Reporting Services Service
- Check that Reporting Services is licensed
- Go back to the client workstation and test BizInsight again to see if the issue is resolved.
- NOTE : The default location for the LogFiles directory is C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\LogFiles.
- Sort the directory contents by Date modified and open the most current "RSManagement" log file with Notepad.
- To resolve this issue, the Reporting Services installation must be repaired and the SQL Server product key entered. To locate the SQL Server product key, follow the steps in this Microsoft Docs article: Find the product key for SQL Server Reporting Services .
For Further Assistance
If this article does not resolve the issue, please contact insightsoftware Support for further assistance.
Article feedback, related articles.
- Number of Views 395
- Number of Views 1.68K
- Number of Views 1.44K
- Number of Views 1.47K
- Number of Views 1.27K
- How to Display Transaction code number in SAP menu
- BizNet - The following feature couldn't be installed OR Error installing .NET Framework 3.5
- How-to: Converting Gregorian dates to Julian dates
- Event1 Software Downloads
- SPS - How to enable the Spreadsheet Server Ribbon in Microsoft Excel
- Skip to main content
- Skip to search
- Skip to select language
- Sign up for free
- English (US)
503 Service Unavailable
The HyperText Transfer Protocol (HTTP) 503 Service Unavailable server error response code indicates that the server is not ready to handle the request.
Common causes are a server that is down for maintenance or that is overloaded. This response should be used for temporary conditions and the Retry-After HTTP header should, if possible, contain the estimated time for the recovery of the service.
Note: together with this response, a user-friendly page explaining the problem should be sent.
Caching-related headers that are sent along with this response should be taken care of, as a 503 status is often a temporary condition and responses shouldn't usually be cached.
- HTTP Status Code Definitions
- System Center Configuration Manager (Current Branch)
- Remember me Not recommended on shared computers
Forgot your password?
Fixing an evaluation version of SSRS with "HTTP Error 503. The Service is unavailable"
By anyweb , September 14, 2020 in System Center Configuration Manager (Current Branch)
- Reply to this topic
- Start new topic
- Report post
I was writing a blog post about Troubleshooting BitLocker Management in ConfigMgr 2002 Current Branch and one of the things I was trying to do was install the web portals, but I was seeing errors shown below.
I assumed this was because SSRS was not installed or configured but after checking the lab, I could see it was indeed installed and configured. However when I browsed the http://cm01.windowsnoob.lab.local/ReportServer URL in Internet Explorer it produced a HTTP Error 503. The Service is unavailable.
A quick search gave some clues and things to try but in reality the reason it was not working was because:
- SSRS was installed in evaluation mode
- SSRS evaluation had expired
This was revealed in the logs stored at C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\Logfiles
To upgrade the evaluation version you'd normally just need to upgrade the edition of SSRS from Evaluation to Production via change /uninstall in Control Panel, however the way this installation was packaged (WIX bundle) meant that it retained the original download link in a bundled file called state.rsm
and that was looking in the IE cache as you can see in the SSRS installation log files
That path no longer existed. Manually recreating that path and copying the SQLServerReportingServices.exe file to that path did not help, it reported another error.
I could keep trying to hack my way around these errors or fix it once and for all.
Fixing the evaluation version
As this is just a lab I decided to rip SSRS out completely and then add it back.
Note : If you are doing this in production then make sure to backup all your custom reports first and if necessary backup the reporting databases also.
I decided to try the following:
- uninstall reporting from ConfigMgr
- delete the 2 reporting db's in SQL
- uninstall SQL Reporting Services in control panel
- restart server
- reinstall SSRS
- reconfigure SSRS
Keep in mind that unless you want the same problem occurring in 180 days or so, you'll need the key that was used when installing SQL. If this process doesn't pick it up from your installed instance of SQL, you can find that key in the installation media.
Using the product key from DefaultSetup.ini
To find the product key in your installation media , you should know that the PID is more than likely contained within the DefaultSetup.ini file located under Root\X86 or Root\x64 folder. Open that file with notepad and copy the product key for later use.
Let's get started. In ConfigMgr remove the SSRS role.
Confirm that it's removed successfully via the SRSRPSetup.log .
Next, in Sql Server Management studio, find the 2 reporting services databases and remove them, if you are doing this in Production, read my NOTE at the top of this section as deleting the two Reporting databases will result in the following: Reporting services will not work (it's broken already...), all your reports will have been lost (you did back them up didn't you ?), schedules, permissions, etc.
And now they are gone.
Next in Control Panel, locate SQL Server Reporting Services and uninstall it.
Once uninstalled, close the wizard.
restart the ConfigMgr server.
After the server has restarted, reinstall SSRS by launching SQLServerReportingServices.exe available for download here for SQL Server 2017 or here for SQL Server 2019. After downloading it, copy it to a safe location outside of the browsers cache, eg: C:\SSRSSource.
Run the executable and choose Install Reporting Services .
Paste in your SQL License key from the SQL Server media, look in ..\x64\DefaultSetup.ini and your SQL license key will be in there.
Accept the license terms
Install the database engine.
Pick the path and click next, after a while it's completed. Click on Configure Report Server.
Select Connect when prompted. The report server configuration manager wizard will appear, notice how it states the version is Standard (and not evaluation).
In Web Service URL , click Apply .
Note: This is assuming you want to configure SSRS in HTTP mode, if you'd like to use HTTPS mode please review this blog post .
For Database , choose Change Database.
Choose create a new report server database from the options
Decide if you are going to use the current logged on user or a SQL server account to setup this new database
Select the database name.
continue through that wizard until completion. Make sure it's all successful before clicking on Finish.
Next, click on Web Portal , and choose Apply .
And you can configure other options or simply select Exit.
In the ConfigMgr console, add back the reporting services role
Configure the account...
And confirm that it was successfully installed in the SRSPSetup.log.
At this point you can go back into your web browser and confirm that reporting is indeed responding without the initial error.
and via the Reports web portal.
And finally, verify that the reports are present and working in the ConfigMgr console
And that's it ! Once again I started one blog post only to hit an issue that threw me a wobbler. But thanks to that you have this blog post 🙂
Share this post
Link to post, share on other sites.
Md. Ehteshamuddin Khan
My issue has been resolved once I followed the steps, it is really helpful the way of elaboration.
Once again thanks.
Just wanted to say thank you, we ran into the same exact issue and its resolved through these steps!
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
× Pasted as rich text. Paste as plain text instead
Only 75 emoji are allowed.
× Your link has been automatically embedded. Display as a link instead
× Your previous content has been restored. Clear editor
× You cannot paste images directly. Upload or insert images from URL.
- Submit Reply
- Existing user? Sign In
- Online Users
- All Activity
- Create New...
- Shop 'Til You Drop
- Our Picks: The Best Tech Gifts This Year
503 Service Unavailable Error Message: What It Is and How to Fix It
Retry the URL, reboot the router/modem, or just come back later
- Emporia State University
In This Article
Jump to a Section
- Solutions to Try
- Fix 503 Errors on Your Site
- Common Ways the Error Appears
More Ways You Might See a 503 Error
- Extra: Errors Similar to 503 Errors
- Frequently Asked Questions
The 503 Service Unavailable error is an HTTP status code that means a website's server is not available right now. Most of the time, it occurs because the server is too busy or maintenance is being performed on it.
A 503 error message can be customized by the website it appears on or the server software that generates it, so how you might see it vary greatly.
How to Fix the 503 Service Unavailable Error
Since the 503 Service Unavailable error is a server-side error, the problem is usually with the website's server. Your computer may have an issue causing the 503 error, but it's not likely.
Regardless, there are a few things you can try:
Retry the URL from the address bar again by selecting Reload or Refresh , the F5 key, or the Ctrl + R keyboard shortcut.
Even though the 503 Service Unavailable error means there's an error on another computer, the issue is probably only temporary. Sometimes just trying the page again will work.
If the 503 Service Unavailable error message appears while paying for an online purchase, be aware that multiple attempts to check out may end up creating multiple orders and multiple charges. Most payment systems and some credit card companies have protections from this kind of thing, but it's still something you should know.
Restart your router and modem . Then restart your computer or device, especially if you see the Service Unavailable - DNS Failure error.
While the 503 error is still most likely the fault of the website you're visiting, there may be an issue with the DNS server configurations on your router or computer, which a simple restart of both might correct.
If rebooting your equipment didn't correct the 503 DNS Failure error, there might be temporary issues with the DNS servers themselves. In this case, pick new DNS servers from our Free & Public DNS Servers list and update the servers on your computer or router .
Another option is to contact the website directly for help. There's a good chance that the site's administrators already know about the 503 error, but letting them know, or checking the status on the problem, isn't a bad idea.
Most sites have support-based social network accounts, and some even have phone numbers and email addresses.
If the website giving the 503 error is a popular one, and you think it might be down completely, check if the website is down by plugging its URL into a service like Freshping's Is it down tool . An outage on a prominent site will also generate lots of talk on social media.
Come back later. Since the 503 Service Unavailable error is a common error message on trendy websites when a massive increase in traffic by visitors is overwhelming the servers, simply waiting it out is often your best bet. Frankly, this is the most likely "fix" for a 503 error. As more and more visitors leave the website, the chances of a successful page load for you increase.
Fixing 503 Errors on Your Own Site
With so many different web server options out there and even more general reasons why your service might be unavailable , there isn't a straightforward "thing to go do" if your site is giving your users a 503.
That said, there are certainly some places to start looking for a problem and then hopefully a solution.
Start by taking the message literally—has something crashed? Restart running processes and see if that helps.
Beyond that, look at not-so-obvious places where something might have hiccuped. Where applicable, look at connection limits, bandwidth throttling , overall system resources , fail-safes that might have triggered, etc.
In what's very likely a "double-edged sword" for your website, it may be that it's suddenly very, very popular. Getting more traffic than you built your site to handle almost always triggers a 503.
However, the 503 error could also result from a malicious denial of service (DoS) attack. If so, getting into contact with the company hosting your website would be wise to discuss steps that you can take to reduce the likelihood of it happening again or to better prepare for another in the future.
Even an unintentional DoS attack can occur, where a virus on the server is sucking away usable system resources and slowing the server down to the point that it causes a 503 error.
Most Common Ways You Might See the 503 Error
503 Service Unavailable errors can appear in any browser in any operating system , including Windows 10 back through Windows XP, macOS, Linux, etc...even your smartphone or other nontraditional computers. If it has internet access, you could see a 503 in certain situations.
Here are the most common ways you might see the "service unavailable" error:
- 503 Service Unavailable
- 503 Service Temporarily Unavailable
- Http/1.1 Service Unavailable
- HTTP Server Error 503
- Service Unavailable - DNS Failure
- HTTP Error 503
- Error 503 Service Unavailable
- Error 503 Backend fetch failed
The 503 Service Unavailable error displays inside the browser window, just as web pages do.
Sites that use Microsoft IIS may provide more specific information about the cause of a 503 Service Unavailable error by suffixing a number after the 503 , as in HTTP Error 503.2 - Service Unavailable , which means Concurrent request limit exceeded . See More Ways You Might See a 503 Error near the bottom of the page for the whole list.
In Windows applications that inherently access the internet, a 503 error might return with the HTTP_STATUS_SERVICE_UNAVAIL error, and maybe also with a The service is temporarily overloaded message.
Windows Update might also report an HTTP 503 error, but it will display as error code 0x80244022 or with a WU_E_PT_HTTP_STATUS_SERVICE_UNAVAIL message.
Some less common messages include 503 Over Quota and Connection Failed (503) , but the troubleshooting above applies all the same.
If the website that reports the 503 error happens to be running Microsoft's IIS web server software, you might get a more specific error message like one of these:
Errors Like 503 Service Unavailable
The 503 Service Unavailable error is a server-side error. It's very much related to other server-side errors like the 500 Internal Server Error , the 502 Bad Gateway error, and the 504 Gateway Timeout error, among others.
Several client-side HTTP status codes exist, too, like the standard 404 Not Found error, among others.
You can encounter a 503 error pretty much any time you're visiting a website or using an online service. It's sometimes possible to anticipate these errors, such as when a small website suddenly receives an unexpected surge in attention it wasn't built for. However, more often than not it comes down to timing and bad luck whether or not you'll encounter one.
Yes. It can also appear as Varnish Cache Server: Error 503 Service Unavailable or Error 503: Backend Unhealthy or error when calling aws apis. error details - serializationerror: 503 service unavailable . Regardless of how the message appears, the main terms to look out for are 503 and Error .
This probably means that whatever website you've set as Safari's home page default is experiencing trouble. Aside from waiting a bit and trying again, or restarting Safari or your Mac, you can also change Safari's home page to a different URL.
Get the Latest Tech News Delivered Every Day
- 404 Page Not Found Error: What It Is and How to Fix It
- 502 Bad Gateway Error: What It Is and How to Fix It
- How to Fix a 500 Internal Server Error
- 7 Most Common Online Error Codes
- How to Fix a 504 Gateway Timeout Error
- How to Fix a 401 Unauthorized Error
- How to Fix a 408 Request Timeout Error
- How to Fix a 400 Bad Request Error
- What Does a 403 Forbidden Error Mean? How Do You Fix It?
- HTTP Status Codes
- DNS Servers: What Are They and Why Are They Used?
- Hulu Error Codes: What They Are and How to Fix Them
- How to Fix the PS4 'Cannot Connect to the Wi-Fi Network' Error
- Error 524: A Timeout Occurred (What It Is & How to Fix It)
- How to Fix It When Your ChatGPT Login Isn't Working
- The Best Free and Public DNS Servers (November 2023)
By clicking “Accept All Cookies”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts.
Deploy your app quickly and scale as you grow with our Hobby Tier
How to Fix the HTTP Error 503 Service Unavailable
What's the HTTP 503 Service Unavailable Error?
The HTTP 503 Service Unavailable error means that a website can’t be reached at the moment because the server is not ready to handle the request. This could happen because it’s too busy, under maintenance, or something else which requires a deeper analysis.
Running into errors on your site can be intimidating. However, most errors give you some clue as to what caused them, which can make troubleshooting these common issues a lot easier. The 503 error is not as polite, unfortunately, and doesn’t give you much information to go on.
It helps to understand what the most common causes are for the 503 error. After that, you’ll need to be methodical when it comes to troubleshooting the error, which means following several steps in order to locate the root cause.
In this article, we’ll cover what the 503 error is and how it typically manifests. Then we’ll guide you through six steps in order to troubleshoot it. Let’s get to work!
Check Out Our Video Guide To Fixing Different Types of 500 Errors
What Is an HTTP Error 503?
The Internet Engineering Task Force (IETF) defines the 503 Service Unavailable as:
The 503 (Service Unavailable) status code indicates that the server is currently unable to handle the request due to a temporary overload or scheduled maintenance, which will likely be alleviated after some delay. The server MAY send a Retry-After header field to suggest an appropriate amount of time for the client to wait before retrying the request.
When you encounter the 503 error, it means that the server in question is unavailable. That could be because it’s too busy, for example, or it’s under maintenance. Unlike other similar error codes, 503 signifies that your website is online and running, but can’t be reached at the present moment.
What’s so vexing about this particular error is that it barely gives you any information to go on. Most of the time, it just shows up with a “ Service temporarily unavailable ” message. That’s the equivalent of calling a restaurant via phone, only to have them tell you that they’re closed but refuse to let you know when they’ll be open again.
If you’re lucky, the 503 error code will have occurred because your website is under maintenance. WordPress very briefly sets your site to maintenance mode when you’re updating a plugin, a theme, or the core software:
Usually, this timeout is so brief that no one will notice it. However, in those cases where the 503 error persists, you’ll have a bigger problem to deal with. After all, not only will users be unable to visit your site, but you’ll lose access to your WordPress admin area as well. That means you can’t update your site in any way, and in order to troubleshoot it, you’ll need to dig into its files.
503 Error Variations
The 503 error can show up in a lot of ways. However, almost every variation comes accompanied by that 503 code, making it easy to identify.
Here are some of the variations you might encounter, depending on your server configuration and browser:
- 503 Service Unavailable
- 503 Service Temporarily Unavailable
- HTTP Server Error 503
- HTTP Error 503
- Error 503 Service Unavailable
- The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Whatever the code you run into might look like, it means you need to get to work fast before it affects your users negatively.
What Causes an HTTP Error 503?
These are the most common reasons why a server is temporarily unable to handle a request:
- There is a high number of requests being sent to the server, exhausting all the available resources.
- The server is experiencing technical issues or maintenance work.
- The server could be under a Denial of Service (DDoS) attack.
There are also other technical issues triggering the 503 error, like problems with your plugins or theme. More on that below.
How to Fix the 503 Error?
Since you often can’t be sure what caused the 503 error in any given situation, you’ll need to go about troubleshooting it methodically. The following six sections each cover a potential fix, aimed at resolving the different potential root causes.
After each step, take a moment to return to your website and see if the 503 error is gone. If it is, you’ve successfully fixed the issue. If not, continue on to the next step in the process.
1. Temporarily Deactivate Your Plugins
One of the most common causes of the 503 error in WordPress is plugin compatibility issues. To determine if that’s what’s happening, you’ll need to disable all of your site’s plugins.
Since the 503 error prevents you from accessing the admin area, you’ll need to use an FTP client for this step. If you don’t have one set up, we recommend FileZilla .
Once your FTP client is ready, connect to your website through it and navigate to your root folder. In case you can’t find it, it’s usually called public_html, html, public, www, or your site’s name. If you’re a Kinsta client, it’s your public folder.
Open that folder, and navigate to the wp-content directory. Inside, you’ll see a folder called plugins , which contains individual subdirectories for each of the plugins installed on your site (both active and inactive).
What you’re going to do now is right-click on the plugins folder, and rename it to something else. We recommend plugins.old or plugins.deactivated , so you can easily recognize it later.
WordPress will now not be able to find any of your plugins. When that happens, it will automatically disable those plugins.
Now, try accessing your dashboard. If the 503 error is gone, then you can assume that one of your plugins was the culprit. All you have to do is figure out which one was at fault.
Return to the wp-content directory, and rename your original plugins folder correctly. Then, you’ll need to disable each of your plugins one by one, until you find the culprit.
To do this, open the wp-content/plugins directory. Inside, you’ll find one folder for each of your plugins. The process you’re going to follow is much the same as before:
- Start with the first folder, and rename it to anything you like.
- Check your website to see if the error is gone.
- If it isn’t, return the plugin folder from the previous step to its original name.
- Move on to the next plugin on your list, repeating the above steps.
This process can take a while if you have a lot of plugins, but it’s vital to check each plugin in turn. If at any point you identify the plugin that’s causing the error, you can uninstall it or replace it with another tool.
If you make it to the end of these steps without finding a solution, you can move on to the next stage of troubleshooting.
2. Deactivate Your Website Theme
Now that you’ve ruled out your plugins as the cause of the 503 error, it’s time to do the same with your active theme. In fact, your theme could also be creating compatibility issues.
Unfortunately, the process doesn’t work the same as above. WordPress won’t revert to the default theme if simply rename the theme folder, you would end up with an error like “The theme directory “theme name” does not exist.” Or if you try to rename the entire theme directory folder, you end up with “ERROR: The themes directory is either empty or doesn’t exist. Please check your installation.”
Therefore, you need to access your WordPress database by logging into phpMyAdmin . If you’re a Kinsta client, this can be found within the “Info” section of the MyKinsta dashboard.
Once in phpMyAdmin, click into the “wp_options” table, then click on the “Search” tab. You will want to search under the “option_name” for template .
Under the “option_value” column you will see the current name of your theme. Change this to one of the default themes, such as “twentynineteen.”
Check your website again to see if this has fixed the error. If it did, it simply means it’s a problem with your website theme and you might want to try reinstalling it or reverting to your most recent backup.
3. Temporarily Disable Your Content Delivery Network (CDN)
Sometimes, the 503 error will show up not because of a problem on your website, but because of your Content Delivery Network (CDN). If you’re using a CDN , a quick way to figure out if that’s the case is to temporarily disable it.
Every CDN should include some feature that enables you to pause its services. If you’re on Kinsta, you can disable your Kinsta CDN by navigating to CDN → “Disable CDN” inside your MyKinsta dashboard :
The process you need to follow may be different depending on which CDN you’re using. Cloudflare has also been known to cause 503 errors sometimes. If you can’t find the option to pause yours, check out your service’s knowledge base, which will usually contain detailed instructions.
If you don’t use a CDN or find that pausing your service doesn’t help with your issue, there are still a few more fixes to try. Do remember to reactivate your CDN before moving on.
4. Limit the WordPress ‘Heartbeat’ API
The WordPress Heartbeat is an API built into WordPress, which the platform uses for auto-saving content, showing you plugin notifications, letting you know when someone else is working on a post you’re trying to access, and more.
Just like a regular heartbeat, the API works in the background with a high frequency so that it doesn’t miss anything. As you might imagine, this API consumes server resources. Usually, that’s not a problem but in some cases, it may lead to a 503 error if your server can’t handle the load.
The quickest way to determine if the Heartbeat API is at the center of your problems is to temporarily disable it. To do that, connect to your WordPress website via FTP once more, and then open your current themes folder and look for the functions.php file within:
Right-click on the file and select the View/Edit option, which will open it using your local text editor. Once it’s open, you’ll need to add the following code snippet within:
Those three lines of code tell WordPress to disable the Heartbeat API. Save the changes to the functions.php file, close it, and try to access your website again.
If the 503 error is gone, you’ll know that the API was the problem. Disabling it altogether removes a lot of useful functionality, however. Instead, we recommend that you ‘slow down’ the Heartbeat, so that it doesn’t cause problems.
The easiest way to do that is by installing the Heartbeat Control plugin . Activate the plugin and navigate to the Settings > Heartbeat Control section. Look for the Modify Heartbeat options, and drop the frequency to the lowest possible number:
Save the changes to your settings and return to the functions.php file you tweaked a while back. For the above changes to work, you’ll need to remove the string of code you added before and save your changes to the file.
At this stage, the 503 error should be gone if the Heartbeat API was the problem. If it isn’t, then it’s time to try something different.
5. Increase Your Server’s Resources
If the 503 error is still occurring despite all your attempts to fix it so far, then there’s a good chance the problem might be due to a lack of server resources. That is to say, you’ll need to upgrade your hosting plan to see if that fixes the issue. This is especially true if you’re using cheap WordPress hosting , as they tend to throttle resources.
We don’t do this at Kinsta. We offer great Managed WordPress Hosting (as well as Application Hosting and Database Hosting ).
Upgrading your plan is a big decision, however. The smart move is to first contact your web hosting support service and discuss the 503 error with them, as well as the steps you’ve taken so far to try and solve it. The support team should be able to help you work out the cause and advise you on whether you need to upgrade your plan or not.
6. Review Your Logs and Enable WP_DEBUG
You should also take advantage of your error logs . If you’re a Kinsta client, you can easily see errors in the log viewer and enable WordPress debug mode in the MyKinsta dashboard. This can help you quickly narrow down the issue, especially if it’s resulting from a plugin on your site.
If your host doesn’t have a logging tool, you can also add the following code to your wp-config.php file to enable logging:
The logs are typically located in the /wp-content directory. Inside it, look for a file called debug.log and open it up.
Others, like here at Kinsta might have a dedicated folder called “logs”.
Interpreting your debug log can be a bit intimidating but it’s not as hard to read as you might imagine. In a nutshell, the log contains each error that pops up on your site in chronological order. It shows which file caused each error, as well as which specific lines of code were involved.
Beware: you’re not going to find direct references to the 503 error within your log. Even so, if all else fails, it can point you in the right direction by showing you what files are causing problems. That way, you’ll know where to focus your efforts next. As we mentioned in the previous step, now is a good time to get in touch with your hosting provider if you need further assistance resolving this error.
You can also check the log files in Apache and Nginx , which are commonly located here:
- Apache: /var/log/apache2/error.log
- Nginx: /var/log/nginx/error.log
To learn more, please check out our web server showdown: Nginx vs Apache .
If you’re a Kinsta client you can also take advantage of our analytics tool to get a breakdown of the total number of 503 errors and see how often and when they are occurring. This can help you troubleshoot if this is an ongoing issue, or perhaps something that has resolved itself.
If the 503 error is displaying because of a fatal PHP error, you can also try enabling PHP error reporting. Simply add the following code to the file throwing the error. Typically you can narrow down the file in the console tab of Google Chrome DevTools.
And you might need to also modify your php.ini file with the following:
If you’re lucky, the 503 error will only show up when you put your website into maintenance mode. However, if it appears without warning, then you’ll have to roll up your sleeves and do some troubleshooting.
To get at the root cause of the 503 error, you’ll need to follow these steps to fix it:
- Temporarily Deactivate Your Plugins.
- Deactivate Your Website Theme.
- Temporarily Disable Your Content Delivery Network (CDN).
- Limit the WordPress ‘Heartbeat’ API.
- Increase Your Server’s Resources.
- Review Your Logs and Enable WP_DEBUG.
Have you ever run into the HTTP 503 error? Share your experiences with us in the comments section below!
Head of Content at Kinsta and Content Marketing Consultant for WordPress plugin developers. Connect with Matteo on Twitter .
Related Articles and Topics
How to Fix a 403 Forbidden Error on Your Site
How to fix error 404 not found on your site.
Thank you for the article. Over the past 3 months, the 503 error has been on my site 5 times. Now I think that I need to change hosting in order to avoid problems in the future.
Leave a Reply Cancel reply
You also agree to receive information from Kinsta related to our services, events, and promotions. You may unsubscribe at any time by following the instructions in the communications received.
- Log In Sign Up Members get daily listing updates
- Redfin Premier
- Sell My Home
- List My Home for Rent
- Saved Searches
- Why Sell with Redfin?
- Owner Dashboard
- Open House Schedule
- Be a Redfin Agent
- Notification Settings
- Property details
- Sale & tax history
- Public Facts
506 Samara St , Apex , NC 27502
About this home
Stunning 4 Bed/2.5 Bath home in the heart of Apex! Just minutes from downtown Apex which has restaurants, bars, and shops. Very easy access to the Highway. No grass in the backyard which means low maintenance, with the added benefit of lots of shade from the many trees! Natural gas, city water and sewer. Very low HOA. All of the bedrooms are upstairs, all of which are a good size. Great for entertainers due to the large back porch which has been refreshed recently. * OFFER DEADLINE : Monday 8/23 at 10am *
Redfin Estimate for 506 Samara St
1 year newer
6 years older
Est. $2,807 per month, based on comparable rentals
27502 real estate market
Homes go pending in 27 days
Electricity and solar
View estimated energy costs and solar savings for this home
View Internet plans and providers available for this home
From agents who toured
Property details for 506 samara st.
- # of Garage Spaces: 2
- Garage Floor: Main
- Garage Dimensions: 19.7x23.4
- # of Covered Spaces: 2
- Parking Features: Attached, Garage
- Has Attached Garage
- # of Bathrooms (Full): 2
- # of Bathrooms (Half): 1
- Master Bedroom Width: 16.9
- Master Bedroom Level: Second
- Master Bedroom Length: 12.6
- Master Bedroom Area: 212.939999
- Bedroom 2 Level: Second
- Bedroom 2 Area: 109.2
- Bedroom 2 Width: 10.5
- Bedroom 2 Length: 10.4
- Bedroom 3 Level: Second
- Bedroom 3 Area: 110.24
- Bedroom 3 Width: 10.6
- Bedroom 3 Length: 10.4
- Bedroom 4 Level: Second
- Bedroom 4 Area: 155.609999
- Bedroom 4 Width: 13.3
- Bedroom 4 Length: 11.7
- Laundry Features: 2nd Floor, Laundry Room
- Interior Features: Entrance Foyer, Great Room, Walk In Pantry, Pantry, Walk-In Closet(s)
- # of Fireplaces (Total): 1
- Fireplace Features: Great Room
- Has Fireplace
- Appliances: Gas Water Heater
- Flooring: Carpet
- # of Rooms (Total): 7
- Living Room Width: 16.7
- Living Room Length: 12.6
- Living Room Level: Main
- Living Room Area: 210.42
- Kitchen Width: 15.1
- Kitchen Length: 10.5
- Kitchen Level: Main
- Kitchen Area: 158.549999
- Breakfast Room Dimensions: 8.1x10.7
- Breakfast Room Floor: Main
- Dining Room Width: 10.5
- Dining Room Length: 10.3
- Dining Room Level: Main
- Dining Room Area: 108.15
- Dining Room Features: Breakfast Room,Separate Dining Room
- Utility Room Dimensions: 6x6.4
- Utility Room Floor: Second
- Other Area Above Grade: 0
- Total Other Area SqFt: 0
- Construction Materials: Masonite
- Patio And Porch Features: Deck
- Porch Dimensions: 5x6
- Porch Floor: Main
- Deck Dimensions: 16x28
- Deck Floor: Main
- Roof: Shingle
- Levels: Two
- StructureType: House, Site Built
- Entry Location: Main Floor
- Above Grade Finished Area: 1916
- Below Grade Finished Area: 0
- Lot Size Dimensions: 64 x 217 x 110 x 162
- Lot Features: Landscaped
- Annual Tax Amount: $3,190
- Buyer Financing: Conventional
- Gas: Natural Gas
- Heating: Forced Air, Natural Gas
- Has heating
- Cooling: Central Air
- Has Cooling
- Association Fee: 230
- Association Fee Frequency: Annually
- Maint Com. Area, Storm Water Maintenance
- HOA 1 Fees Required
- Elementary School: Wake - Apex
- Middle Or Junior School: Wake - Apex
- High School: Wake - Apex
- Inside City: Yes
- City Limits Of: Apex
- CountyOrParish: Wake
- Directions: From Vintage Grove Ln, left onto Samara St.
- Buyer Agency Compensation: 2.5
- Property Leased: No
Sale and tax history for 506 Samara St
- Sale History
- Tax History
Public facts and zoning for 506 Samara St
HDSF-CZ | Permitted: Single-Family, Two-Family, Multi-Family, Commercial, Industrial
Cost of home ownership
$2,283 per month
Public, PreK-5 • Serves this home • 1.6mi
Public, 6-8 • Serves this home • 1.0mi
Public, 9-12 • Serves this home • 1.0mi
Around this home
Transportation near 506 samara st, walk score ®, bike score ®, climate risks.
About climate risks
Most homes have some risk of natural disasters, and may be impacted by climate change due to rising temperatures and sea levels.
Flood Factor - Minimal
Unlikely to flood in next 30 years
Fire Factor - Minor
0.00% chance of being in a wildfire in next 30 years
Heat Factor - Major
7 days above 104° expected this year, 17 days in 30 years
Wind Factor - Major
80% chance of strong winds in next 30 years
Is this your home?
Track this home's value and nearby sales activity
Nearby similar homes
Nearby recently sold homes
Home values near 506 Samara St
More real estate resources.
- New Listings in 27502
- Nearby Cities
- Popular Searches
Frequently asked questions for 506 Samara St
What is 506 samara st, how many photos are available for this home, how much is this home worth, when was this home built and last sold, what is the rental estimate for this home, how competitive is the market for this home, what comparable homes are near this home, what’s the full address of this home, what's the housing market like in 27502.
Find homes faster
Copyright: © 2023 Redfin. All rights reserved.
Do not sell or share my personal information .
REDFIN and all REDFIN variants, TITLE FORWARD, WALK SCORE, and the R logos, are trademarks of Redfin Corporation, registered or pending in the USPTO.
California DRE #01521930
Redfin is licensed to do business in New York as Redfin Real Estate. NY Standard Operating Procedures
New Mexico Real Estate Licenses
TREC: Info About Brokerage Services , Consumer Protection Notice
If you are using a screen reader, or having trouble reading this website, please call Redfin Customer Support for help at 1-844-759-7732 .
Please verify you are a human
Click "I am not a robot" to continue