Hi Team,
We are experiencing an issue with our Rundeck instance on dbfz instance. Even though the configuration specifies HTTPS on port 8080 (RDECK_HTTPS_PORT=8080 and framework.server.url set to http://<host>:8080), accessing the web interface redirects to port 8443.
Steps taken so far:
Verified framework.server.url in /etc/rundeck/framework.properties is correct.
Checked for any references to 8443 across /etc/rundeck/—none found.
Updated /etc/rundeck/profile to include SSL configuration on port 8080.
Restarted rundeckd service; however, the service fails to start when adding -Dserver.port=8080 to force HTTPS.
Current behavior:
Curling https://<host>:8080/ results in a 302 Found redirect to https://<host>:8443/user/login.
Startup logs indicate Rundeck is running, but the application redirects to 8443, causing access issues.
Request:
Guidance on how to properly configure Rundeck to serve HTTPS on port 8080 without redirecting to 8443.
Confirmation if there are hidden defaults or startup scripts that enforce port 8443.
Any recommended best practices for SSL configuration on a non-standard port.
Thank you for your support.
Regards,
Deljin Davis