Blog
- Home
- Blog
WordPress error "Your Connection Is Not Private" - Fix it Now ?
As a result of the SSL connection, sensitive information is protected from being stolen while being transferred between the server and the browser, which is one step in hardening your WordPress security
"Your Connection Is Not Private Error" message means that Google Chrome is preventing you from visiting your site because it is untrusted.
Ultimately, the chrome browser prevents you from gaining access to your website because the SSL certificates cannot be validated.
Typically, the "connection is not private" error in google chrome originates from issues from the side of the client, or from problems with the site's certificate.
To Fix Your Connection Is Not Private WordPress Error:
1. Reload the page
2. Check your network connection
3. Set time and date on your computer
4. Try browser's incognito mode
5. Clear your Browser Cookies, Cache, and History
6. Disable Antivirus Temporarily
7. Update your Operating System
8. Restart your Computer
Rebooting your device will help clear out the temporary cache.
This could surely very well fix your issue.
Prestashop parse error – How to fix the syntax error ?
This article covers ways to resolve Prestashop parse error.
Basically, Prestashop parse error happens when we install Prestashop 1.7 or above or accessing the admin panel of the store.
To fix this error:
1. You can start with emptying your cache by deleting the /var/cache directory.
If that doesn't work copy lines 28-30 from another shop and save it.
2. Also you can try to remove the following:
# php -- BEGIN cPanel-generated handler, do not edit
# Set the “ea-php72” package as the default “PHP” programming language.
<IfModule mime_module>
AddHandler application/x-httpd-ea-php72 .php .php7 .phtml
</IfModule>
# php -- END cPanel-generated handler, do not edit
From end of .htaccess.
Just to be sure if that is not source of issues.
Move Exchange Mailboxes to Another Database – How to perform it ?
This article covers how to move Exchange Mailboxes to Another Database.
Exchange administrator can move user mailboxes in the Active Directory forest from one database to another between Exchange servers, or between mailbox databases on the same server through the Exchange Admin Center web interface or PowerShell CLI.
To move the user or resource mailbox from one database to another, you need to create a move request (if migration occurs within the same Active Directory forest, this is called a local move request; if you want to move a mailbox between AD forests — this is a remote move request).
To move the user mailbox the New-MoveRequest cmdlet is used.
The following two services process your move request to move mailboxes:
1. Exchange Mailbox Replication service (MRS)
2. Exchange Mailbox Replication Proxy
How to Create local move requests ?
You can create local move requests for:
1. A single mailbox.
2. Multiple mailboxes (also known as a batch move request).
3. Multiple mailboxes that you specify in a comma-separated value (CSV) file (also known as a migration batch).
Cloudflare 502 error - Fix it Now ?
This article covers methods to resolve Cloudflare 502 error. Basically, the Cloudflare 502 error triggers when the origin web server responds with a standard HTTP 502 bad gateway or 504 gateway timeout error.
This happens due to firewall restrictions and server resource issues.
Cause of 502 Bad Gateway Errors:
1. Domain name not resolvable
The domain name is not pointing to the correct IP or it does not point to any IP this problem may happen. Also, DNS propagation could take some time to make changes in DNS setting. It may take 24 to 48 hours to make reflect which is dependent upon the TTL defined per record on the DNS.
2. server down
The origin server is not reachable, this may due to the server is down for some reason or there is no communication to the server given.
3. Firewall blocks
A firewall interrupts the communication between the edge servers and the origin server. This may be caused by security plugins of your CMS.
As a part of DDOS protection and mitigation process or due to some strict firewall rules servers can be blocked from accessing the original server.
Nginx upstream timed out error - Fix it Now ?
This article covers methods to resolve Nginx upstream timed out error. Basically, this error happens as a result of server resource usage and software timeouts.
A possible issue here could be that PHP is using too much RAM and the PHP FPM process gets killed.
Therefore, do the following to fix this nginx error:
1. Make sure that there is enough RAM on the server, to check that you could use the top, htop or free -m commands.
2. Make sure that the PHP memory limit is not too high compared to the actual available memory on the Droplet.
For example if you have 1GB of RAM available your PHP memory limit should not be more than 64MB otherwise only a few processes could consume all of your memory.
3. Optimize your website by installing a good caching plugin, that way you would reduce the overall resource usage on the server.
4. Delete any plugins that are not being used. Generally speaking, it is always recommended to try and keep the number of your plugins as low as possible.
5. Consider using a CDN like Cloudflare, that way it would offload some of the heavy liftings from your Droplet.
WordPress error "Installation failed, could not create directory" - Fix it Now ?
This article covers methods to fix WordPress error "Installation failed, could not create directory". Basically, this WordPress error happens when there exist insufficient disk space, incorrect folder permission and so on.
Your WordPress site's plugins and themes provide important functionality for you and your users.
Encountering an error when attempting to install or update one can throw a wrench in your plans and slow down your progress.
To determine if a file permissions issue is causing a plugin or theme installation error on your site, you can use the Site Health tool or check out your server's error log.
After that, resetting your permissions using FTP should only take a few minutes.
