# Jupyter cannot find the Julia 1.11 kernel

**URL:** <https://discourse.julialang.org/t/jupyter-cannot-find-the-julia-1-11-kernel/121155>\
**Category:** New to Julia\
**Tags:** jupyter\
**Created:** [October 10, 2024, 3:05pm UTC](https://discourse.julialang.org/t/jupyter-cannot-find-the-julia-1-11-kernel/121155 "2024-10-10T15:05:10Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![vsoler](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/vsoler/32/30667_2.png) [@vsoler](https://discourse.julialang.org/u/vsoler)\
**Post date:** [October 10, 2024, 3:05pm UTC](https://discourse.julialang.org/t/jupyter-cannot-find-the-julia-1-11-kernel/121155/1 "2024-10-10T15:05:10Z")

</div>

There are some posts concerning the upgrade to version 1.11 with juliaup, but I cannot solve a problem that I have with Jupyter: it cannot find the new julia kernel. I’m sorry if someone feels that my question has been answered, but I am stuck and I do not know how to move forward. Thank you for your patience.  
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

I just installed Julia by means of “juliaup”. The upgrade went fine, perfect, except that now my Jupyter notebooks cannot access the Julia 1.11 kernel.

In my Anaconda terminal I can see that version 1.11 is installed:

 ![image](https://global.discourse-cdn.com/julialang/original/3X/8/4/840992a8619fe87723c4364754cdbe18a4c7187f.png)

In Jupyterlab, the new kernel seems installed:

![image](https://global.discourse-cdn.com/julialang/original/3X/c/f/cfc04342fd0f8a0fdc122f7f0b52f3a14eabf554.png)

However, Jupyterlab cannot find it, it keeps trying to connect:

![image](https://global.discourse-cdn.com/julialang/original/3X/3/c/3cfa74d7834ecc10c562aa56a113fc0cca557683.png)

It tries to, but it never connects.

My impression is that perhaps something to do with the Windows PATH has gone wrong, but I do not know how to fix it.

Can you suggest any hints. I appreciate your patience.

---

<div class="post-metadata">

**Author:** ![stevengj](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stevengj/32/71_2.png) [@stevengj](https://discourse.julialang.org/u/stevengj)\
**Post date:** [October 10, 2024, 3:39pm UTC](https://discourse.julialang.org/t/jupyter-cannot-find-the-julia-1-11-kernel/121155/2 "2024-10-10T15:39:18Z")

</div>

> [@vsoler](#):
>
> I just installed Julia by means of “juliaup”. The upgrade went fine, perfect, except that now my Jupyter notebooks cannot access the Julia 1.11 kernel.

You need to open Julia and run

```julia
pkg> build IJulia

```

after running `juliaup` (or `add IJulia` if it is not already installed for that version, but it sounds like it’s already installed).

See [IJulia broken on update — re-build IJulia when updating Julia? · Issue #857 · JuliaLang/juliaup · GitHub](https://github.com/JuliaLang/juliaup/issues/857)

---

<div class="post-metadata">

**Author:** ![vsoler](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/vsoler/32/30667_2.png) [@vsoler](https://discourse.julialang.org/u/vsoler)\
**Post date:** [October 10, 2024, 5:58pm UTC](https://discourse.julialang.org/t/jupyter-cannot-find-the-julia-1-11-kernel/121155/3 "2024-10-10T17:58:47Z")

</div>

I already used …

```julia
build IJulia

```

.  
but jupyter does not find the kernel. I also tried …

```julia
IJulia.installkernel("Julia", "--project=@.")

```

.  
but it does not work either.

I spent the whole day with this problem, now I’m thinking of a drastic solution: perhaps I could uninstall Julia and Anaconda and re-install the again. In what order should I install them. Do you think it could work?

---

<div class="post-metadata">

**Author:** ![stevengj](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stevengj/32/71_2.png) [@stevengj](https://discourse.julialang.org/u/stevengj)\
**Post date:** [October 10, 2024, 7:17pm UTC](https://discourse.julialang.org/t/jupyter-cannot-find-the-julia-1-11-kernel/121155/4 "2024-10-10T19:17:47Z")

</div>

> [@vsoler](#):
>
> but jupyter does not find the kernel. I also tried …

If you run Jupyter from the command line, then you should see an error message about why the kernel doesn’t start.

---

<div class="post-metadata">

**Author:** ![goerz](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/goerz/32/3269_2.png) [@goerz](https://discourse.julialang.org/u/goerz)\
**Post date:** [October 10, 2024, 10:50pm UTC](https://discourse.julialang.org/t/jupyter-cannot-find-the-julia-1-11-kernel/121155/5 "2024-10-10T22:50:50Z")

</div>

Try `jupyter kernelspec list` on the command line, and see if that shows the kernels installed by IJulia

---

<div class="post-metadata">

**Author:** ![ctkelley](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ctkelley/32/10684_2.png) [@ctkelley](https://discourse.julialang.org/u/ctkelley)\
**Post date:** [October 11, 2024, 7:10pm UTC](https://discourse.julialang.org/t/jupyter-cannot-find-the-julia-1-11-kernel/121155/6 "2024-10-11T19:10:12Z")

</div>

I’m having a similar problem. I’m trying to update several notebooks to the 1.11 kernel. When I try to change the kernel from the pulldown after the notebook comes up, 1.11 shows up as an option but I get the “connection to the server could not be established” message.

I’ve done `build Julia` and the notebooks come up fine in 1.10, but I cannot change the kernel. Bug in 1.11?

---

<div class="post-metadata">

**Author:** ![stevengj](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stevengj/32/71_2.png) [@stevengj](https://discourse.julialang.org/u/stevengj)\
**Post date:** [October 11, 2024, 9:07pm UTC](https://discourse.julialang.org/t/jupyter-cannot-find-the-julia-1-11-kernel/121155/7 "2024-10-11T21:07:24Z")

</div>

Make sure that IJulia is installed in the global environment.

(1.11 notebooks work fine for me.)

---

<div class="post-metadata">

**Author:** ![ctkelley](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ctkelley/32/10684_2.png) [@ctkelley](https://discourse.julialang.org/u/ctkelley)\
**Post date:** [October 11, 2024, 10:45pm UTC](https://discourse.julialang.org/t/jupyter-cannot-find-the-julia-1-11-kernel/121155/8 "2024-10-11T22:45:00Z")

</div>

I did the nuclear option.

1. delete .julia/environments/v1.11/manifest.toml
2. delete .julia/compiled/v1.11

`] instantiate`

and nothing changed. IJulia is in the global environment. If it works for you,  
something bizarre is happening to me and I will try again when 1.11.1 comes  
out.

I also tried 1.12.Dev and got the same bad results.

---

<div class="post-metadata">

**Author:** ![kpobrien](https://avatars.discourse-cdn.com/v4/letter/k/c0e974/32.png) [@kpobrien](https://discourse.julialang.org/u/kpobrien)\
**Post date:** [October 11, 2024, 10:59pm UTC](https://discourse.julialang.org/t/jupyter-cannot-find-the-julia-1-11-kernel/121155/9 "2024-10-11T22:59:40Z")

</div>

I think the problem is the `--project=@.` option. Kernels without that connect properly, kernels with this option give a precompile error. Here is the start of the error message I get:

```julia
[Info: Precompiling IJulia [7073ff75-c697-5162-941a-fcdaad2a7d2a] 
ERROR: LoadError: ArgumentError: Package REPL does not have StyledStrings in its dependencies:
- Note that the following manifests in the load path were resolved with a different
  julia version, which may be the cause of the error. Try to re-resolve them in the
  current version, or consider deleting them if that fails:
    /home/kevin/Manifest.toml (v1.10.4)
- You may have a partially installed environment. Try `Pkg.instantiate()`
  to ensure all packages in the environment are installed.
- Or, if you have REPL checked out for development and have
  added StyledStrings as a dependency but haven't updated your primary
  environment's manifest file, try `Pkg.resolve()`.
- Otherwise you may need to report an issue with REPL
Stacktrace:
 [1] macro expansion
   @ ./loading.jl:2211 [inlined]
 [2] macro expansion
   @ ./lock.jl:273 [inlined]
 [3] __require(into::Module, mod::Symbol)
   @ Base ./loading.jl:2183
 [4] #invoke_in_world#3
   @ ./essentials.jl:1088 [inlined]
 [5] invoke_in_world
   @ ./essentials.jl:1085 [inlined]
 [6] require(into::Module, mod::Symbol)
   @ Base ./loading.jl:2176
 [7] include
   @ ./Base.jl:557 [inlined]
 [8] include_package_for_output(pkg::Base.PkgId, input::String, depot_path::Vector{String}, dl_load_path::Vector{String}, load_path::Vector{String}, concrete_deps::Vector{Pair{Base.PkgId, UInt128}}, source::String)
   @ Base ./loading.jl:2806
 [9] top-level scope
   @ stdin:4
in expression starting at /home/kevin/.julia/juliaup/julia-1.11.0+0.x64.linux.gnu/share/julia/stdlib/v1.11/REPL/src/REPL.jl:3
in expression starting at stdin:4
ERROR: LoadError: Failed to precompile REPL [3fa0cd96-eef1-5676-8a61-b3b8758bbffb] to "/home/kevin/.julia/compiled/v1.11/REPL/jl_Rt55lX".
Stacktrace:
  [1] error(s::String)
    @ Base ./error.jl:35
  [2] compilecache(pkg::Base.PkgId, path::String, internal_stderr::IO, internal_stdout::IO, keep_loaded_modules::Bool; flags::Cmd, cacheflags::Base.CacheFlags, reasons::Dict{String, Int64})
    @ Base ./loading.jl:3089
  [3] (::Base.var"#1081#1082"{Base.PkgId})()
    @ Base ./loading.jl:2477
  [4] mkpidlock(f::Base.var"#1081#1082"{Base.PkgId}, at::String, pid::Int32; kwopts::@Kwargs{stale_age::Int64, wait::Bool})
    @ FileWatching.Pidfile ~/.julia/juliaup/julia-1.11.0+0.x64.linux.gnu/share/julia/stdlib/v1.11/FileWatching/src/pidfile.jl:95
  [5] #mkpidlock#6
    @ ~/.julia/juliaup/julia-1.11.0+0.x64.linux.gnu/share/julia/stdlib/v1.11/FileWatching/src/pidfile.jl:90 [inlined]
  [6] trymkpidlock(::Function, ::Vararg{Any}; kwargs::@Kwargs{stale_age::Int64})
    @ FileWatching.Pidfile ~/.julia/juliaup/julia-1.11.0+0.x64.linux.gnu/share/julia/stdlib/v1.11/FileWatching/src/pidfile.jl:116
  [7] #invokelatest#2
    @ ./essentials.jl:1056 [inlined]
  [8] invokelatest
    @ ./essentials.jl:1051 [inlined]
  [9] maybe_cachefile_lock(f::Base.var"#1081#1082"{Base.PkgId}, pkg::Base.PkgId, srcpath::String; stale_age::Int64)
    @ Base ./loading.jl:3613
 [10] maybe_cachefile_lock
    @ ./loading.jl:3610 [inlined]
 [11] _require(pkg::Base.PkgId, env::String)
    @ Base ./loading.jl:2473
 [12] __require_prelocked(uuidkey::Base.PkgId, env::String)
    @ Base ./loading.jl:2300
 [13] #invoke_in_world#3
    @ ./essentials.jl:1088 [inlined]
 [14] invoke_in_world
    @ ./essentials.jl:1085 [inlined]
 [15] _require_prelocked(uuidkey::Base.PkgId, env::String)
    @ Base ./loading.jl:2287
 [16] macro expansion
    @ ./loading.jl:2226 [inlined]
 [17] macro expansion
    @ ./lock.jl:273 [inlined]
 [18] __require(into::Module, mod::Symbol)
    @ Base ./loading.jl:2183
 [19] #invoke_in_world#3
    @ ./essentials.jl:1088 [inlined]
 [20] invoke_in_world
    @ ./essentials.jl:1085 [inlined]
 [21] require(into::Module, mod::Symbol)
    @ Base ./loading.jl:2176
 [22] include
    @ ./Base.jl:557 [inlined]
 [23] include_package_for_output(pkg::Base.PkgId, input::String, depot_path::Vector{String}, dl_load_path::Vector{String}, load_path::Vector{String}, concrete_deps::Vector{Pair{Base.PkgId, UInt128}}, source::String)
    @ Base ./loading.jl:2806
 [24] top-level scope
    @ stdin:4
in expression starting at /home/kevin/.julia/packages/SoftGlobalScope/u4UzH/src/SoftGlobalScope.jl:1
in expression starting at stdin:4
ERROR: LoadError: Failed to precompile SoftGlobalScope [b85f4697-e234-5449-a836-ec8e2f98b302] to "/home/kevin/.julia/compiled/v1.11/SoftGlobalScope/jl_GX7fBf".
Stacktrace:

```

---

<div class="post-metadata">

**Author:** ![kpobrien](https://avatars.discourse-cdn.com/v4/letter/k/c0e974/32.png) [@kpobrien](https://discourse.julialang.org/u/kpobrien)\
**Post date:** [October 11, 2024, 11:03pm UTC](https://discourse.julialang.org/t/jupyter-cannot-find-the-julia-1-11-kernel/121155/10 "2024-10-11T23:03:26Z")

</div>

and deleting the Manifest.toml file in the current directory resolves that error.

---

<div class="post-metadata">

**Author:** ![ctkelley](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ctkelley/32/10684_2.png) [@ctkelley](https://discourse.julialang.org/u/ctkelley)\
**Post date:** [October 11, 2024, 11:10pm UTC](https://discourse.julialang.org/t/jupyter-cannot-find-the-julia-1-11-kernel/121155/11 "2024-10-11T23:10:54Z")

</div>

That was it. Zapping Manifest.toml in the notebook directory did the job.

---

<div class="post-metadata">

**Author:** ![vsoler](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/vsoler/32/30667_2.png) [@vsoler](https://discourse.julialang.org/u/vsoler)\
**Post date:** [October 13, 2024, 9:40pm UTC](https://discourse.julialang.org/t/jupyter-cannot-find-the-julia-1-11-kernel/121155/12 "2024-10-13T21:40:30Z")

</div>

Deleting the Manifest.toml file also worked for me. I had to run Pkg.instantiate() but eventually everything went fine.

Thank you

---

<div class="post-metadata">

**Author:** ![vsoler](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/vsoler/32/30667_2.png) [@vsoler](https://discourse.julialang.org/u/vsoler)\
**Post date:** [October 13, 2024, 10:14pm UTC](https://discourse.julialang.org/t/jupyter-cannot-find-the-julia-1-11-kernel/121155/13 "2024-10-13T22:14:25Z")

</div>

Sorry to disturb you again…

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

Now that Jupyterlab connects to the Julia kernel, it is not possible to, for example, see the list of packages installed by means of “]st”. This had always worked for me.

---

<div class="post-metadata">

**Author:** ![nilshg](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nilshg/32/2283_2.png) [@nilshg](https://discourse.julialang.org/u/nilshg)\
**Post date:** [October 14, 2024, 6:29am UTC](https://discourse.julialang.org/t/jupyter-cannot-find-the-julia-1-11-kernel/121155/14 "2024-10-14T06:29:48Z")

</div>

That’s a known issue, just use the regular Pkg API (Pkg.status()) until this gets fixed

---

<div class="post-metadata">

**Author:** ![goerz](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/goerz/32/3269_2.png) [@goerz](https://discourse.julialang.org/u/goerz)\
**Post date:** [October 14, 2024, 11:17am UTC](https://discourse.julialang.org/t/jupyter-cannot-find-the-julia-1-11-kernel/121155/15 "2024-10-14T11:17:57Z")

</div>

Can you link to the issue?

---

<div class="post-metadata">

**Author:** ![nilshg](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nilshg/32/2283_2.png) [@nilshg](https://discourse.julialang.org/u/nilshg)\
**Post date:** [October 14, 2024, 12:17pm UTC](https://discourse.julialang.org/t/jupyter-cannot-find-the-julia-1-11-kernel/121155/16 "2024-10-14T12:17:56Z")

</div>

Sorry was on my phone this morning - it’s

> <https://github.com/JuliaLang/IJulia.jl/issues/1119>
>
> Already noticed this in rc3 but it's still a problem and I've just set up a comp…letely new machine so could confirm that this happens on a fresh install (Windows 11, Julia 1.11-rc4 installed through Juliaup, then just \`add IJulia; using IJulia; notebook()\` and allowing the standard install of miniconda).
> 
> Then in a notebook I do:
> 
> \`\`\`
> \] st
> \`\`\`
> 
> and get:
> 
> \`\`\`
> MethodError: no method matching do\_cmd(::IJulia.MiniREPL, ::String; do\_rethrow::Bool)
> The function \`do\_cmd\` exists, but no method is defined for this combination of argument types.
> 
> Closest candidates are:
> do\_cmd(::Pkg.REPLMode.Command, ::Any) got unsupported keyword argument "do\_rethrow"
> @ Pkg ...\\.julia\\juliaup\\julia-1.11.0-rc4+0.x64.w64.mingw32\\share\\julia\\stdlib\\v1.11\\Pkg\\src\\REPLMode\\REPLMode.jl:398
> \`\`\`
> 
> I assume this is related to the excision of Pkg?

---

<div class="post-metadata">

**Author:** ![xujc](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/xujc/32/214263_2.png) [@xujc](https://discourse.julialang.org/u/xujc)\
**Post date:** [March 11, 2025, 7:06am UTC](https://discourse.julialang.org/t/jupyter-cannot-find-the-julia-1-11-kernel/121155/17 "2025-03-11T07:06:54Z")

</div>

Deleting the `Manifest.toml` solved my problem.

I tried to open and run a notebook created several months ago. But Jupyterlab always says ‘connecting’ in the status bar for a while and then ‘disconnected’. I tried updating Julia packages, `build IJulia`, removing and installing the Julia kernel, all with no luck.

Fortunately, this issue only agonized me for twenty minutes, and I found this post. 😉