# More problems trying to add packages from private repos

**URL:** <https://discourse.julialang.org/t/more-problems-trying-to-add-packages-from-private-repos/69059>\
**Category:** General Usage\
**Tags:** pkg\
**Created:** [October 1, 2021, 5:05pm UTC](https://discourse.julialang.org/t/more-problems-trying-to-add-packages-from-private-repos/69059 "2021-10-01T17:05:36Z")\
**Posts on this page:** 1\
**Page:** 2

<div class="post-metadata">

**Author:** ![mkitti](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mkitti/32/12459_2.png) [@mkitti](https://discourse.julialang.org/u/mkitti)\
**Post date:** [July 29, 2022, 7:27pm UTC](https://discourse.julialang.org/t/more-problems-trying-to-add-packages-from-private-repos/69059/21 "2022-07-29T19:27:29Z")

</div>

Another diagnostic would be to use

`julia ---startup-file=no` and rerun `versioninfo()`. That will completely rule out any contribution of startup.jl.

Also check your shell startup files such as .profile, .bashrc.

Edit:

In this case the issue ended up being due to a rogue VSCode-Julia extension setting. To resolve, clear the “Package Server” setting for the Julia extension within VSCode.

[![](https://global.discourse-cdn.com/julialang/original/3X/b/3/b314e023929f7a08472b7180a5ffa69b9b0ba8ab.png) ](https://global.discourse-cdn.com/julialang/original/3X/b/3/b314e023929f7a08472b7180a5ffa69b9b0ba8ab.png)

See here for more details:

> **[Bash Startup Files (Bash Reference Manual)](https://www.gnu.org/software/bash/manual/html_node/Bash-Startup-Files.html)**
>
> Bash Startup Files (Bash Reference Manual)

Having an incorrect JULIA\_PKG\_SERVER will make it challenging to get new packages.

[Previous page](https://discourse.julialang.org/t/more-problems-trying-to-add-packages-from-private-repos/69059.md?page=1)