VirtualCardxForce HTTP to HTTPS Redirect with .htaccess
To force all traffic to use HTTPS, the most common method is to redirect requests via the .htaccess file. Here are the basics about the .htaccess file and the steps to do it:
The .htaccess file is a simple text file named “.htaccess” that contains extra settings passed to the web server, enabling some of your site's more advanced features.
If you use a script built by someone else (including content management systems like WordPress), you can usually find an existing .htaccess file in your site's htdocs folder; if your site doesn't have one yet, you need to create it yourself — we recommend creating a file named .htaccess through the file manager, because some systems (especially Windows) don't handle .htaccess files well, and the file manager avoids problems during creation.
Once you've found or created the .htaccess file, you can edit it with the file manager or any text editor (such as Notepad). Specifically, add the following lines to the file:
RewriteEngine On
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteCond %{HTTPS} off
RewriteCond %{HTTP:CF-Visitor} !{"scheme":"https"}
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]Source: https://forum.infinityfree.com/docs?topic=49322
Force HTTP to HTTPS Redirect with .htaccess: Pre-Check Checklist
Nothing is worse for tutorial-style content than copying commands while ignoring differences in your environment. Different system versions, web servers, plugin combinations and permission settings can all affect the final result. Before you start, record your current configuration and take a snapshot or backup if needed, so you can roll back quickly even if a step goes wrong.
Things to confirm before you start
- System and software versions:Confirm the versions of Windows, Debian, Nginx, Apache, WordPress or related tools.
- Permissions:When credentials, certificates or config files are involved, first confirm the current user has sufficient permissions.
- Backups:Copy the original file before modifying any config file; for WordPress sites, back up the database too.
- Testing method:Verify after each change instead of waiting until everything is done to troubleshoot.
Debugging approach
When an error occurs, first figure out which layer it happens in: browser, DNS, server, application, plugin or permissions. Breaking the problem into small pieces works better than repeatedly searching for the whole error message. For issues involving WordPress, Nginx, certificates or proxies, logs are usually more reliable than the front-end page.
If paths or menus in a tutorial don't match your environment, trust what your current system displays and locate the equivalent feature by keywords. Windows Control Panel, WordPress plugin menus and cloud console entry points in particular often move around between versions.
Ongoing maintenance tips
Fixing a problem once doesn't mean it's gone forever. Write down the key commands, the files you changed, when you changed them and the verification results. When you later migrate servers, upgrade plugins or switch themes, these notes will save you a lot of debugging time.
Related content
2026 verification note
Recheck this procedure against the linked primary documentation and the live configuration before applying it. Product limits, plugin settings, dashboard labels, server paths, and commands change over time. Take a backup, test in staging where possible, validate configuration syntax before reload/restart, and verify the resulting HTTP status, canonical URL, logs, and user-visible behavior. Do not treat a successful command or a third-party tool score as proof that the underlying SEO, security, or availability issue is resolved.
Use least-privilege credentials, keep secrets out of repositories and logs, and preserve a rollback plan. For search changes, observe Search Console data over a normal reporting period rather than repeatedly requesting indexing.