Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

After upgrading from satellite and capsule from 6.14 to 6.15

unable to login with capsule fqdn:8443 

Red Hat Satellite 6.15

In Red Hat Satellite 6.14 users are able to log in using capsule fqdn.

Example: https://capsule-fqdn:8443/users/login

But after upgrading to Satellite 6.15 user are not able to login, but the URL changes to Satellite fqdn


Expected Result:

User should be able to login using capsule fqdn

https://capsule-fqdn:8443/users/login

Technically when you are accessing port 8443 of the capsule, It's proxying the request back to satellite fqdn only. 

I believe there is no intention of even keeping port 8443 active as it was already deprecated in Sat 6.11. On top of that, please check the response from the engineering team on another BZ:

1743839 – [RFE] Officially support core Satellite API proxy via Capsule port 8443
https://bugzilla.redhat.com/show_bug.cgi?id=1743839#c7

*** This bug has been marked as a duplicate of bug 1743839 ***

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days