Issues setting a new account and enterprise

[marcwoosnam]

🏷️ Discussion Type

Bug

Body

Hey,

I'm hoping i can get some help with a rather weird issue.

My org has never used github before, i setup a new enterprise and completed the wizard, received the email confirming that it has been built but when i click the link to set an admin password i received this:

[org name].ghe.com normally uses encryption to protect your information. When Chrome tried to connect to [org name].ghe.com this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be [org name].ghe.com or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Chrome stopped the connection before any data was exchanged.

You cannot visit [org name].ghe.com right now because the website uses HSTS. Network errors and attacks are usually temporary, so this page will probably work later.

I've tried different browsers but no change.

Also when i login to the account that i did setup during the process it shows as a personal account (even though i selected enterprise with managed users and not personal accounts)

Can anyone please help? i can't raise a support ticket as i can't login to the enterprise

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐

[DevZ44d]

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:

1. 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.

2. 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.

3. Run the following checks:

   • nslookup [org-name].ghe.com
   • ping [org-name].ghe.com
   • Check the SSL certificate presented by the site using an online SSL checker.

4. If the certificate appears invalid or does not match the *.ghe.com domain, this is likely a provisioning issue on GitHub's side and will require intervention from GitHub Support.

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.