How can I run Deno behind corporate proxy - deno

I'm trying to run deno on my corporate machine. So I'm behind a corporate proxy.
When I try to run a command like:
deno run https://deno.land/std/http/server.ts
I get an error saying:
Download https://deno.land/std/http/server.ts
error: error sending request for url (https://deno.land/std/http/server.ts): error trying to connect: tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)
I checked this GitHub Issue but it's still Open and without a resolution.
I also checked this GitHub Issue but without any luck.
There was a link pointing to some Manual in this GitHub Issue but it's broken.

Ah! So I got the link to the manual for proxies here. As mentioned here:
Deno supports proxies for module downloads and the Web standard fetch API.
Proxy configuration is read from environmental variables: HTTP_PROXY and HTTPS_PROXY.
In case of Windows, if environment variables are not found Deno falls back to reading proxies from registry.
So I just set the HTTP_PROXY and HTTPS_PROXY environment variables to the proxy url(with format - http://my-proxy-domain.com:PORT/) and it started working.
Hope this helps others. 🙂

Related

Ngrok can't read config for ports

So, I'm currently setting up a Raspberry Pi to be my testing server and to host code backups over SFTP(I really don't like Git). After tussling with Hamachi for a bit, I was recommended Ngrok. Installing Ngrok, I was able to open a port just fine without a config file. It was at this point that I decided that I'd want multiple ports open. I read through the documentation, and wrote this config file.
authtoken:(REDACTED)
tunnels:
httpnorm:
proto: http
addr: 80
httptest:
proto: http
addr:69420
sftp1:
proto: tcp
addr:22
sftp2:
proto:tcp
addr: 21
Now, this is a completely fine YAML file, I've even checked it for error twice, so the formatting doesn't appear to be an issue. However, upon running the command "./ngrok start -config='ngroksetup.yml' sftp1", I get the following output.
ERROR: Tunnel 'sftp1' is not defined in the config files.
ERROR: Tunnels available:
ERROR: Config files read: [ngroksetup.yml]
That isn't correct, because ngroksetup.yml(which is on the root of the filesystem) clearly has listed tunnels. Why is it incorrectly interpreting the setup file?
User error. The issue would be obvious from the get go if I had included my auth token, but I didn't want my auth token being stolen for obvious reasons. Thankfully, the way I wrote it kind of gives it away. I needed a space between the : and the auth token itself, just like how I missed the space on the (REDACTED).

Alfresco unable to connect to server http://mydomain:8080/alfresco

i am running alfresco on linux server i am able to access the files from back end but when running http://mydomain:8080/ it gives the following error
Unable to connect
Firefox can’t establish a connection to the server at mydomain:8080.
The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
tomcat is running but i still cant figure out what could be the cause of the error.
Could you take a look to a tomcat logs?. Maybe you can find more information about the issue.
Could you check compatibility of your amps files with Alfresco version?
Regards,
clv
First, try to hit the Alfresco webapp from the local server itself using curl, like:
curl -v -uadmin http://localhost:8080/alfresco
And see what comes back. If you get a 200 or a redirect, try Share next, like:
curl -v http://localhost:8080/share
If you get a 200 or a redirect then both web applications are working fine and this is due to a network connectivity problem between your client machine and the server or a firewall issue.
If curl cannot hit one of the web applications locally, you should inspect the logs ($TOMCAT_HOME/logs/catalina.out) to figure out why.
You can also "ps -ef|grep tomcat" to make sure Tomcat is actually running, and you can "netstat -atnp|grep 8080" to make sure Tomcat is listening on the port you think it is.
If all of the firewall and networking tests are fine and the logs have no clues, uninstall the AMPs one-by-one until it starts working again.

ngrok with visual studio 2017 and IIS express fails to connect

So I'm trying to setup my dev machine to be able to respond to some webhooks, as per the twilio documentation here:
https://www.twilio.com/docs/usage/tutorials/how-use-ngrok-windows-and-visual-studio-test-webhooks
I've got ngrok installed, and have the tunnel up and running, pointing at the port that is specified in visual studio. In this case, 44336.
However, if I go to visit the external URL, I get a very long load time, and eventually a 502 error. Visiting localhost works fine as expected.
So, I tried setting ngrok to point at 8080, and I get a little further along, but still no luck with the following error message in the browser.
With the first tunnel attempt, I can see the GET/ requests show up in the ngrok client, but no error. In the second attempt, I can see the 502 errors:
So I have two questions: How can I diagnose the source of the problem? And how can I setup IIS to accept connections from ngrok?
This is resolved in the latest version of ngrok (at this time 2.3.23).
A related closed issue can be referenced here: https://github.com/inconshreveable/ngrok/issues/448
You can now run:
ngrok http https://localhost:<port> -host-header="localhost:<port>"
for your example:
ngrok http https://localhost:44336 -host-header="localhost:44336"
Just go Right click on project -> Properties, and then disable ssl.

After Artifactory upgrade to 5.10.2, remote repo connections fail with Proxy Error 407

We have updated our Artifactory from 5.2.0 to 5.10.2.
Since that, all remote repository test connection failed with Proxy error 407.
The proxy is correctly set in Admin section, the Proxy has been set for all repo.
login/password are valid.
There's no log error except this one :
20180419151212|30|REQUEST|172.22.50.135|usertst|POST|/ui/admin/repositories/testremote|HTTP/1.1|400|1610
Unfortunately I can't bypass the proxy.
It used to work so I don't understand why it doesn't work anymore since the update.
This is a bug that has been reported. You may want to vote & watch the JIRA for updates.

How to set Nexus feed and src URL to https

I am new to this forum and my searches haven't found a solution to my problem.
I am having an issue with Sonatype Nexus v2.11.4-01. This is the OSS version. The repo server is behind a load balancer which is handling all the SSL and redirecting via http to the Nexus server.
I have a windows server using a chocolatey client, v0.9.9.11, configured to use the source: https://repo.agent.company.com/nexus/service/local/nuget/NuGet/
This windows server is on a network that does not allow port 80 traffic in or out. The commands choco list and choco search work correctly. However, when I try to run choco install agent -y, I get an error about not being able to get to the repo.
If I open the following in a browser: https://repo.agent.company.com/nexus/service/local/nuget/NuGet/Packages/
I see in the response:
xml:base="http://repo.agent.company.com/nexus/service/local/nuget/NuGet/"
and
src="http://repos.agent.company.com/nexus/service/local/nuget/NuGet/"
My question is, how do I get the xml:base and src URL's to have https? Wireshark has shown me that the initial communications are done via https, but the download is initiated via http, which seems to match what I am seeing in the Package URL response.
Thank you for helping.
It sounds like there is a reverse proxy of some sort running in front of Nexus?
If so, it has to be configured to set the X-Forwarded-Proto header:
https://help.sonatype.com/display/NXRM2/Installation+and+Running#InstallationandRunning-Example:ReverseProxySSLTerminationatBasePath

Resources