Hi @atripp ,
Thanks again.

Changing the source list to:

deb [trusted=yes] https://{our-proget-server}/ debian main

at least gets rid of the error message regarding 'InRelease'.

However, we get now

Fetched 888 B in 31s (28 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
W: No Hash entry in Release file /var/lib/apt/lists/partial/repository-t.cbsp.nl_dists_debian_Release
W: Invalid 'Date' entry in Release file /var/lib/apt/lists/partial/repository-t.cbsp.nl_dists_debian_Release
W: Failed to fetch https://{our-proget-server}/dists/debian/main/binary-amd64/Packages  Connection timed out [IP: ##.##.##.## 443]
W: Some index files failed to download. They have been ignored, or old ones used instead.

So a connection timed out. The network connection should be possible (from the source machine port 443 to the proget-server IP is reachable).
However, https://{our-proget-server}/dists/debian/main/binary-amd64/Packages gives an empty page.

Do you know how to proceed from here?

Hi Alana,
Thanks for your reply. But I'm afraid I don't really understand how to fix the problem you describe (nor what an 'InRelease' endpoint is). We have tied both http and https as proget server endpoint, but neither seems to work:
"deb http://{proget-server}/ debian main" and
"deb https://{proget-server}/ debian main".

But why, when I have (as shown above) 'debian' as feed-name and 'main' as component-name, does the error message say 'debian InRelease'? Is this something we should tell apt not to do?

And still my other question remains; what URL(s) should be whitelisted to download the apt packages from the Internet?

Thanks again!

Hi,
We are trying to setup a Debian feed, as described here: https://docs.inedo.com/docs/proget-feeds-debian
After executing these commands on a client ubuntu (20.04) machine:

wget -qO - https://{proget-server}/debian-feeds/{feed-name}.pub | sudo apt-key add -

and

echo "deb http://{proget-server}/ debian main" | sudo tee /etc/apt/sources.list.d/debian.list

we get

user@proget-server:$ sudo apt update
Ign:1 https://{proget-server} debian InRelease
Get:2 https://{proget-server} debian Release [69 B]
Get:3 https://{proget-server} debian Release.gpg [819 B]
Reading package lists... Done
W: No Hash entry in Release file /var/lib/apt/lists/partial/{proget-server}_dists_debian_Release
W: Invalid 'Date' entry in Release file /var/lib/apt/lists/partial/{proget-server}_dists_debian_Release
E: The repository 'https://{proget-server} debian Release' provides only weak security information.
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.

We suspect that we have not yet whitelisted the correct URL('s) in our proxy (to connect from our proget-server to the Internet). But we can't find the URL('s) that should be whitelisted, as there is no connector for this feed that could give a clue.
What URLs should ProGet be able to reach?

Or is the error "E: The repository 'https://{proget-server} debian Release' provides only weak security information" caused by something else?

Thanks in advance!