- Notifications
You must be signed in to change notification settings - Fork958
Description
🐛 Bug Report: Rundeck Redirects to Port 8443 After Logout Despite Configuration Using 8080
Getting Help
Please use this issue template for reporting identified or suspectedbugs only.
For configuration or troubleshooting, please seeGetting Help.
Describe the bug
Rundeck always redirects the login page to port8443 after logout, even though the instance is configured and running onHTTPS port 8080 only.
All configuration files (rundeck-config.properties,framework.properties,/etc/rundeck/profile) and database entries (rundeckdb.mv.db) reference port 8080. However, after logging out and clickingLogin, the browser is redirected to:
https://dbfz-automate01.leipzig.dbfz.de:8443/user/loginThis causes aERR_CONNECTION_REFUSED error since port 8443 is closed.
My Rundeck detail
| Field | Value |
|---|---|
| Rundeck version | 5.17.0-20251103 |
| Install type | deb |
| OS Name/version | Ubuntu 22.04 LTS (Kernel 6.1.0-40-amd64) |
| DB Type/version | H2 embedded (rundeckdb.mv.db) |
| Java version | OpenJDK 11.0.28 (Ubuntu build) |
| Node hostname | dbfz-automate01.leipzig.dbfz.de |
To Reproduce
- Install Rundeck via
.debon Ubuntu 22.04. - Configure SSL and port 8080 in
/etc/rundeck/rundeck-config.properties:grails.serverURL=https://dbfz-automate01.leipzig.dbfz.de:8080server.port=8080server.enableHttpsConnector=falseserver.ssl.key-store=/etc/rundeck/ssl/keystore
- Start Rundeck:
sudo systemctl start rundeckd
- Log in successfully via
https://dbfz-automate01.leipzig.dbfz.de:8080. - Log out and clickLogin again.
- Observe redirect to:→
https://dbfz-automate01.leipzig.dbfz.de:8443/user/loginERR_CONNECTION_REFUSED.
Expected behavior
Rundeck should consistently use the configured HTTPS port (8080) for all generated links and redirects, including login/logout actions.
The redirect should resolve to:
https://dbfz-automate01.leipzig.dbfz.de:8080/user/loginScreenshots
| Description | Screenshot |
|---|---|
| Redirect after logout |

|
Desktop (client browser)
| Field | Value |
|---|---|
| OS | Windows 10 |
| Browser | Google Chrome |
| Version | 141.0.0.0 (latest) |
Additional context
- No references to port 8443 exist in
/etc/rundeckor the embedded H2 database. - Redirect behavior persists even with
server.enableHttpsConnector=falseand cookie clearing. - The internal Grails app appears to default to 8443 when SSL is detected, despite custom port configuration.
- Likely related to Jetty’s embedded HTTPS connector initialization (default redirect port hardcoded at 8443).
Suspected Root Cause:server.externalRedirectPort or similar Jetty/Grails internal default is not overridden when a nonstandard HTTPS port (8080) is configured. This causes Rundeck to generate redirect URLs pointing to 8443.