Back again :slight_smile: and as always, apologies for my noob devops questions, but here it goes … I’m trying to setup https for a docker instance of Discourse that’s deployed on AWS. I’m able to successfully run Discourse on AWS using the following setup: EC2 t2.medium instance (attached to an …

So I ended up just ditching the ELB as there’s other questions about how to setup duplicate EC2 instances to actually use load balancing and manage asset paths and updates appropriately. I was able to setup HTTPS within Discourse/docker and used an elastic IP. [Bild] riking: Make the directory.…

If you’re using HTTPS via ELB, you do not need to use it within the Docker or Discourse. Have your ELB back-end to HTTP/80 and let it handle all the HTTPS proxying itself. Put another way: as far as Discourse and Docker are concerned, they’re still just HTTP. ELB will act as a secure proxy, using t…

Thanks @mshappe that answers one of the problems! The remaining two are: what’s the best method to redirect HTTP to HTTPS using AWS ELB? any thoughts on how to address updates / rebuild of the Discourse server breaking the ELB? Thanks!

How about not thinking it as “redirect http->https using ELB”? Redirect it on the end point. Apache’s htaccess, Nginx https redirect, or App’s response header redirect. I hope that helps.

For the redirect, I think that https setting should work, but I haven’t tried it. I know for a straight rails application, configuring nginx or Rails itself to always redirect to https just works, provided that the URL being redirected to is the ELB’s URL, not your server’s. In general, that should …

[Bild] stroupaloop: instead when I cd / ls through the directory, I get /var/discourse/shared/web-only/ with no path to an ssl folder within web-only (the folders available are: backups, log, state, uploads), which is when I stopped and decided to start this thread. Make the directory. Alth…

I like to have the whole domain fronted by a CDN such a CloudFront or CloudFlare and then you can use that to redirect HTTP > HTTPS.

[Bild] stroupaloop: had to setup the Health Check to TCP:80/ because the root URL redirects to /login if not logged in (this is just a note for others trying to do this). There is actually a /srv/status end point which should return a simple 200 “ok” response.

Here is a tutorial (apparently written by a 14 year old) on setting up Discourse with AWS, including ELB. https://web.archive.org/web/20140424075917/http://0ak.org/how-to-setup-discourse-on-amazon-aws/

Thanks for this link. I can’t see where his post talks about ELB or am I missing something?

[Bild] stroupaloop: ended up ditching Did anyone find a solution to make discourse work with ELB?

Setting up Discourse with SSL on Docker with AWS ELB breaks and returns 503 Service Unavailable (Back-end server is at capacity)

Unterstützung Installation

schleifer (Andrew Schleifer) 25. Februar 2021 um 06:42 13

Die Seite, die Sie gerade lesen, wird hinter einem AWS ELB gehostet.

5 „Gefällt mir“

Thema		Antworten	Aufrufe
How do I configure Discourse behind an AWS or Google Cloud Proxy with SSL Self-hosting	21	3301	20. Mai 2022
Discourse instance unreachable on AWS Support	29	3987	30. April 2019
Configure Discourse - Environment AWS Linux 2 AMI and Apache2 (httpd) Self-hosting advanced-setup	3	2253	7. Juli 2023
How to install Discourse in the AWS EC2 Instances(Ubuntu Server LTS)? Self-hosting	36	4846	30. März 2019
Aws deployed discourse is fetching assets from database url Support unsupported-install	20	2262	15. November 2020

Setting up Discourse with SSL on Docker with AWS ELB breaks and returns 503 Service Unavailable (Back-end server is at capacity)

Verwandte Themen