Secure websites transfer the data in an encrypted format. This ensures that an attacker who sniffs the packages from the network cannot read the data. Securing your website by using an SSL certificate is the first step towards the right direction. Browsers take this approach to the next level by making sure that all resources use HTTPS. This is where you may come across this error: “Mixed Content: The page was loaded over HTTPS, but requested an insecure font“.
This error doesn’t show up to the end users right away. It stays in the “Console” tab of your browser’s “Developer Tools” window. The website shows different symptoms when this error occurs in the background.
Symptoms of Mixed Content (Insecure Font) Issue
When there is a “Mixed Content (Insecure Font)” issue:
Your website may not use the font you selected
Some icons may not appear
There might be CSS adjustment issues
In order to figure out the underlying issue, turn on “Developer Tools” and visit the website again. The “Console” tab should give the detailed error message:
Mixed Content: The page at ” was loaded over HTTPS, but requested an insecure font ”. This request has been blocked; the content must be served over HTTPS.
Web servers display an HTTP status code such as 404 (Page Not Found) or 500 (Internal Server Error) when there is an issue accessing the website. Some issues are easy to fix (Ex. just upload the file if you get 404 error). Some issue are more challenging to cope with. WordPress 500 Internal Server Error is one of them.
The first step is to make sure what status code you receive. In most cases, the browser clearly indicates the HTTP 500 error. However, you may see only a white blank page in some situations. I would recommend visiting the URL via different browsers. Browsers have different error pages and formats.
Are you seeing “Error establishing a database connection” error while accessing your WordPress blog? Check this post out for the solution.
Check server logs
Even if you see 500 error in the browser, I would recommend connecting to the server and checking IIS or Apache logs. The logs will show you HTTP status code as well as the sub-status code such us 500.11 or 500.19. The sub-status code provides a valuable information about the issue. Check this post to see the meaning of each sub-status code.
If you are using a hosting provider such as GoDaddy or RackSpace, you can obtain the server logs in your dashboard. Most of the time, these logs are available via a few clicks. Therefore, you don’t need to contact the customer support.
Here are the most common causes and the solutions for the WordPress 500 error:
Misconfiguration in .htaccess file
Solution: Simply rename this file. If the issue goes away it’s better to create a brand-new .htaccess file. Go to your blog’s dashboard. Click “Settings > Permalinks”. Click “Save Changes” (You don’t need to make any changes).
PHP memory limit
Solution: Create a text file and name it php.ini. Add memory=64MB line to this file and upload it to your server.
Windows hosting settings. This issue happens if you move WordPress files from a Windows server to Linux server
Solution: Remove user.ini and any other Windows server related files from the root folder of your website
If you are still seeing a white blank page or receiving WordPress 500 Internal Server Error, double check the information in your wp-config.php file. In this file, change the value of WP_DEBUG parameter to true to see more details about the issue.
In conclusion, HTTP 500 error may mean there is a damaged file, insufficient file permission or wrong configuration in your WordPress blog or hosting account. If you can’t solve the problem no matter what you do, please reach out to your server admins or hosting provider.
If you have any questions, please drop a comment! I try to answer questions as much as I can.
WordPress is the most popular content management system (CMS) by far ahead of its competitors. One of the reasons why it is very popular is that the 5-minute fast installation process. Here is the question: It is fast but is it complete? After the installation for a hobby blog today, I have received this error message while trying to upload an image: “Is its parent directory writable by the server?”.
This error message tells us that there is a configuration setting missed during the installation. Apparently, uploading files and connecting the database don’t always enough for your blog to start running. There might be additional steps to go through.
Unable to create directory wp-content/uploads/2019/01. Is its parent directory writable by the server?
Fix “Is its parent directory writable by the server?” error
As the name implies, this is an issue of the folder or folder permissions. In order to fix it:
Make sure there is an uploads folder in wp-content
Make sure the site owner has Write permission on the uploads folder
Setting folder permissions by using an FTP client could get tricky. In my case, I have received this error message while trying to change permissions:
Response: 500 ‘SITE’: command not understood
This error message may refer to several types of errors. In my case, it was because of trying to change folder permissions via FTP client for a site hosted in a Windows server. As soon as I made the same change through the administration panel of my hosting provider, the error message went away.
The way how you set folder permissions on an administration panel depends on your hosting provider. For GoDaddy, please use these instructions.
Are you seeing “Error establishing a database connection” message when you install WordPress? Check this post out.