Hello, now encountered a problem, the current architecture is two servers to do high availability through nginx.http.sock file forwarding listening 80 port, using remote AWS cloud database, through aws alb load balancing, in access aws cloudfront acceleration, aws cloudfront acceleration when configuring https The whole process is perfect. However, due to the new requirements that require access to Facebook, gmail, discord, apple login, it is found that Facebook will verify https Because it is https configured on aws cloudfront, there may be authentication failures; The final test method is to use the internal https of the program when starting discorse, which is why I hope that the discourse will automatically update the certificate, and then when configuring aws alb for load balancing, it is found that only by configuring http status code 301 can it pass health detection, and when trying to access through ip or http, it will return 301, and return normal 200 when accessing https; Eventually, if you increase how to load balancer or forward, the 301 redirect will be too much,How do I configure it to load balance two machines?
Chengjiu_Su
(Chengjiu Su)
4
Gerelateerde topics
| Topic | Antwoorden | Weergaven | Activiteit | |
|---|---|---|---|---|
| How do I configure Discourse behind an AWS or Google Cloud Proxy with SSL | 20 | 3653 | 25 maart 2019 | |
| SSL cert not working on main Discourse site | 13 | 904 | 30 oktober 2020 | |
| Discourse failure to renew certificate | 24 | 1427 | 23 december 2025 | |
| How to renew Let's Encrypt? | 13 | 4692 | 20 januari 2021 | |
| Setting up Discourse with SSL on Docker with AWS ELB breaks and returns 503 Service Unavailable (Back-end server is at capacity) | 13 | 23097 | 25 februari 2021 |