GitHub Community
Issues setting a new account and enterprise #198693
-
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
Hi, This issue is usually related to the SSL/TLS certificate that was provisioned for the new GitHub Enterprise Cloud subdomain. A few things to check:
Regarding the account showing as a personal account: this is expected in many cases. The user who creates the enterprise may still have a personal GitHub account, while Enterprise Managed Users are provisioned separately after the enterprise is fully configured. If you cannot access the enterprise to open a support ticket, try contacting GitHub Support through the account used to create the enterprise and reference the enterprise creation confirmation email, as they can usually locate the enterprise using the account details. Could anyone confirm whether this behavior is expected during initial enterprise provisioning, or if this indicates a failed certificate setup? If this answer helps resolve the issue, I would greatly appreciate marking it as the accepted solution. Thank you for your time and assistance. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
Hi,
This issue is usually related to the SSL/TLS certificate that was provisioned for the new GitHub Enterprise Cloud subdomain.
A few things to check:
Verify that the enterprise setup has fully completed. Although the confirmation email was received, certificate provisioning and DNS propagation can sometimes take additional time before the enterprise URL becomes accessible.
Try accessing the enterprise URL from a different network (for example, a mobile hotspot) to rule out any corporate proxy, firewall, SSL inspection, or DNS caching issue.
Run the following checks:
nslookup [org-name].ghe.comping [org-name].ghe.com