You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Critical] Google & GitHub Login Failing with 522 due to Incorrect account.huly.app Domain #11006
The Google and GitHub login flows are currently using the following URLs:
https://account.huly.app/auth/google
https://account.huly.app/auth/github
It looks like the primary domain has been migrated from huly.app to huly.io. If that is the case, these authentication URLs should now use account.huly.io instead of account.huly.app.
Additionally, please verify that account.huly.io is correctly configured in DNS and resolves to the appropriate server using an A, AAAA, or CNAME record.
This is based on my analysis of the issue. Please investigate and fix it as soon as possible.
changed the title [-][Critical] Google & GitHub Login Failing with 522 Due to Incorrect account.huly.app Domain[/-][+][Critical] Google & GitHub Login Failing with 522 due to Incorrect `account.huly.app` Domain[/+]on Aug 12, 2026
This looks like a DNS/availability problem of the hosted account service rather than a defect in the self-hostable codebase, so it can only be handled by the service operators. If maintainers agree, please consider closing.
@AyushChothe — as explained above, this does not look like something that can be addressed in the codebase. Could you please close this issue if you agree? If you think there is a code change needed after all, please describe what should change.
Activity
[-][Critical] Google & GitHub Login Failing with 522 Due to Incorrect account.huly.app Domain[/-][+][Critical] Google & GitHub Login Failing with 522 due to Incorrect `account.huly.app` Domain[/+]marcoslor commentedon Aug 14, 2026
Registration on huly.io is broken!
fix: resolve maintainer feedback for hcengineering#11006
fix: resolve maintainer feedback for hcengineering#11006
fix: resolve maintainer feedback for hcengineering#11006
MichaelUray commentedon Oct 20, 2026
This looks like a DNS/availability problem of the hosted account service rather than a defect in the self-hostable codebase, so it can only be handled by the service operators. If maintainers agree, please consider closing.
MichaelUray commentedon Oct 20, 2026
@AyushChothe — as explained above, this does not look like something that can be addressed in the codebase. Could you please close this issue if you agree? If you think there is a code change needed after all, please describe what should change.