Error during the installation of Neovim on the remote host

[Tonidotpy]

Describe the bug

While running the :RemoteStart command, the installation of Neovim inside the remote host fails with the following error: curl: (22) The requested URL returned error: 404

After taking a closer look at the scripts created within the remote host, I noticed that the appimage URL of Neovim v0.10.4 for Linux has changed from the previous version and as a result curl is unable to download it.

To reproduce

Use the repro.lua to reproduce the issue.
This provides me with a better chance to reproduce the issue.
This also provides a sanity check of if the issue is with the plugin or some other part of your configuration.

Steps to reproduce the behavior:

1. Run nvim -u <repro.lua>
2. Execute :RemoteStart
3. Choose Remote SSH: Set up configured SSH host
4. Choose previously configured remote connection
5. Choose Neovim version v0.10.4 to install on the remote host

Expected behavior

Installation of Neovim on the remote host terminate successfully.

Screenshot/Screencast(s)

System information

• Your local OS: Void Linux x86_64
• Local Neovim version: v0.10.4
• Remote host OS (if applicable): Rocky Linux 8.7 (Green Obsidian) x86_64
• Remote Neovim version (if applicable): v0.10.4

[aaron-r-campbell]

Issue

The issue seems to be caused by a change in Neovim's package naming scheme starting from v0.10.4. Previously, the package was named nvim.AppImage, but now it follows the format nvim-linux-.AppImage (eg. nvim-linux-x86_64.AppImage). This change causes a problem in the script on line 50 of the neovim_download.sh.

Temporary Workaround

A temporary fix is to manually update the script on the remote machine after the error occurs. You can do this by running the following command:

ssh user@host "sed -i 's|/nvim.appimage|/nvim-linux-$(uname -m).appimage|g' ~/.remote-nvim/scripts/neovim_download.sh"

Where user and host refer to your remote machine's user and address.

[melMass]

@amitds1997 any plan to make this fix in main?

EDIT: There is actually a PR fixing this from a month ago #205

[pdicerbo]

I'm facing the same issue :(
Hope that the fix will be merged soon

[udautkarsh]

Below command does not fix the problem:

ssh user@host "sed -i 's|/nvim.appimage|/nvim-linux-$(uname -m).appimage|g' ~/.remote-nvim/scripts/neovim_download.sh"

My session info:

Progress View (P)   Session Info (S)   Help (?) 

  Config

   Log path         : /home/uday/.local/state/nvim/remote-nvim.nvim.log
   Host ID          : root@sensu
   Version (Commit) : 0.3.11 (fatal: not a git repository (or any of the parent directories): .git)

  Local config

   OS             : Linux
   Neovim version : 0.11.2

  Remote config

   OS              : Linux
   Neovim version  : v0.11.2
   Connection type : ssh
   Host URI        : root@sensu
   Connection opts : <no-extra-options>
   Workspace path  : /root/.remote-nvim/workspaces/Njp5VXaH0p
   Working dir.    : <not-provided>

My local machine:
Ubuntu 24.04.2 with nvim 0.11.2 and remote os : Rocky 9.5

[abishek]

The neovim download path as well as the SHA sum retrievel format has changed it seems. Will this be fixed soon? I manged to download the file manually and bypass the remote install for now.

[bboles]

Github recently changed the SHA to be automatically calculated and provided via API:

• https://github.blog/changelog/2025-06-03-releases-now-expose-digests-for-release-assets/

This means you can get the SHA like this now:

❯ curl --silent https://api.github.com/repos/neovim/neovim/releases/tags/v0.11.3 | jq '.assets[] | select(.name == "nvim-linux-x86_64.appimage") | .digest'
"sha256:5f377dc48c49a4170bd698a80ef461a702b8ebb8b2f7ddbb776341503d36415f"

[melMass]

wow that's a fantastic news!

[matdombrock]

This issue is affecting me as well.

The workaround:

ssh user@host "sed -i 's|/nvim.appimage|/nvim-linux-$(uname -m).appimage|g' ~/.remote-nvim/scripts/neovim_download.sh"

Does not work for me.

Host system: Fedora 42
Target system: Ubuntu 24.0.4

[amitds1997]

Should be fixed by the latest commit to master. If you see any issue, please feel free to create a new one. Thanks!