# JuliaHub registration fails: Could not fetch associated GitHub/GitLab account

**URL:** <https://discourse.julialang.org/t/juliahub-registration-fails-could-not-fetch-associated-github-gitlab-account/65353>\
**Category:** Package Management\
**Created:** [July 27, 2021, 6:27am UTC](https://discourse.julialang.org/t/juliahub-registration-fails-could-not-fetch-associated-github-gitlab-account/65353 "2021-07-27T06:27:35Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![MartinOtter](https://avatars.discourse-cdn.com/v4/letter/m/87869e/32.png) [@MartinOtter](https://discourse.julialang.org/u/MartinOtter)\
**Post date:** [July 27, 2021, 6:27am UTC](https://discourse.julialang.org/t/juliahub-registration-fails-could-not-fetch-associated-github-gitlab-account/65353/1 "2021-07-27T06:27:35Z")

</div>

I tried to register new versions of my packages in Juliahub, such as [https://github.com/ModiaSim/ModiaPlot\_GLMakie.jl](https://github.com/ModiaSim/ModiaPlot_GLMakie.jl). When clicking the Submit button, I get the error message:

**Could not fetch associated GitHub/GitLab account**

Previously, this worked and I did not make any changes to my repository settings. Any help is appreciated.

Has this something to do with github OAuth access tokens? Does one need to “somewhere” set a personal access token in Juliahub?

---

<div class="post-metadata">

**Author:** ![MartinOtter](https://avatars.discourse-cdn.com/v4/letter/m/87869e/32.png) [@MartinOtter](https://discourse.julialang.org/u/MartinOtter)\
**Post date:** [July 28, 2021, 6:46am UTC](https://discourse.julialang.org/t/juliahub-registration-fails-could-not-fetch-associated-github-gitlab-account/65353/2 "2021-07-28T06:46:43Z")

</div>

Sorry. I made a stupid mistake by not logging into Juliahub via github

---

<div class="post-metadata">

**Author:** ![dfdx](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dfdx/32/120_2.png) [@dfdx](https://discourse.julialang.org/u/dfdx)\
**Post date:** [July 9, 2022, 7:55pm UTC](https://discourse.julialang.org/t/juliahub-registration-fails-could-not-fetch-associated-github-gitlab-account/65353/3 "2022-07-09T19:55:27Z")

</div>

I’m now getting the same error. I am logged into JuliaHub via Github, e.g. I can see the details of my profile in the top right menu. Tested it from Firefox on desktop and phone, as well as Chromium-based browser on desktop.

Does anyone else hit this issue?

---

<div class="post-metadata">

**Author:** ![shamazmazum](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/shamazmazum/32/25200_2.png) [@shamazmazum](https://discourse.julialang.org/u/shamazmazum)\
**Post date:** [July 14, 2022, 11:10am UTC](https://discourse.julialang.org/t/juliahub-registration-fails-could-not-fetch-associated-github-gitlab-account/65353/4 "2022-07-14T11:10:08Z")

</div>

> [@dfdx](#):
>
> Does anyone else hit this issue?

I do

 ![20220714_14h09m45s_grim](https://global.discourse-cdn.com/julialang/original/3X/d/5/d53045ff792bb97d94bed5b8d85db913d08f5ba9.png)

---

<div class="post-metadata">

**Author:** ![henry2004y](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/henry2004y/32/9284_2.png) [@henry2004y](https://discourse.julialang.org/u/henry2004y)\
**Post date:** [July 25, 2022, 5:15pm UTC](https://discourse.julialang.org/t/juliahub-registration-fails-could-not-fetch-associated-github-gitlab-account/65353/5 "2022-07-25T17:15:41Z")

</div>

I had this issue today, and I was logged in with my GitHub account. What could go wrong?

---

<div class="post-metadata">

**Author:** ![dfdx](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dfdx/32/120_2.png) [@dfdx](https://discourse.julialang.org/u/dfdx)\
**Post date:** [July 25, 2022, 8:35pm UTC](https://discourse.julialang.org/t/juliahub-registration-fails-could-not-fetch-associated-github-gitlab-account/65353/6 "2022-07-25T20:35:25Z")

</div>

I’m still experiencing it, but triggering `@JuliaRegistrator` like [this](https://github.com/dfdx/Umlaut.jl/issues/13) works fine so far.