// Module included in the following assemblies:
//
// * cloud_experts_tutorials/cloud-experts-rosa-with-hcp-private-offer-acceptance-and-sharing.adoc

:_mod-docs-content-type: REFERENCE
[id="offer-troubleshooting_{context}"]
= Private offer troubleshooting

[role="_abstract"]
Review solutions for the most frequent issues associated with private offer acceptance and Red{nbsp}Hat account linking.

[id="accessing-private-offer-different-aws-account_{context}"]
== Accessing a private offer using a different AWS account

* If you try accessing the private offer when logged in under an AWS account ID that is not defined in the offer, and see the "Page not found" message, then verify that you are logged in as the desired AWS billing account.
+
[caption="HTTP 404 error when using the private offer URL"]
image::rosa-http-404-error-when-using-the-private-offer-url.png[]
+
** Contact the seller if you need the private offer to be extended to another AWS account.

[id="private-offer-cannot-be-accepted_{context}"]
== The private offer cannot be accepted because of an active subscription

* If you try accessing a private offer that was created for the first-time {product-title} activation, while you already have {product-title} activated using another public or private offer, and see the following notice, then contact the seller who provided you with the offer.
+
The seller can provide you with a new offer that will seamlessly replace your current agreement, without a need to cancel your previous subscription.
+
[caption="Existing subscription preventing private offer acceptance"]
image::rosa-existing-subscription-preventing-private-offer-acceptance.png[]

[id="aws-account-linked-to-different-rh-account_{context}"]
== The AWS account is already linked to a different Red{nbsp}Hat account

* If you see the error message "AWS account is already linked to a different Red{nbsp}Hat account" when you try to connect the AWS account that accepted the private offer with a presently logged-in Red{nbsp}Hat user, then the AWS account is already connected to another Red{nbsp}Hat user.
+
[caption="AWS account is already linked to a different Red{nbsp}Hat account"]
image::rosa-aws-account-is-already-linked-to-a-different-red-hat-account.png[]

* You can either log in using another Red{nbsp}Hat account or another AWS account.

** However, since this guide pertains to private offers, the assumption is that you are logged in with the AWS account that was specified as the buyer and already accepted the private offer so it is intended to be used as the billing account. Logging in as another AWS account is not expected after a private offer was accepted.

* You can still log in with another Red{nbsp}Hat user which is already connected to the AWS account that accepted the private offer. Other Red{nbsp}Hat users belonging to the same Red{nbsp}Hat organization are able to use the linked AWS account as the {product-title} AWS billing account when creating clusters.

* If you believe that the existing account linking might not be correct, see the "My team members belong to different Red{nbsp}Hat organizations" question for tips on how you can proceed.

[id="team-members-different-rh-organizations_{context}"]
== My team members belong to different Red{nbsp}Hat organizations

* An AWS account can be connected to a single Red{nbsp}Hat account only. Any user that wants to create a cluster and benefit from the private offer granted to this AWS account needs to be in the same Red{nbsp}Hat account. This can be achieved by inviting the user to the same Red{nbsp}Hat account and creating a new Red{nbsp}Hat user.

[id="incorrect-aws-billing-account_{context}"]
== Incorrect AWS billing account was selected when creating a cluster

* If the user selected an incorrect AWS billing account, the fastest way to fix this is to delete the cluster and create a new one, while selecting the correct AWS billing account.

* If this is a production cluster that cannot be easily deleted, contact Red{nbsp}Hat support to change the billing account for an existing cluster. Expect some turnaround time for this to be resolved.