Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Bug Report: Rundeck Redirects to Port 8443 After Logout Despite Configuration Using 8080 #9882

Open
@DelDex

Description

@DelDex

🐛 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/login

This causes aERR_CONNECTION_REFUSED error since port 8443 is closed.


My Rundeck detail

FieldValue
Rundeck version5.17.0-20251103
Install typedeb
OS Name/versionUbuntu 22.04 LTS (Kernel 6.1.0-40-amd64)
DB Type/versionH2 embedded (rundeckdb.mv.db)
Java versionOpenJDK 11.0.28 (Ubuntu build)
Node hostnamedbfz-automate01.leipzig.dbfz.de

To Reproduce

  1. Install Rundeck via.deb on Ubuntu 22.04.
  2. 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
  3. Start Rundeck:
    sudo systemctl start rundeckd
  4. Log in successfully viahttps://dbfz-automate01.leipzig.dbfz.de:8080.
  5. Log out and clickLogin again.
  6. Observe redirect to:
    https://dbfz-automate01.leipzig.dbfz.de:8443/user/login
    ERR_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/login

Screenshots

DescriptionScreenshot
Redirect after logout
Image

|

Desktop (client browser)

FieldValue
OSWindows 10
BrowserGoogle Chrome
Version141.0.0.0 (latest)

Additional context

  • No references to port 8443 exist in/etc/rundeck or the embedded H2 database.
  • Redirect behavior persists even withserver.enableHttpsConnector=false and 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2025 Movatter.jp