Don’t panic, we’ve all been there. Just editing a page or updating a wordpress plugin – then suddenly wham – a white screen is delivered in front of your eyes – HTTP 500 Internal Server Error 500. Most likely you have probably seen this error whilst browsing before – thankfully it is a common error that is fairly easy to troubleshoot regardless of your wordpress skill level!
The HTTP 500 Server Error is not something that can happen to any website and framework and isn’t something that just effects wordpress websites. Even though it is the most common it doesn’t give much away in regards to the issue. [See our post next week on Enabling your WordPress Error Log].
Usually this error can be drilled down to a few things:
plugins or theme conflictions
php memory limit
a corrupt .htaaccess file
This can be found by using an FTP client such as Filezilla
You will need to go to your Public_Html Directory into your wordpress directory and scout for a file named .htaaccess
Rename your file by clicking like you would when you rename a file through your computer and name is following the same structure – .htaccess_trash
Once done it will rebuild a fresh .htaaccess – if you can now refresh and load your site – well done you fixed it (now go to Settings>Permalinks and resave)
If not… continue…
Next up lets check your PHP Memory limit see if the website is timing out because of the limit and processes on site. Usually this will only flag the 500 error if you have done something like upload an image. If its down to Memory limit is usually only really effects the back end of the website due to this being the place you are updating, changing, uploading and configuring.
Connect to your FTP again
Open a new file on Notepad or any text file program and save as php.ini
Paste in the following:
memory=128MB
Upload by dropping and dragging it into your wp-admin folder. (This is in your Public_html folder and located in your wordpress directory)
Still not working?… don’t give up on us now!
If you have come this far, it is more likely down to a plugin extension or a theme function. To troubleshoot, the best place to start is to deactivate all your plugins. Naturally this has to also be done through your FTP.
Open up your FTP connect to your website
Open the WP-Content Folder (this is where your plugins are kept)
Find your Plugins folder
Rename this folder to something such as plugins.old
Refresh the website and clear cache.
If you can now see your website this issue is related to a plugin confliction. You will need to login to your wordpress website and deactivate each plugin one by one. This way you can work out which plugin is causing the internal server error.
Once you are logged in to wp-admin – go back to your ftp rename your plugins file back to ‘plugins’ as it was before. When the file name is back as it was, you can start troubleshooting each plugin one by one until you find the cause.
Sadly if you have got to this point and are still none the wiser in regards to the wordpress 500 internal server error its time to speak to your hosting company or pop us a message or support ticket here
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-advertisement | 1 year | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Advertisement". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
laravel_session | laravel uses laravel_session to identify a session instance for a user, this can be changed | |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
XSRF-TOKEN | 2 hours | The cookie is set by Wix website building platform on Wix website. The cookie is used for security purposes. |
__cfduid | 1 month | The cookie is used by cdn services like CloudFare to identify individual clients behind a shared IP address and apply security settings on a per-client basis. It does not correspond to any user ID in the web application and does not store any personally identifiable information. |
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Cookie | Duration | Description |
---|---|---|
YSC | session | This cookies is set by Youtube and is used to track the views of embedded videos. |
_gat | 1 minute | This cookies is installed by Google Universal Analytics to throttle the request rate to limit the colllection of data on high traffic sites. |
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Cookie | Duration | Description |
---|---|---|
_ga | 2 years | This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors. |
_gid | 1 day | This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form. |
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Cookie | Duration | Description |
---|---|---|
IDE | 1 year 24 days | Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile. |
test_cookie | 15 minutes | This cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies. |
VISITOR_INFO1_LIVE | 5 months 27 days | This cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website. |
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
Cookie | Duration | Description |
---|---|---|
CONSENT | 16 years 9 months 6 days 9 hours 9 minutes | No description |