RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.

Created attachment 1038496 [details]
Errorcode70 pop up displayed while registering in red hat

Description of problem:Problem Registering System


Version-Release number of selected component (if applicable):RedHat 6.5 x64


How reproducible:


Steps to Reproduce:
1.First I type the command Rhn_register for registering my red hat
2.When I enter the system name ie(by default name(local.localdomain) is given)
3.I am facing some error popup ie Error communicating with server

Actual results:


Expected results:


Additional info:

Hi Ashutosh,

There are a number of known causes of this error. Have you tried any of the possible resolutions here? https://access.redhat.com/articles/1345223

If you've tried these already, you may need to contact support directly.

Cheers,
Laura B

Closing INSUFFICIENT DATA.