Skip to content
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

Setting "server.http.host" has no effect in 3.0 #3786

Closed
paulholden opened this issue Aug 6, 2018 · 7 comments
Closed

Setting "server.http.host" has no effect in 3.0 #3786

paulholden opened this issue Aug 6, 2018 · 7 comments
Assignees

Comments

@paulholden
Copy link

Describe the bug
In previous versions (2.11.5) of Rundeck it was possible to configure the interface to bind to by setting the server.http.host System Property - ref.

This setting no longer appears to have any effect in 3.0

My Rundeck detail

  • Rundeck version: 3.0.0
  • install type: deb
  • OS Name/version: ubuntu 16.04
  • DB Type/version: mysql

To Reproduce
Steps to reproduce the behavior:

  1. Set server.http.host in profile configuration file
  2. Observe netstat output and see server is bound to all addresses "0.0.0.0"

Expected behavior
Rundeck should observe the server.http.host configuration and bind to the correct interface

@sjrd218
Copy link
Contributor

sjrd218 commented Aug 6, 2018

Try setting the server.address property and let us know if that accomplishes your desired result in 3.0.

@joscha-alisch
Copy link

joscha-alisch commented Aug 6, 2018

@sjrd218 We have the same problem with the "server.http.port" system property. Since updating to 3.0, it no longer has an effect as well. Seems like this might be related - if not, I'm happy to create a separate issue.

@sjrd218
Copy link
Contributor

sjrd218 commented Aug 6, 2018

@joscha-alisch Try using server.port and see if that works.

The latest grails framework is built on spring boot so we've had to change the way Rundeck initialization works. We may have a few places where we aren't translating the old property to the new. Please let us know if these properties mentioned above work for you. Thanks!

@joscha-alisch
Copy link

Yes that works @sjrd218, thank you! I can also confirm that "server.address" works for me for the initial issue of @paulholden.

@sjrd218 sjrd218 self-assigned this Aug 6, 2018
@chtay
Copy link

chtay commented Aug 7, 2018

I just tried rundeck-3.0.1-20180803 (war version)..and this is what I notice.
The configuration files (profile, framework.properties, preference.properties) has no affect.
Looks like the correct config file now is only "rundeck-config.properties".
The config is case sensitive.

To change the server address (lets say 192.168.1.2), you need to modify the rundeck-config.properties on:
server.address=192.168.1.2

To change the port to lets say 4444, you need to modify the rundeck-config.properties on:
server.port=4444

To change the web context to lets say http(s)://yourserver:4444/rundeck, you need to modify the undeck-config.properties on:
server.contextPath=/rundeck

If you are doing a reverse proxy thing, lets say https://yourserver/rundeck do remember to change the rundeck-config.properties on:
grails.serverURL=https://yourserver/rundeck

@paulholden
Copy link
Author

Thanks all, I've upgraded to 3.0.5 this morning and can confirm that server.http.host is now working as expected 👍

@lightarrow
Copy link

I fixed this issue by setting ports in /etc/rundeck/framework.properties & /etc/rundeck/rundeck-config.properties

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants