Signup: confirmation link redirects to https version of your Jetpack site

[jeherve]

Steps to reproduce

1. Start from a self-hosted WP site using HTTP, not HTTPS.
2. Activate the Jetpack plugin.
3. Follow the steps and get to the Jetpack signup flow for WordPress.com.
4. Create your WordPress.com account, finish connecting Jetpack on your site.
5. In my meantime, you've received an email asking you to "Activate" your WordPress.com account.
   
6. When clicking on that link, your account gets verified and you then get redirected to your Jetpack site.

The problem is, the Jetpack site URL is incorrect: it always uses HTTPS, even though my site does not use HTTPS.

[stale]

This issue has been marked as stale because it hasn't been updated in a while. It will be closed in a week.
If you would like it to remain open, can you please you comment below and see what you can do to get things moving with this issue?
Thanks! 🙏

[jeherve]

This is still an issue.

[github-actions]

This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels.

[github-actions]

This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels.

[cuemarie]

👋 Hey folks! Since this issue has been inactive for quite some time, KitKat has made the decision to close it.

• Internal reference, for more on this decision: pdqkMK-14B-p2

If you think this issue warrants another look, here are some next steps!

1. Report anew: A new report with more current details and steps to replicate may be the best way to renew attention on this issue. Feel free to refer back to this closed issue in your report!
2. Reopen: If you feel the issue still matches the context/history here, you can also reopen the issue and add fresh logs, screenshots and steps to reproduce.

Thanks for your involvement!