by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Paul Broadwith
@pauby
Apologies for the slight misinformation. All my fault.
matrixbot
@matrixbot
linuturk I'm having trouble pushing a choco package to artifactory. I'm getting Error: SecureChannelFailure (The authentication or decryption has failed.) I've double checked my API key for the source, and it's good. I've confirmed that I have the ca-certificates and ca-certificates-mono packages installed, and I can see where CA certs have been imported during the install.
linuturk mono 6.8 with the latest stable build of choco
Rob Reynolds
@ferventcoder
To artifactory? I am guessing it is a cert issue but that's noted already
RB
@RedBaron2
@ferventcoder could you take a look at issue #2084
Rob Reynolds
@ferventcoder
That may be a placeholder in foss
RB
@RedBaron2
Oh! Thanks for the heads-up.
matrixbot
@matrixbot
linuturk "Rob Reynolds (Gitter)" (https://matrix.to/#/@gitter_ferventcoder:matrix.org): cert is valid and the cert chain is available to mono
matrixbot
@matrixbot
linuturk even at trace level, there's very little information about the failure. is there any way to get more details in the logs?
Rob Reynolds
@ferventcoder
The trace logs for choco push may have limited information as it passes over to nuget.core pretty quickly and there is not a lot it produces. Something is not right, I would suggest grabbing an official chocolatey build on windows and pushing to the artifactory source to rule out that aspect first.
Make sure that Windows system has all windows updates and at least .net 4.5
if you still hit an issue there, then the next step is to ensure the certificate installation is correct.
Another route is to look at artifactory and see if there is an issue there as well.
If it works once you try from that route, then it's something in the mono build/POSIX system that may be missing.
a quick search turned this up - duplicati/duplicati#2672
Rob Reynolds
@ferventcoder
All of the other findings point to something faulty in mono (older versions though). Maybe a regression has occurred? Or maybe there is some cypher missing somewhere
Good luck, its certainly an interesting challenge
matrixbot
@matrixbot
linuturk thank you, I'll take a look
KMPLSV
@kmplsv
hmm
matrixbot
@matrixbot
linuturk Seems it was related to my upgrade from xenial to bionic. rolling back solved it for now.
Rob Reynolds
@ferventcoder
Thanks!
Rob Reynolds
@ferventcoder
Thanks for the heads up
dwilliams9329
@dwilliams9329
hey all, I'm having an issue when attempting to install a specific version of visual studio 2017 professional. I'm attempting to install 15.9.15 with the command [choco install -y visualstudio2017professional --version=15.9.15.0 --package-parameters "--allWorkloads --passive --productKey * --wait"] but what's happening is I'm getting version 15.9.25. I'm installing using packer and when I look at the output, I see a manifest file being referenced (found here: https://aka.ms/vs/15/release/channel). within that manifest file, it's referencing version 15.9.25, which is the version being installed. has anyone come across this before and/or have any ideas? I'm at a bit of a standstill. any help is greatly appreciated, thank you!
Christian Bumann
@christianbumann

https://chocolatey.org/packages/VisualStudio2017Professional#versionhistory

-> see comments
->
Jakub Bereżański Nikolai
2 years ago
As stated in the release notes: "the native installer always installs the latest released Visual Studio 2017 build". This is a decision made by Microsoft. Because of that, the package version does not really matter for new installations

Christian Bumann
@christianbumann
All package parameters are passed to the Visual Studio installer, enabling full customization of the installation. The possible parameters are described here.
If I am not completely wrong you should be able to pass a different Channel uri for the installer file
dwilliams9329
@dwilliams9329
thank you! I knew I was overlooking something
There you should have a link to microsoft downloads to find old installer files... I did this last week for Vs 2019
dwilliams9329
@dwilliams9329
I'll give it a shot tomorrow! we're trying to run this all through Packer and Jenkins to be fully automated, with the end result being an AMI within AWS that we can launch EC2 instances from
thanks again for the help
Ryan
@Mibo5354
hello everyone, is chocolatey blocking VPNs? I've getting an error with upgrading packages when my VPN is on for the past month or so.
[WARN ] - Error retrieving packages from source 'https://chocolatey.org/api/v2/': Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
Rob Reynolds
@ferventcoder
Not actively. If your VPN doesn't maintain a TLS 1.2+ connection, that could be an issue @Mibo5354
Ryan
@Mibo5354
I don't think that's the issue since it only stopped working in the recent month
Rob Reynolds
@ferventcoder

It's possible that VPN IP address has been blocked by Cloudflare for strange or erratic behavior, or it was blocked at the community level due to excessive use.

There is also a high likelihood that something changed on your end somewhere.

Ryan
@Mibo5354
if it was blocked would I still be able to access the chocolatey website? I can still open it fine. Other people have the same issue so it's less likely is my end. For example https://www.reddit.com/r/Windscribe/comments/i43gec/windscribe_is_blocking_chocolatey/
Ryan
@Mibo5354
with the vpn on I can open up https://chocolatey.org/api/v2/ in chrome with no problem
Rob Reynolds
@ferventcoder

Possibly you could have some traffic blocked and still be able to browse the website, yes. That Reddit article points to a VPN type getting blocked, but not explicitly by us. Cloudflare may deem something and some kinds of traffic as a problem and block it. Opening something on a web browser versus using choco is going to have different kinds of traffic.

Fiddler can help you see the differences.

Also, not sure if this is the case for you, but almost every time someone files a blocked ip request with us and there is a corporate VPN involved, it's the VPN and not Chocolatey.org. Typically either a misconfiguration or something is being blocked on it.

HTH get you looking in the right direction - if it works when you are not on the VPN and doesn't work when you are, look for something that changed regarding the VPN in the last few weeks. You can also file a blocked IP request (contact forms on website) and we can make a determination if the IP is being blocked. That will rule out if it is coming from our side or not.

@Mibo5354 ^^ sorry forgot to tag you
Ryan
@Mibo5354
@ferventcoder thanks for the info
Ryan
@Mibo5354
After poking around with fiddler, I see it's a 504 error
Ryan
@Mibo5354
GET https://chocolatey.org/api/v2/$metadata HTTP/1.0
User-Agent: NuGet/0.10.15.0 (Microsoft Windows NT 10.0.19041.0)
Host: chocolatey.org


HTTP/1.1 504 Fiddler - Receive Failure
Date: Thu, 13 Aug 2020 01:56:09 GMT
Content-Type: text/html; charset=UTF-8
Connection: close
Cache-Control: no-cache, must-revalidate
Timestamp: 11:26:09.044

[Fiddler] ReadResponse() failed: The server did not return a complete response for this request. Server returned 7,179 bytes.
Rob Reynolds
@ferventcoder
Does your proxy cache responses?
Sorry VPN
Ryan
@Mibo5354
I don't think so
David Hekimian
@dhekimian
We've been using SonaType Nexus for quite some time and just started getting 429 Errors from https://Chocolatey.org/api/v2. If we remove the community package source, will Chocolatey still go via my Nexus mirror to pull in the latest from the community packages when they are updated?
Rob Reynolds
@ferventcoder
Yes, choco will use whatever sources it is configured with
Nexus cached repo chooses when to update as well, but my experience is that it will pull newer versions down