# Load balancer issue for the web interface **URL:** \ **Category:** Graylog Central (peer support)\ **Created:** [July 4, 2018, 8:50am UTC](https://community.graylog.org/t/load-balancer-issue-for-the-web-interface/5857 "2018-07-04T08:50:18Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![mariusgeonea](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/mariusgeonea/32/2162_2.png) [@mariusgeonea](https://community.graylog.org/u/mariusgeonea)\ **Post date:** [July 4, 2018, 8:50am UTC](https://community.graylog.org/t/load-balancer-issue-for-the-web-interface/5857/1 "2018-07-04T08:50:18Z")
Hello gents, I have a F5 load balancer which sends the web traffic to 3 servers 10.0.0.1, 10.0.0.2 and 10.0.0.3. 10.0.0.3 is the primary where the web connections go, and in case it’s not available the traffic gets to 10.0.0.2 or to 10.0.0.1 in case 10.0.0.2 and 10.0.0.3 are not available. I’m getting the following error when i connect to the web page [https://graylog.local.net](https://graylog.local.net) Server currently unavailable We are experiencing problems connecting to the Graylog server running on [https://10.0.0.3:9000/api/](https://10.0.0.3:9000/api/). Please verify that the server is healthy and working correctly. You will be automatically redirected to the previous page once we can connect to the server. Do you need a hand? We can help you. Less details This is the last response we received from the server: Error message Request has been terminated Possible causes: the network is offline, Origin is not allowed by Access-Control-Allow-Origin, the page is being unloaded, etc. Original Request GET [https://10.0.0.3:9000/api/system/sessions](https://10.0.0.3:9000/api/system/sessions) Status code undefined Full error message Error: Request has been terminated Possible causes: the network is offline, Origin is not allowed by Access-Control-Allow-Origin, the my graylog config is: rest\_listen\_uri = [https://10.0.0.3:9000/api/](https://10.0.0.3:9000/api/) rest\_transport\_uri = [https://10.0.0.3:9000/api/](https://10.0.0.3:9000/api/) web\_listen\_uri = [https://10.0.0.3:9000/](https://10.0.0.3:9000/) web\_endpoint\_uri = [https://10.0.0.3:9000/api/](https://10.0.0.3:9000/api/) do i do anything wrong with the config on the graylog side? Thanks, Marius. ---
**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\ **Post date:** [July 4, 2018, 9:01am UTC](https://community.graylog.org/t/load-balancer-issue-for-the-web-interface/5857/2 "2018-07-04T09:01:09Z")
Is [https://10.0.0.3:9000/api/](https://10.0.0.3:9000/api/) (and all the other 10.0.0.0/8 addresses you’ve mentioned) reachable from your web browser? ---
**Author:** ![mariusgeonea](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/mariusgeonea/32/2162_2.png) [@mariusgeonea](https://community.graylog.org/u/mariusgeonea)\ **Post date:** [July 4, 2018, 9:17am UTC](https://community.graylog.org/t/load-balancer-issue-for-the-web-interface/5857/3 "2018-07-04T09:17:39Z")
> [@jochen](#): > > other 10.0.0.0/8 addresses yo yes they are, all of them ---
**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\ **Post date:** [July 4, 2018, 9:40am UTC](https://community.graylog.org/t/load-balancer-issue-for-the-web-interface/5857/4 "2018-07-04T09:40:04Z")
Have you configured Graylog to enable HTTPS on the Graylog REST API (via `rest_enable_tls=true`)? Hint: Maybe your `web_endpoint_uri` should be different, if you’re terminating SSL/HTTPS in your load balancer. ---
**Author:** ![mariusgeonea](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/mariusgeonea/32/2162_2.png) [@mariusgeonea](https://community.graylog.org/u/mariusgeonea)\ **Post date:** [July 4, 2018, 9:55am UTC](https://community.graylog.org/t/load-balancer-issue-for-the-web-interface/5857/5 "2018-07-04T09:55:10Z")
i have the web and the rest set to true rest\_enable\_tls = true web\_enable\_tls = true the load balancer is doing a redirect from [https://graylog.local.net](https://graylog.local.net) to [https://10.0.0.3:9000/api/](https://10.0.0.3:9000/api/) ---
**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\ **Post date:** [July 4, 2018, 10:07am UTC](https://community.graylog.org/t/load-balancer-issue-for-the-web-interface/5857/6 "2018-07-04T10:07:40Z")
What happens if you open [https://10.0.0.3:9000/](https://10.0.0.3:9000/) in a fresh browser session? > [@mariusgeonea](#): > > the load balancer is doing a redirect from [https://graylog.local.net](https://graylog.local.net) to [https://10.0.0.3:9000/api/](https://10.0.0.3:9000/api/) What does “redirect” mean exactly? Is it sending an HTTP response with status 30x and a proper `Location` header? ---
**Author:** ![mariusgeonea](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/mariusgeonea/32/2162_2.png) [@mariusgeonea](https://community.graylog.org/u/mariusgeonea)\ **Post date:** [July 4, 2018, 10:16am UTC](https://community.graylog.org/t/load-balancer-issue-for-the-web-interface/5857/7 "2018-07-04T10:16:44Z")
i don’t have access to the LB itself, but the healthchecks are done with HTTPS and it is sending a https response, as far as i know. do you think that LB might be the problem? ---
**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\ **Post date:** [July 4, 2018, 10:31am UTC](https://community.graylog.org/t/load-balancer-issue-for-the-web-interface/5857/8 "2018-07-04T10:31:36Z")
> [@mariusgeonea](#): > > do you think that LB might be the problem? No, I think that your Graylog configuration is the problem. > [@jochen](#): > > Hint: Maybe your `web_endpoint_uri` should be different, if you’re terminating SSL/HTTPS in your load balancer. ---
**Author:** ![mariusgeonea](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/mariusgeonea/32/2162_2.png) [@mariusgeonea](https://community.graylog.org/u/mariusgeonea)\ **Post date:** [July 4, 2018, 10:36am UTC](https://community.graylog.org/t/load-balancer-issue-for-the-web-interface/5857/9 "2018-07-04T10:36:23Z")
now i changed it to web\_endpoint\_uri = [https://graylog.local.net:9000/api/](https://graylog.local.net:9000/api/) and now i get We are experiencing problems connecting to the Graylog server running on [https://graylog.local.net:9000/api/](https://graylog.local.net:9000/api/). Please verify that the server is healthy and working correctly. ---
**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\ **Post date:** [July 4, 2018, 10:38am UTC](https://community.graylog.org/t/load-balancer-issue-for-the-web-interface/5857/10 "2018-07-04T10:38:08Z")
> [@mariusgeonea](#): > > now i changed it to > web\_endpoint\_uri = [https://graylog.local.net:9000/api/](https://graylog.local.net:9000/api/) Why did you choose to use this URI when you’re using [https://graylog.local.net](https://graylog.local.net) in your web browser? Hint: Maybe [https://graylog.local.net/api/](https://graylog.local.net/api/) might work? ---
**Author:** ![mariusgeonea](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/mariusgeonea/32/2162_2.png) [@mariusgeonea](https://community.graylog.org/u/mariusgeonea)\ **Post date:** [July 4, 2018, 10:42am UTC](https://community.graylog.org/t/load-balancer-issue-for-the-web-interface/5857/11 "2018-07-04T10:42:07Z")
that config works like a charm. Many thanks for your help Jochen 🙂 ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\ **Post date:** [July 18, 2018, 10:42am UTC](https://community.graylog.org/t/load-balancer-issue-for-the-web-interface/5857/12 "2018-07-18T10:42:09Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.