Hey @mcascone, my previous comment was slightly incorrect - my testing showed that ProGet requires the first file in a Debian package to be debian-binary (see this commit I made in a project a while back).
It looks like you're able to verify such is the case on a Debian archive by running the following on a Linux system:
ar tf name-of-package.deb
And the first line in the output should be debian-binary.
I know this is an old issue (no clue if it's still relevant), but I experienced this issue with a program I was working on a while back and I thought I'd post the fix I had here:
If I recall correctly, ProGet thinks a deb is invalid when the first file in a .deb archive isn't control.tar.gz, or something like that. The main thing I remember is that I had to ensure files got added into the .deb archive in the correct order for ProGet to recognize it, and I'm assuming cargo-deb isn't doing that part correctly.
I'm pretty sure it's just due to Microsoft SQL's CLI cutting off the XML output @atripp, as the XML object would just be unfinished when viewing in my terminal.
I'm gonna whip together a quick CLI to try to pull it out programmatically later today, and then I can let you know if it all works. I'm quite confident that's what's been causing my issue though.
I'm not sure how much it'll help, but this is the specific error I get from GPG:
gpg: read_block: read error: Invalid packet
gpg: import from '/dev/stdin' failed: Invalid keyring
After some further looking it appears that the XML entries in FeedConfiguration_Xml just stop without a closing quote/bracket as well, are they supposed to?
I confirmed non of the environment variables were set @atripp, but after getting the GPG key running echo '{gpg_key}' | base64 -d | gpg --show-keys /dev/stdin is complaining about it being an invalid key.
Is the GPG key in that part of the database just in some weird format or something?
@stevedennis: I'm running ProGet through the Docker images, do you know where I could fine the config in that? I haven't been able to find it anywhere inside of my container.
Do you know where I can find the configuration file @atripp?
You mentioned that code to run too, but where should I put it if I want to run it? Is it like an extension I put in ProGet, or is it something I'd run manually on a command line?
It didn't look like there was anything in the UI to get the key out of my instance, so I started looking around in the database to see if I could find anything:
I found the Feeds table which looked like it might contain the key in the SecretKeys field, but GPG isn't recognizing that as valid key if I put it into a file.
Is there something I'm missing? I'm more than glad to do whatever I need to from the database manually if this isn't something that could be added to the UI in the near future.
I've got an APT repository on ProGet that uses a GPG key to sign the repository, but I'm needing to get the private key because I need to do some stuff with it locally.
Where can I find the GPG key at? Looking through ProGet's data directory (on a Docker setup) isn't showing any GPG files.
Hi! I wasn't sure where I could really post about this, but I thought I'd send a message here in case it was of interest to anyone:
I've made a CLI tool for ProGet, which internally is using the ProGet API. The tool can't do much right now - it can currently report status information of a server and upload .deb packages (it was a personal need).
I'm wanting to add more features, but for anyone that would enjoy using the tool, I'm wanting to know if they have any specific things they'd like added.
If there's any feedback that y'all would have, feel free to leave it in the GitHub repo :)
Cool, thanks a ton for the quick response and getting the docs fixed! I'll send something in a new message if I get any other questions.
Hi! I'm in the middle of writing up a Rust library for the ProGet API, and I noticed that the documentation for the health API isn't valid JSON.
On another note while I'm mentioning the health API - is there any documentation on what the valid values for things like serviceStatus are? I'd love to make things like that enums instead of just a string when I parse the JSON into structs, but I wasn't positive on what the valid values were.
The issue seems to be back now, would you guys be trying to get everything going again or something?
My browser doesn't appear to be redirecting HTTP to HTTPS on the website, and the errors currently appear to be coming from my HTTP requests with 404 errors. Maybe things just need to be redirected to HTTPS in the webserver config?
Both my local computer and a server that's pulling ProGet's Docker images are having trouble connecting to https://proget.inedo.com with timeout errors while making the HTTP requests.
Is this happening to anyone else?
I just went ahead and recreated the key, and everything started working fine. I'm assuming something got messed up during the upgrade then, thought I can't really guarantee anything outside of what's working now.
Yeah, this was all working before in ProGet v5. All of these issues were when I was changing things right after upgrading the other day.
Hi! This is what I have for the key's configuration:
The key is set to allow access to all feeds, so there shouldn't be any issues there.
I also tried the Pesonal format when I was testing it the other day, but I didn't get any luck out of it.
I had some automated Docker build attempt to get deployed a bit earlier as well, and those appear to have failed from an authentication issue as well. Maybe it's an issue with how I have my key set up?
I've got a feed API key set up for deployments to a PyPi feed, but I can't figure out what user I should be using.
I'm currently using the following command, but all it results in is 403s (${proget_api_key} and ${proget_server} are variables set in my deployment scripts):
twine upload -u api -p "${proget_apt_key}" --repository-url "https://${proget_server}/pypi/python/legacy" dist/*
At current (or at the time of testing about a week or two ago), ProGet only (or is appearing to) allow login cookies to persist across the current browser session, and not past things like a restart of a web browser.
This gets quite annoying, especially when I'm getting some work done and might be constantly opening and closing my web browser.
Any chance cookies could persist past the closing of my web browser?
@rhessinger It looks like I was on a wrong menu or something, and it thus wasn't showing up.
I was able to dig around a bit and found the option though.
Thanks!
I'm trying to delete packages from one of my Debian feeds, but there doesn't appear to be any button to do so (there was before).
There also used to be some options when I hovered over Manage Feeds, but those are missing now too.
I'm on 5.3.31 (Build 15).
Definitely try out @rhessinger's method - just make sure to remove the insecure-registries config after.
@Fred I've got the following configuration on my system, and it's working just fine. I'm also on Ubuntu, specifically 20.04.
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-Proto "https";
The only other proxy settings I have are proxy_pass and client_max_body_size, but those shouldn't be related.
I couldn't tell from the original post, but make sure your not connecting over http when connecting from Docker. Unless you manually specify HTTP, I'm pretty sure Docker will automatically use HTTPS though.
Hi!
determined that naming is very important when using Debian and this is how I was able to get this to work:
wget -O "{feed-name}.gpg" http://{proget-server}/debian-feeds/{feed-name}.pub && sudo apt-key add "{feed-name}.gpg"
Are you saying the file fails to get added if you save it under the filename {feed-name}.pub?
My guess is that using wget -qO -
http://{proget-server}/debian-feeds/{feed-name}.pub | sudo apt-key add -, it added the key with the name of{feed-name}.gpgor whatever extensions apt converts it to.
This adds the key in the ASCII-formatted version (which is what ProGet is using), which is just a base64-encoded version of a binary GPG key.
When using pipes (the | symbol in the above command), the filename doesn't get sent to the apt-key command, only the output of the previous command does, here being the content of the remote file wget downloaded.
apt-key supports ASCII-formatted keys though (again, which ProGet is using), so it has no problem adding it.
I imagine GPG, which APT uses for keys, is handling checking or converting the content of the key when necessary.
When you ran
echo "deb http://{proget-server}/ {feed-name} {component-name}" | sudo tee /etc/apt/sources.list.d/{proget-deb}.listwhat did your use of {proget-deb}.list? Was it your feed name?
Yep, that just saves to the feed name.
In the tee command, it should read sudo tee /etc/apt/sources.list.d/{feed-name}.list though.
More specifically, it'll create a file at /etc/apt/sources.list.d/{feed-name}.list that contains deb http://{proget-server}/ {feed-name} {component-name}.
Hope that helps! Let me know if you need any clarification.
Just noticing it now - it looks like I forgot a hyphen in the wget command right before the URL. It should look like this:
wget -qO - http://{proget-server}/debian-feeds/{feed-name}.pub | sudo apt-key add -
The previous command returns an error saying a URL wasn't specified, as I'm pretty sure wget is interpreting http://{proget-server}/debian-feeds/{feed-name}.pub as the output file.
Also - were you saying there was a place to submit PRs for stuff like this?
Just adding a side note:
Allowing the container to automatically restart would allow everything to be automated, thus preventing me having to enter into my server and manually restart the ProGet container.
Thanks!
On a side note, it looks like the wget command for the key saves the file to deb.gpg, but the add-apt command uses {feed-name}.gpg. If I'm not mistaken, add-apt should read from deb.gpg then, right?
I'm also seeing this being used, which prints to stdout, pipes to the apt-key command, and then tells apt-key to read from stdin, thus avoiding the need to write to a file at all:
wget -qO http://{proget-server}/debian-feeds/{feed-name}.pub | sudo apt-key add -
If it can influence any changes in the future, there's also this note in the manual for apt-key:
Note: Instead of using this command a keyring should be placed
directly in the /etc/apt/trusted.gpg.d/ directory with a
descriptive name and either "gpg" or "asc" as file extension.
If you were to go that route, the file would probably be placed like so (ideally with the .asc extension, as ProGet's keys are ASCII-armored):
/etc/apt/trusted.gpg.d/{feed-name}.asc
The Debian feed client configuration currently is shown as follows:
In order to actually install packages from ProGet, each client must perform the following steps:
1. Add the signing key
To add the key to apt, run the following commands:
wget -O "deb.gpg" http://{proget-server}/debian-feeds/{feed-name}.pub && sudo apt-key add "{feed-name}.gpg"
echo "deb http://{proget-server}/ {feed-name} {component-name}" | sudo tee /etc/apt/sources.list.d/{proget-deb}.list
Only the first command is used to add the key - the second command adds the repository to the system.
It should read something along the lines of this (kept the info about the two commands in one line - didn't seem to flow well with it on one command each):
1. Add the signing key and repository information
To add the repository information and signing key to your system, run the following commands:
wget -O "deb.gpg" http://{proget-server}/debian-feeds/{feed-name}.pub && sudo apt-key add "{feed-name}.gpg"
echo "deb http://{proget-server}/ {feed-name} {component-name}" | sudo tee /etc/apt/sources.list.d/{proget-deb}.list
...
2. Update apt
In order to actually install packages from a ProGet feed, the package cache must be updated by running:
sudo apt update
Thanks! Everything looks like it working fine.
Hi,
If it's not possible to restart the ProGet process(es), would the following approach work?
--restart unless-stopped Docker option.I'm wanting the processes to be killed by the container itself, without me needing to do anything. Docker would then, again, start the container back up again through the --restart unless-stopped option.
The Docker Installation Guide in the docs mention using the latest tag for pulling the image, but I've only had luck using specific versions (I get a manifest error when pulling from latest).
Looking at the Docker repository on the Inedo ProGet instance, it doesn't appear that latest tags are being published.
Is it something on my end, or are images not published under latest?
Sorry, completely forgot about checking.
Anyway, I tried checking for the status code with curl -I on the system running the ProGet image (this is where NGINX wouldn't be involved), but the same Connection reset by peer is showing up, without a status code.
What OS is your Docker engine running on?
The host system is running Ubuntu Server 20.04.
@rhessinger I haven't tried connecting from a web browser without NGINX in the way, as my setup blocks any ports besides HTTP ports (80 and 443) from leaving the machine (which is a CLI-only server). I'll try to see if I can find an error code after writing this message though.
Besides when uninstalling extensions, the issue also appeared to pop up when modifying some settings under Advanced Settings, including Web.CustomHomePageHtml and Web.HideHomePageFromAnonymousUser.
I don't know how related it is, but changing the value for the Customer Experience & Improvement Program isn't causing it to return a 502.
If it helps, I'm getting this when I run curl directly on the Docker instance (without the NGINX proxy in the way):
curl: (56) Recv failure: Connection reset by peer
I've recently gotten ProGet set up, and I'd like to mess around with some of the settings before setting up any feeds, but the error mentioned in the title keeps showing up.
The only way to fix it is to restart the Docker containers ('docker-compose down; docker-compose up -d'). If I attempt to change any settings though, the issue just pops right back up.
The issue is also present when attempting to uninstall the AWS and Azure extensions (I haven't tried the other two yet).
Anything I can try? I'm on ProGet 5.3.30 (Build 7), running behind an NGINX reverse proxy.
p.s. sorry if this is a duplicate of a ticket - I wasn't sure if it was working, as I'm on the free plan.