Community repo for Jammy InRelease resolves to TEST-NET 203.0.113.1 — cannot update openvas-scanner

Building from Source and Advanced Topics
1

apt update fails because DNS lookups for deb.greenbone.net resolve to the TEST-NET address 203.0.113.1, and all HTTPS connections time out. Hard-coding the IP in /etc/hosts leads to a TLS certificate mismatch.

What I’ve already checked

  • DNS resolution via public resolvers (8.8.8.8, 1.1.1.1) always returns 203.0.113.1.
  • nc -vz deb.greenbone.net 443 → connection timed out
  • openssl s_client -connect deb.greenbone.net:443 → connection timed out
  • No /etc/hosts entries override the domain, and corporate DNS does not intercept it locally.
  • Imported the GPG key from https://www.greenbone.net/GBCommunitySigningKey.asc successfully, but apt update still fails on InRelease.

Questions

  1. Is the Jammy repository currently serving a placeholder at 203.0.113.1?
  2. When will the production CDN node (with a valid InRelease) be available?
  3. Is there an alternate URL or mirror list for the Community Edition APT repo?

Any guidance would be greatly appreciated—thanks in advance!

2

@Bigdo where did you find such a repo? There is no such repo, as far as I know.

Eero

3

AI hallucination maybe? This is the second time within a few weeks some one tried to use non-existing APT/Debian repositories for installing the community edition:

1 Like
4

@Bigdo could you please let us know where you got the info about the apt.greenbone.net URL from?

1 Like
5

Thanks for the quick replies! I haven’t manually added any Greenbone repository—here’s exactly what happened:
I ran “sudo apt update”
And without any prior changes to /etc/apt/sources.list***, the output included:

Ign:9 https:/deb.greenbone.net/community-edition jammy InRelease
Err:9 https:/deb.greenbone.net/community-edition jammy InRelease
Could not connect to deb.greenbone.net:443 (203.0.113.1), connection timed out

The only occurrence of deb.greenbone.net is stored in the file:

/etc/apt/sources.list.d/greenbone-community.list
PS: I removed one “/” in the Err:9 line (https:/deb.greenbone.net/community-edition jammy InRelease) so that the site wouldn’t complain about the link.

6

where did you get deb.greenbone.net source? That really does not exists

Eero

7

Here’s the deal: I didn’t modify anything myself—I inherited this project from a colleague who left the company, so he may have obtained that link from somewhere. In any case, if you have the current repository URL, could you please share it?

8

@Bigdo there is no such repo.

So you probably need to start learning from scratch and reinstall system OR buy commercial version of greenbone.

Eero

9

So here’s my question: of course I could reinstall the system, but then where would updates be pulled from? Also, if I reinstall, can I import my old scan profiles or will I have to recreate everything from scratch?

10

@Bigdo It means that if you install from source, then you need to take care of installing new version.

Or use kali linux packages.

You probably need to reconfigure all. there is way, but it requires scripting..

Eero

11

@Bigdo for exporting data, probably export from to text file (gvm-cli) and then some importing to new via gvm-cli

Eero

12

for Kali Linux instructions.

Eero

13

Hi,

there is only one single source of truth for using the Greenbone Community Edition

Other links, docs, tools, scripts, etc. are unofficially and not supported by Greenbone at all.

I am still curious where your former colleague get apt.greenbone.net or deb.greenbone.net got from.

Both URLs are not available and Greenbone doesn’t provide packages for any Linux distribution besides our own Greenbone OS.

2 Likes
14

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