# Problems with Patreon Login, Force HTTPS, and S3 CDN (three) Issues

**URL:** <https://meta.discourse.org/t/problems-with-patreon-login-force-https-and-s3-cdn-three-issues/223144>\
**Category:** Self-hosting\
**Tags:** unsupported-install\
**Created:** [April 4, 2022, 1:14pm UTC](https://meta.discourse.org/t/problems-with-patreon-login-force-https-and-s3-cdn-three-issues/223144 "2022-04-04T13:14:26Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [January 6, 2023, 6:58pm UTC](https://meta.discourse.org/t/problems-with-patreon-login-force-https-and-s3-cdn-three-issues/223144/13 "2023-01-06T18:58:06Z")

</div>

> [@Francis](#):
>
> my thinking at the time was that using sticky sessions would allow you to use the builtin Redis in the Discourse image. Is this correct?

No, as Redis isn’t a simple cache, but handles a lot of counting, rate limits, background jobs, pub sub. Having multiple Redii will result in corrupted counting and broken behavior.

> [@Francis](#):
>
> I suspect removing all state from the Droplets is the answer to solve the installation problems

That would do it, but adding a managed Redis, managed PostgreSQL, managed Load Balancer, Object Storage, Container Registry will also be more expensive than just paying for our standard hosting and a lot more complicated to maintain.

At that point the intersection between people who want to pay hundreds of dollars per month and don’t care if their service go down because of a SPOF is quite small, and it becomes more a hobbyist setup than what we would recommend for forum admins.

---

_[View the full topic](https://meta.discourse.org/t/problems-with-patreon-login-force-https-and-s3-cdn-three-issues/223144)._