# 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:** 7

<div class="post-metadata">

**Author:** ![Martin\_Bailey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/martin_bailey/32/238747_2.png) [@Martin\_Bailey](https://meta.discourse.org/u/Martin_Bailey)\
**Post date:** [April 5, 2022, 7:01am UTC](https://meta.discourse.org/t/problems-with-patreon-login-force-https-and-s3-cdn-three-issues/223144/7 "2022-04-05T07:01:37Z")

</div>

OK guys, you win. 🙂

I started to see more issues with images not loading again because they were sometimes being shared over http and not https. You’re right, it’s a mess.

I’ve just backed most of the way out of this, leaving the Postgres database in place but back to just one server droplet, no load-balancer and images/Redis stored locally. I’ve left S3 in place for the site backups though. I love how smoothly that works.

I’m back to 15-minute outages with each upgrade I guess, but I’ve spent a total of like five full days on this so far, and I can’t spend any more time on it, so I’m happy that you were all able to put me straight regarding that original tutorial I followed. It’s almost as though they just want people to pay for more Droplets. 🙂

Thanks again for your help.

---

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