Fuel redirect to wrong HTTPS port: 8443

[Thomas Goirand]

After installing Fuel master node on Debian (yes, you're reading well ... :) no, it's not uploaded to Debian ... YET !), I have found that the web interface for Fuel, at the login prompt, has a link to HTTPS, though this link redirects to port 443.

not serioius:
What have you guys drink to redirect to this port number? Do you know it's forbidden to drink and type code?
/joke

More seriously, while it may make sense to use such a funny port, probably the default should be 443. I would advise a specific configuration option to use any other port.

[Maciej Kwiek (maciej-iai)]

If this bug is indeed a bug, it needs changes in both Library and UI, probably in files
In library port number is configured in deployment/puppet/nailgun/templates/nginx_nailgun.conf.erb
In UI Port is set in nailgun/static/views/login_page.js#L121

[Maciej Kwiek (maciej-iai)]

Also, changing to Low, it seems that this doesn't really affect anything. It's just non-standard port.

[Thomas Goirand (thomas-goirand)]

Maciej Kwiek (maciej-iai), please don't turn this into "low", as Debian really *IS* affected. Indeed, fuel gets installed in the normal Apache configuration, where the port 443 is in use, not this non-standard port. The packaging will *NOT* be changed to switch to such a non-standard port. As a consequence, this is just a broken link, which we would like to avoid.

[Thomas Goirand (thomas-goirand)]

Oh, btw, I'm just interested in the JS file fix, as the Debian package installs the Apache config itself. Thanks for pointing at the correct place to patch, which I have added as a debian/patches file in my package.

[Dmitry Pyzhov (dpyzhov)]

It doesn't look like an issue from the user point of view. So I'm marking it as a tech-debt. However I think this is a quite important tech-debt.

[Thomas Goirand (thomas-goirand)]

Is there a patch available? Has it been merged yet?

[Maksim Malchuk (mmalchuk)]

Not yet. As You can see the status is Triaged, not In Progress.

[Vitaly Kramskikh (vkramskikh)]

I'm still unsure how this should be fixed. Currently UI doesn't have its own config, it only relies on nailgun and the only "configurable" value which is used by UI - is "auth enabled" flag which is obtained via /api/version output. The approach should be discussed, so moving the status back to Confirmed