Open kraabrsg opened 2 days ago
So after further research the os error 10060 is because it is blocked by the coporate firewall ( a proxy is not used here).
After talking to firewall colleaugue he informed me that there is an ip addy that is blocked because of malware infections (not sure if its from jsr.io or dl.deno.land or deno.land) https://www.virustotal.com/gui/ip-address/34.149.100.209
Which is really bad because i doubt that they will open this...
1.) The stuck download is because the coporare proxy gets a 301, is there a way to avoid that ? 2.) is there a way to say deno to use our corporate proxy, because it seems that some of theses requests are not going via our proxy, but direct instead
In Settings.json:
"http.proxy": "http://myproxy:8080",
"deno.certificateStores": ["system"],
Even when starting a deno project from scratch, using deno init
add depencies in deno.json and do deno install
with only depencies from denos std it does not work...
Thanks!
@nayeemrmn PTAL, I think we might not be respecting some settings here?
@kraabrsg Use "deno.env": { "HTTP_PROXY": "http://myproxy:8080" }
instead for now. I don't remember what the situation was for http.proxy
, if and why we don't support it..
Hi @bartlomieju , @nayeemrmn thanks for getting back on this, but this does not seem to make a difference.
I tried deno install
Deno Version: 2.1.0
One big Problem (even if this solution would work) is the ip above which is on a black list https://www.virustotal.com/gui/ip-address/34.149.100.209
I have to ask again with our firewall colleaugue to look if something has changed, but seems not... Any further ideas to track this down ?
Btw. deno looks really awesome, it would be a pitty if we could not use this...
Version: Deno x2.0.5
Hi,
sorry if i missed an issue.... We have a node project where we build several js files to run on a RHEL Linux.
The idea is to use deno to build native executeable files via crosscompile.
Now it seems as if deno could not do anything which needs to fetch files e.g.
deno install
anddeno info
wants do download from registry.npmjs.org but stucks without doing anything.I had a phone call with colleague responsible for proxy configuration and told me for which certificate i need to use on my pc to bypass issues like "local certificate errors" .
so i added the .crt file with a deno setting deno.tlsCertificate in the project and also for node via cafile=xxx in npm settings file.
Denos output:
Terminal output stuck:
package.json
So i am not sure if there is a problem with proxy(is there a checklist or something like that somewhere) , or a misconfiguration in the package.json ?
Thanks!