Closed CBozsik closed 7 years ago
The content you are trying to serve from the load balancer (client) is over HTTP on your master (HTTPS). This should be returning an mixed content warning in your browsers JS console. IMO, this functionality should even be necessary and was only implemented to fulfill a weird use-case of one of the developers. A much simpler route would just to use an actual CDN.
Edit: Also, this functionality technically isn't a load balancer and is incorrectly named. It's just a simple hack to distribute bandwidth usage across numerous servers/instances. If you are looking to improve performance, you would need to have load balancing done at a routing level or have some really aggressive caching solution with a CDN service.
Hey, I think I have everything set up correctly but my master reader is only loading half the pages now. Is this something that takes some time to sync up the master and clients? Or is there an issue with having an https master and an http client?
I've set the client to 0% priority for now just so it works fine for my readers.
Master Settings:![image](https://user-images.githubusercontent.com/16769601/27946504-6181d0e2-62af-11e7-8d06-dbd66c37a11e.png)
Client Settings:![image](https://user-images.githubusercontent.com/16769601/27946518-71fc172a-62af-11e7-8cd5-2018dd291a62.png)