Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Graylog2 provides wrong API URI after upgrade to 2.1 beta3 #2680
Graylog 2 should provide the API URI with https, if rest_transport_uri is set with https URI.
Today I tried upgrading from Graylog 2.1 beta-2 to beta-3 without changing any settings. Currently our rest_transport_uri is set to https://graylog:443 and it worked fine for every version until beta-3.
We use SSL Offloading with a A10 loadbalancer and the API and Web endpoint of graylog do not use SSL themselves, so web_enable_tls is not set. They are available via different DNS names, and do not use the same IP address on the loadbalancer, but use the same servers. When upgrading to beta-3, I get an error message on the web interface, that the graylog-server could not connect to the API endpoint "http://graylog:443". So it changes https to http, which is not working. Removing the 443 results in a HTTP code 301, since it automatically redirects to https, but this is also not working for me.
I am not quite sure if this is an issue with the new beta version and URI handling, or if this is simply a config error on my side.
Steps to Reproduce (for bugs)
Since I was testing on a preview instance, there was no real impact and reverting to beta-2 fixed the issue for me. We plan on upgrading our live environment to 2.1 once it has a stable release.