Could not connect to ubuntu.vargonen.com:80 (178.18.203.35), connection timed out

Hi guys, been having this problem for some time and I really do not know what to do to fix it.

Is there a command, or two, that I can copy and paste into the terminal to fix it?

Could not connect to ubuntu.vargonen.com:80 (178.18.203.35), connection timed out
Reading package lists... Done
W: GPG error: http://deb.volian.org/volian scar InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A87015F3DA22D980
E: The repository 'http://deb.volian.org/volian scar InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Thanks in advance.

It looks like the Repo isn't set up right. It seems that the Signing Key for the Repo is missing. I don't know what Repo You have added but I would suggest to take a second Look at the Instructions from it.

I formatted the O.P. slightly.

You can add the missing GPG key.
First see if you have the keyrings directory:

ls /etc/apt/keyrings

If you get any output, you do. If you have no output, make the directory.

sudo mkdir -p /etc/apt/keyrings

Place the key
curl -fsSL https://deb.volian.org/volian/scar.key | gpg --dearmor | sudo tee /etc/apt/keyrings/volian.gpg > /dev/null

Correct the source to include the key reference:

sudo nano /etc/apt/sources.list.d/volian.list

Replace the line deb http://deb.volian.org/volian scar main with:
deb [signed-by=/etc/apt/keyrings/volian.gpg] http://deb.volian.org/volian scar main

Tap ctl+o to overwrite, then enter key to save current configuration. Tap ctl+x to exit the editor.
Now, run

sudo apt update

1 Like

Thank you @Ponce-De-Leon and @Aravisian . I'm in the middle of moving house, that's why I haven't been back on here....

@Ponce-De-Leon , I've not knowingly added or changed a repository. I do an apt update and if it looks OK I upgrade.

@Aravisian, I will try what you suggest, thank you.

1 Like

I'm doing something wrong and stupidly I've closed the terminal without copying the warning. It said something about "illegal use of curl" but I don't remember what.

EDIT: I can try Timeshift, is that right? I'll have a go tomorrow. I have another mini tower PC on Zorin, so I have another machine as a backup.

As always, I appreciate the advice, sorry I couldn't follow it correctly.

Maybe try without sudo tee if it is causing permission issues...
curl -fsSL https://deb.volian.org/volian/scar.key | gpg --dearmor | sudo install -o root -g root -m 644 /dev/stdin /etc/apt/keyrings/volian.gpg

1 Like

It seems that scar has been moved and now nala.key should be used but I am not familar with this. Perhaps @Aravisian can show you the next steps.

I found this instruction on gitlab:
"The fix is simple as it uses the same key, all you have to do is go to the file in /etc/apt/sources.d/ and change the volian repo from scar to nala."

deb http://deb.volian.org/volian/ scar main

change to

deb http://deb.volian.org/volian/ nala main

2 Likes

First: I corrected Aravisian's User Name in your Comment in the last Row because there was standing:
Bildschirmfoto vom 2025-07-21 11-31-10

But this volian Repo doesn't come by default. If I understand that right from here this is for installing nala - the Front End for APT? I know it; offers a better Structure.

On Zorin 17, You be able to install nala without adding the Repo. You can install it with sudo apt install nala but it isn't the newest Version I think:

I have tried using Timeshift, going back to 2 different dates but without success.

When I tried the sudo apt update this was returned
paste:
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A87015F3DA22D980
Ign:18 http://ubuntu.vargonen.com/ubuntu jammy InRelease
Ign:18 http://ubuntu.vargonen.com/ubuntu jammy InRelease
Ign:18 http://ubuntu.vargonen.com/ubuntu jammy InRelease
Err:18 http://ubuntu.vargonen.com/ubuntu jammy InRelease
Could not connect to ubuntu.vargonen.com:80 (178.18.203.35), connection timed out
Reading package lists... Done
W: GPG error: Files... scar InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A87015F3DA22D980
E: The repository 'Files... scar InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A87015F3DA22D980
Ign:18 http://ubuntu.vargonen.com/ubuntu jammy InRelease
Ign:18 http://ubuntu.vargonen.com/ubuntu jammy InRelease
Ign:18 http://ubuntu.vargonen.com/ubuntu jammy InRelease
Err:18 http://ubuntu.vargonen.com/ubuntu jammy InRelease
Could not connect to ubuntu.vargonen.com:80 (178.18.203.35), connection timed out
Reading package lists... Done
W: GPG error: Files... scar InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A87015F3DA22D980
E: The repository 'Files... scar InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

I have used Nala in the past (on another machine) and when I had the first problem I did try to install it as typed above but it failed. I used a Chris Titus Tech tutorial, which I used before.

I do not know. I will try again with the suggestions above tomorrow and report back.

Thanks again.

You know, this is my fear about switching from Windows to Linux permanently / completely. I have been able to fix every single issue I have ever had, more than one BSofD. Made some serious changes in the registry, used all kinds of root customisations and generally tinkered with my machines.

In Linux I am lost.

At the End, You can simply delete this Repo. For this go to Software & Updates and look there in ''Other Software'' if this repo is listed. If it is, delete it. Then make a sudo apt update to refresh the Sources.

If it isn't listed, it is a bit more fiddeling. But we can make it Step by Step. First it would be good when You take a Look in /etc/apt/sources.list (this is a File) to look if it stands in this List or if You find in /ect/apt/sources.list.d (this is a Folder) a File related to it. You can post a Screenshot here.

1 Like

The error seems to be due to some change on the server for this project, not on your end. If you've already tried to remove the repository from your sources list, and add it again following the instructions from the project's site, I'd recommend reaching out to them to ask about this error.

By the way, I'm not entirely sure based on the error messages that you've provided what is the software that is causing issues. I've looked into Vargonen (some sort of VPS provider) and Volian (software development) but I've not found any instructions to add a private repository. Can you tell us the exact package that you've installed from them?

You may not have done this manually, as some packages have their own installer script that will add this for you e.g.: Google Chrome.

2 Likes

I am in full agreement with the others. I just ran an apt search nala and it is present in the Universe Repository.
I recommend removing that unreliable and balky repository entirely and then installing nala straight from the stable universe repo as is.

sudo apt install nala

I also am a nala fan.

1 Like

Thank you, thank you, thank you.

I was just about to create a Rufus bootable USB and do a fresh installation.

I know I keep saying "tomorrow", it's just that buying a house and moving into it is not easy on your own, especially when everything is being done in your "second language", which I speak reasonably well but keep getting stuck because I've never used this vocabulary before.

it's not urgent. I can do this when my mind is less distracted and I have time. I'll keep logging in to see if there are any new posts.

I really appreciate all your posts. <3

4 Likes

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.