Category: Blog

Several errors can occur when trying to add SSL with your WordPress website. In this article, you will learn how you can fix these errors.

NET:ERR_CERT_INVALID Error

If you get this error, it means the SSL certificate may be expired or issued to a different domain or subdomain. Also, the browser may be facing issues trying to recognize its authority. To fix this error, you can reinstall the SSL certificate.

Mixed Content Errors

Mixed Content Errors are caused by the elements, like scripts or images, not being loaded via secured HTTP protocol. You can fix this in two ways; first is by using a plugin. The second way is by fixing the issue manually.

Fix Using a Plugin

Get the Really Simple SSL plugin from the WordPress repository. After installation and activation, go to Settings > SSL to review plugin settings. The plugin will automatically fix the errors.

Fix it Manually

First, make sure you are using the HTTPS protocol in your WordPress website settings. Go to the general settings of your website to change HTTP to HTTPS.

Once this is done, go through your website manually to check old HTTP URLs in your database and replace with the new HTTPS URLs. An easy and fast way of doing this is by installing the Better Search Replace plugin. Activate the plugin, go to Settings > Tools > Better Search Replace. Then, add the current HTTP website URL in the Search field. Afterwards, add the website URL with HTTPS in the Replace field.

Fixing the Too Many Redirects Errors

To fix this error, access the wp-config.php file and put the following code.

define(‘FORCE_SSL_ADMIN’, true);

However, in some cases, this setting can actually lead to many more redirect errors. In such case, add the following code to your wp-config.php file:

define(‘FORCE_SSL_ADMIN’, true);
//in some setups HTTP_X_FORWARDED_PROTO might contain
//a comma-separated list e.g. http,https
//so check for https existence
if (strpos($_SERVER[‘HTTP_X_FORWARDED_PROTO’], ‘https’) !== false)
$_SERVER[‘HTTPS’]=’on’;

Fix HTTP to HTTPS Redirect

You can fix this error can accessing your .htaccess file and adding the code to it.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
</IfModule>

Conclusion

Try the solutions discussed above and you see your WordPress website up and running, again.

Have you faced an issue with WordPress not sending emails properly or at all? You are in the right place at the right time, as this article will show you how you get email up and running on your WordPress website.

Test Email on your Server

First, run a test on your WordPress site with a free Email Check plugin provided by WordPress itself. By running this test, you will know if your WordPress installation and the server can send emails. After installing the plugin, go the Tools menu under your WordPress dashboard and click Check Email. Enter an email address and click Send test email.

Check your email to see if you get the test the email. The subject of the email will be “Test email from https://yourdomain.com.” You should also check your junk or spam mail folder. If you find the email, then the issue of emails not sent in the past is probably due to misconfiguration or an incompatibility. You can check your WordPress mail settings or contact your plugin developer for help.

Use SMTP to Send your Emails

Here is another way to resolve the email issue in WordPress. There are several SMTP providers that you can choose from; they include Gmail, Mailgun, SendGrid, WPforms, etc. All you need to do is to download the SMTP plugin of any of these providers from the WordPress repository.

To install the plugin, go to Add New Plugin, click the upload tab, browse for the plugin file, click Install Now and hit the activate button.

Using Gmail SMTP

For Gmail SMTP, you need to authorize your WordPress installation to use Google’s servers. To do this, you have to create a set of secure credentials. Visit console.developers.google.com, log in to your Gmail account, Click My Project, and click the Add (+)to create a new project. In the dashboard of the new project, click Enable APIs and Services.

Click on Gmail API under G Suite APIs. On the next screen, click Enable.

Next, click on Credentials on the left-hand side and under Create credentials, choose OAuth client ID. Then, click Configure consent screen.

Afterwards, input your email address, a product name, and a privacy policy URL. On the next screen, choose web application. Enter a name, paste the Authorized JavaScript origins URL, and the Authorized redirect URIs from the Gmail SMTP wizard on WordPress. Then click Save.

Once you do this, you will get your client ID and client secret. Copy and paste them into the fields on the Gmail SMTP wizard in on WordPress. Click Next and then, Finish. That’s all.

On some occasions, you or your users may experience WordPress login redirect loop in which you are redirected back to the login screen after logging in. This prevents you from accessing the admin panel of your website. Therefore, you are unable to manage your site or create new content. Testup is here with three methods you can use to fix this issue.

Clear Browser Cache and Cookies

If your browser’s cache and cookies hold onto to outdated information and use old WordPress files, it can lead to WordPress login redirect loop. To clear your browser caches and cookies, take the following steps:

• On Google Chrome, click the three dots at the top-right corner. Select More tools and click Clear browsing data.

• On Mozilla Firefox, click the three horizontal lines at the top-right corner. Go to Preferences, click Privacy and Security. Navigate to Cookies and Site Data and select Clear Data. Mark the options Cookies and Site Data as well as Cached Web Content; then, click Clear.

• On Safari, go to Preferences, click on Privacy. Then, select Remove All Website Data and click Remove Now.
• On Microsoft Edge, click the three dots at the top right corner and select History. Select Clear History; tick the options Cached data and files as well as Cookies and saved website data. After that, click Clear.

Restore Default .htaccess file

If you still see the login redirect loop after clearing browser cache and cookies, then you can restore the default .htaccess file. To do this, access the WordPress root folder through an FTP or a File Manager. Locate the .htaccess file and delete it.

Deactivate Themes and Plugins

WordPress login redirect loop can also be caused by conflicting or corrupt plugins or themes. To deactivate your WordPress plugins, access the websites’ wp-content directory through an FTP or a file manager. Then, rename the plugin folder to deactivate all plugins. To deactivate a theme, find the themes’ folder in your wp-content directory and rename the folder.

What can be more frustrating than a website working perfectly seconds ago displaying 500 Internal Server Error? If you are at this crossroad, this article will explain the steps you can take to fix the error. But before you start, it’s good to make a complete backup of your site. If you are ready, here we go!

Deactivate all Plugins and Themes

Go to your dashboard and deactivate all your plugins. Check the website again; if it loads without internal server error, it means the issue was with one of the plugins.  Switch them one by one to know the exact plugin that caused the error. Also, you can switch to the default theme. If your site loads without an error, then the issue was with the theme.

Turn on Debugging

Another way to get rid of the error is to turn on debugging. You can do this by editing your site’s wp-config.php file. Access the file and search for WP_DEBUG. If you find it, then, set it to “true” as shown below. If you don’t find it, write it yourself. Either way, you should have the line shown below.

define( "WP_DEBUG", true );

Check your .htaccess File

Use your FTP to access .htaccess file in your WordPress root folder. Create a back up of the file and then delete the original file. Check if your website is back without error. If it is, then, the .htaccess file has issues. Go through it line by line to get the offending line. You may have to delete the line.

Other Options

If all the solutions discussed above did not bring the website back live. You can try other options like increasing your WordPress memory limit, clearing your browser cache, checking your server logs, or reinstalling your WordPress core.