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

TLS termination listening on wrong port #150

Closed
nutjob4life opened this issue Jan 10, 2023 · 0 comments
Closed

TLS termination listening on wrong port #150

nutjob4life opened this issue Jan 10, 2023 · 0 comments
Assignees
Labels
B13.1 bug Something isn't working s.medium Medium level severity

Comments

@nutjob4life
Copy link
Member

🐛 Describe the bug

When starting the composed Docker services for the Registry, the TLS endpoint starts on port 443 and not 8443.
This conflicts with any local web server which listens on port 443. User processes should generally not listen on ports < 1024.

The change that introduced this should be undone. The reverse-proxy on pds-dev expects it on pds-expo:8443, not 443.

🕵️ Expected behavior

That port 8443 is used.

📚 Version of Software Used

main branch.

🖥 System Info

  • Red Hat Enterprise Linux release 8.7 (Ootpa)

🦄 Related requirements

⚙️ Engineering Details

@nutjob4life nutjob4life added bug Something isn't working needs:triage labels Jan 10, 2023
@jordanpadams jordanpadams added B13.1 s.medium Medium level severity and removed needs:triage labels Jan 11, 2023
jordanpadams added a commit that referenced this issue Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
B13.1 bug Something isn't working s.medium Medium level severity
Projects
None yet
Development

No branches or pull requests

2 participants