WordPress and .htaccess files

Content

The use of an .htaccess file is not possible, because it is incompatible with our NGINX servers.

.htaccess files (and more broadly, files beginning with a dot) are indeed used on Apache, LiteSpeed and other servers. But on a NGINX server, there are other alternatives.

What is an .htaccess file?

This is a special file (starting with a dot) in which you can add specific directives like. You can read more about this article.

How to do it?

If you need to perform redirects, you can simply use the very powerful "Redirect" plugin, you can find it at this address.

Concerning the cache, the plugins we recommend (W3 Total Cache and WP-Rocket, see our article on Varnish optimization) handle a site without an .htaccess file very well. So you don't have to do anything else than activate the right settings via your WordPress administration interface.

If you want to add other redirections or rules that can not be managed by this plugin, please contact us per ticket and send them to us so we can add them for you.

Want a secure WordPress?

We take effective measures to improve the security of your WordPress site. That's why every time we deploy a new WordPress we perform the following optimizations:

We create for you a login and a secure password for your Admin account.

We change the login and wp-admin URLs that are often used for Brute Force attacks.

We limit the number of login attempts to protect your Admin account.

NO HOTLINK

We apply a direct restriction from our server to protect your site from hotlinking and preserve the bandwidth allocated to it.

CONSTANT MONITORING

We carry out a permanent watch against malicious code on your site and protect you against DDOS attacks.

PROTECTION

We protect your site's files and folders by blocking navigation in your WordPress folders. Access rights are adjusted accordingly.

MASKED

We hide in the code the version of your WordPress, because it gives information to hackers to find possible security holes.

PREFIX WP

We change the default prefix "WP_" of the tables in the MYSQL database. Indeed, this prefix "_WP" is known by all and can be vulnerable in case of injection.

USER ID

We change the default User ID of the first user. Indeed, the ID 1 is known by everyone and is often searched/attacked by hackers.

CONNECTION ERRORS

We hide the connection errors because WordPress returns a message that is far too explicit in case of connection problems.

FILE EDITOR

We disable the internal file editor of WordPress. To edit your files, you will just have to use your FTP software.

SECURITY WATCH

We keep a daily watch on the main WordPress security flaws and inform you directly by newsletter of the most critical ones.

AND THAT'S NOT ALL

Server-side measures are also in place, proactive file scanning with immediate quarantine of suspicious files, and a few others that we are keeping secret.

Updated on 12 July 2022