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

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 4, 2022, 4:22pm UTC](https://meta.discourse.org/t/problems-with-patreon-login-force-https-and-s3-cdn-three-issues/223144/2 "2022-04-04T16:22:05Z")

</div>

> [@Martin\_Bailey](#):
>
> A few days ago, I used this tutorial ([How to Scale a Discourse Deployment with a Load Balancer and Managed Database Cluster | DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-scale-your-discourse-deployment-with-a-load-balancer-and-managed-database-cluster)) pretty much to the word and migrated my standalone Discourse Droplet on Digital Ocean to two Droplets inside a Load-Balancer, so far so good.

Then you really need to get help there because all that’s really supported here is a [standard install](https://meta.discourse.org/t/142537?silent=true).

Are you expecting more than 200K page views/day? If not, a single 8GB droplet with CDN will be much easier to manage and probably cheaper. And from what I can tell, there are at least a couple of ways those instructions are likely not to work for anyone.

First, did set you up an external redis as described in step 5? If not, I’d expect things to be at least a little bit broken. They imply that using sticky will “fix” it, but it really won’t. So you can expect hard-to-diagnose spurious errors. And they don’t specify a way to make sure that all of your instances are running exactly the same version of Discourse, so that too is likely to make things broken.

> [@Martin\_Bailey](#):
>
> I then went through this tutorial ([Using Object Storage for Uploads (S3 & Clones)](https://meta.discourse.org/t/using-object-storage-for-uploads-s3-clones/148916#digital-ocean-spaces))

You really wanted to do that first, otherwise, actually, that setup **can’t** work, because some uploads will be on one server and some on another, and those instructions make no mention of the word “upload”, so I expect that if you’ve been using this for more than testing you’ve got something of a mess on your hands and you’ll need to sync up the uploads between your multiple droplets.

> [@Martin\_Bailey](#):
>
> I could not get the Digital Ocean Space/CDN to work with S3/CDN according to this tutorial ([Using Object Storage for Uploads (S3 & Clones)](https://meta.discourse.org/t/using-object-storage-for-uploads-s3-clones/148916#digital-ocean-spaces)).

It specifically states that the Digital Ocean CDN doesn’t work with Discourse.

> [@Configure an S3 compatible object storage provider for uploads](https://meta.discourse.org/t/configure-an-s3-compatible-object-storage-provider-for-uploads/148916/1):
>
> DO offering is good and works out of the box. Only problem is that their CDN offering is awfully broken, so you need to use a different CDN for the files.

Did you use a different CDN as it recommends? [Bunny.net](http://Bunny.net) is pretty easy and simple to set up.

---

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