HTTPS certificate warning and redirect issue after updating TranslatePress
-
Hello,
I believe I have found a regression introduced by the latest TranslatePress update.
Environment
- WordPress (latest)
- TranslatePress (latest version after update)
- Astra Pro
- Cloudflare (DNS only, no proxy)
- Apache
- HTTPS with a valid Let’s Encrypt certificate
Issue
Immediately after updating TranslatePress, Brave (and sometimes other Chromium-based browsers) starts displaying HTTPS/security warnings when visiting my site.
Before the update, everything worked normally.
To verify this wasn’t a server issue, I restored my entire virtual machine from a backup taken before the update. Without changing anything else, the problem disappeared completely.
I updated TranslatePress again, and the problem immediately returned.
This makes the issue 100% reproducible on my installation.
What I’ve verified
- SSL certificate is valid.
homeandsiteurlare correctly configured to HTTPS.is_ssl()returnstrue.- The web server is correctly serving HTTPS.
- Restoring the VM before the TranslatePress update fixes the problem.
- Updating TranslatePress immediately brings the problem back.
Observed behavior
After the update, requests involving the translated language (
/fr) appear to trigger unexpected redirect or HTTPS behavior that results in browser security warnings.Questions
- Are you aware of any recent changes to redirect handling or HTTPS detection?
- Has anyone reported similar issues after the latest release?
- Is there any debug mode or logging I can enable in TranslatePress to determine exactly what changed?
I would be happy to perform additional tests or provide logs if needed.
Additional information
This issue is reproducible on my installation:
- Restore the site from a backup taken before the TranslatePress update → everything works correctly.
- Update TranslatePress to the latest version → HTTPS/security warnings immediately appear again.
- Restore the backup again → the issue disappears.
I have repeated this process multiple times with the same result, which strongly suggests the problem is introduced by the latest TranslatePress update rather than by my server configuration.
The problem occurs when updating from version 3.2.1 to version 3.2.2.
The page I need help with: [log in to see the link]
You must be logged in to reply to this topic.