New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support customizing web-ui port #983

Closed
schakrava opened this Issue Oct 25, 2015 · 5 comments

Comments

Projects
None yet
5 participants
@schakrava
Member

schakrava commented Oct 25, 2015

Currently web-ui port(443) cannot be changed from the web-ui. Some users seem to want it.

http://forum.rockstor.com/t/appliances-management-port/601

@neyfrota

This comment has been minimized.

Show comment
Hide comment
@neyfrota

neyfrota Mar 5, 2016

add my 5 cents here:

Change nginx is the easy part... Big problem is: some rockstor systems need api at 443.... Try this:

  • ssh
  • change nginx config https port to 1443 (or any other)
  • reboot your rockstor
  • ssh again
  • RESULT: You notice NO pools/shares are mounted.. just basic root
  • change nginx config https port back to 443
  • reboot your rockstor
  • ssh again
  • RESULT: all your pools shares are mounted

So my guess is: rockstor startup service need api to perform some tasks

Im now looking how to change "current appliance" settings ... my guess if i explain my appliance lives at 1443, rockstor startup scripts will obey and we have peace in system again

Does any one has experience on that?

neyfrota commented Mar 5, 2016

add my 5 cents here:

Change nginx is the easy part... Big problem is: some rockstor systems need api at 443.... Try this:

  • ssh
  • change nginx config https port to 1443 (or any other)
  • reboot your rockstor
  • ssh again
  • RESULT: You notice NO pools/shares are mounted.. just basic root
  • change nginx config https port back to 443
  • reboot your rockstor
  • ssh again
  • RESULT: all your pools shares are mounted

So my guess is: rockstor startup service need api to perform some tasks

Im now looking how to change "current appliance" settings ... my guess if i explain my appliance lives at 1443, rockstor startup scripts will obey and we have peace in system again

Does any one has experience on that?

@schakrava schakrava modified the milestones: Looney Bean, Yosemite Mar 6, 2016

@holmesb

This comment has been minimized.

Show comment
Hide comment
@holmesb

holmesb Mar 11, 2016

The mgmt_port variable appears to be set to 443 by appliance.py. But there are 58 references to 443 in the code, and some of these are hard-coded rather than use the mgmt_port variable. So the solution is probably to allow mgmt_port to be changed in appliance.py then replace the hard-coded references elsewhere with mgmt_port.

holmesb commented Mar 11, 2016

The mgmt_port variable appears to be set to 443 by appliance.py. But there are 58 references to 443 in the code, and some of these are hard-coded rather than use the mgmt_port variable. So the solution is probably to allow mgmt_port to be changed in appliance.py then replace the hard-coded references elsewhere with mgmt_port.

@phillxnet

This comment has been minimized.

Show comment
Hide comment
@phillxnet

phillxnet May 6, 2016

Member

Linking to another forum threat with a use case involving for this feature involving openvpn:
https://forum.rockstor.com/t/openvpn-over-tcp/1457

Member

phillxnet commented May 6, 2016

Linking to another forum threat with a use case involving for this feature involving openvpn:
https://forum.rockstor.com/t/openvpn-over-tcp/1457

@greghensley

This comment has been minimized.

Show comment
Hide comment
@greghensley

greghensley Jun 1, 2016

It looks like this was partially taken care of by cc3c89a, which included a setting for the HTTPS listener port in the rockstor service settings. However, I still see two areas for improvement:

  1. It needs another option to disable the default redirection of port 80 -> https
  2. Updating the setting regenerates rockstor's nginx.conf, but the change is not persistent across updates of the rockstor package.
    • That is, the config database maintains the custom port setting but nginx.conf is replaced by the default copy from the package. Since nginx.conf is only updated when the setting is changed, rather than when the rockstor service is started, you have to access the web interface on port 443 again, go to the rockstor service settings, and hit Submit to recreate nginx.conf with the correct port.
  3. It's not current possible to set a custom port which listens on the ANY address (0.0.0.0 and [::]), since the config settings require selection of a network interface. This, despite the fact that the default nginx config uses the ANY address.

greghensley commented Jun 1, 2016

It looks like this was partially taken care of by cc3c89a, which included a setting for the HTTPS listener port in the rockstor service settings. However, I still see two areas for improvement:

  1. It needs another option to disable the default redirection of port 80 -> https
  2. Updating the setting regenerates rockstor's nginx.conf, but the change is not persistent across updates of the rockstor package.
    • That is, the config database maintains the custom port setting but nginx.conf is replaced by the default copy from the package. Since nginx.conf is only updated when the setting is changed, rather than when the rockstor service is started, you have to access the web interface on port 443 again, go to the rockstor service settings, and hit Submit to recreate nginx.conf with the correct port.
  3. It's not current possible to set a custom port which listens on the ANY address (0.0.0.0 and [::]), since the config settings require selection of a network interface. This, despite the fact that the default nginx config uses the ANY address.

@greghensley greghensley referenced this issue Jun 28, 2016

Open

IPv6 support in nginx #1360

0 of 2 tasks complete

schakrava added a commit to schakrava/rockstor-core that referenced this issue Jul 1, 2016

schakrava added a commit to schakrava/rockstor-core that referenced this issue Jul 1, 2016

schakrava added a commit to schakrava/rockstor-core that referenced this issue Jul 1, 2016

@schakrava schakrava closed this in 3c5e2c5 Jul 2, 2016

@schakrava

This comment has been minimized.

Show comment
Hide comment
@schakrava

schakrava Jul 2, 2016

Member

@greghensley Thanks for listing the problems. You saved me time, appreciate it!

Member

schakrava commented Jul 2, 2016

@greghensley Thanks for listing the problems. You saved me time, appreciate it!

@schakrava schakrava changed the title from custom web-ui port to Support customizing web-ui port Nov 1, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment