How to install ngrok linux

Linux

ngrok allows you to create secure ingress to any app, device, or service without spending hours learning arcane networking technologies. You can get started with a single command or a single line of code.

What is ngrok? ngrok is an ingress-as-a-service platform that removes the hassle of getting code online from developers’ plates by decoupling ingress from infrastructure with one line of code, all without provisioning proxies or VPNs.

In this guide, we’ll walk you through the process of installing the ngrok agent on a remote Linux device, ensuring the agent runs integrated into your operating system, restricting traffic to trusted origins, and integrating traffic events with your preferred logging tool.

Step 1: Install the ngrok Agent​

To download and install the ngrok agent on your remote Linux device, follow these steps:

1. Open a terminal into your remote Linux device.
2. Download the latest ngrok binary for your Linux distribution. You can find the correct binary on our ngrok download page: Select your operating system, select the version, and copy the link that appears in the Download button. Below is an example for x86-64:

wget https://bin.equinox.io/c/bNyj1mQVY4c/ngrok-v3-stable-linux-amd64.tgz 

1. Unzip the downloaded file and move it to a directory in your PATH. Below is an example for /usr/local/bin :

sudo tar xvzf ./ngrok-v3-stable-linux-amd64.tgz -C /usr/local/bin 

1. Now that you have installed ngrok on your Linux device, link it to your ngrok account by using your authtoken:

ngrok authtoken NGROK_AUTHTOKEN 

Note: Replace NGROK_AUTHTOKEN with your unique ngrok authtoken found in the ngrok dashboard.

Step 2: Enable SSH access​

To enable remote SSH access to your device via ngrok:

1. Test that the ngrok agent is configured correctly by starting a TCP tunnel on your remote device. Note: If you get an error, ensure your authtoken is configured correctly.

1. The ngrok agent assigns you a TCP address and port. Use these values to test the SSH access via ngrok by running the following command from another server or from a desktop.

ssh -p NGROK_PORT USER@NGROK_TCP_ADDRESS 

Note: Replace the variables in the command line with the following:

• NGROK_PORT: The port number of the ngrok agent (i.e. if the agent shows tcp://1.tcp.ngrok.io:12345 , your port number is 12345 .
• USER: A valid ssh login to access your remote device’s operating system.
• NGROK_TCP_ADDRESS: The address of the ngrok agent (i.e. if the agent shows tcp://1.tcp.ngrok.io:12345 , your TCP address is 1.tcp.ngrok.io .

Step 3: Adding IP restrictions​

Once you confirmed that you have connectivity to the device, add some security so that you are the only one who can access it.

Note: This capability requires ngrok’s IP Restrictions feature, which is only available with a paid subscription.

1. On the remote Linux device terminal, stop the ngrok process using the ctrl+c command.
2. Add an allow rule to restrict access to your Linux device to an IP address or a range of IP addresses.

ngrok tcp 22 --cidr-allow ALLOWED_IP_ADDRESS_CIDR 

Note: Replace ALLOWED_IP_ADDRESS_CIDR with the CIDR notation for the allowed IP Address(es) (i.e. 123.123.123.0/24 ).

Setting IP restrictions for the entire fleet

Alternatively, you can create an IP policy in the ngrok dashboard (under Security > IP Restrictions), and leverage the same policy to control access to your entire device fleet.

Step 4: Configure ngrok to recover on outages​

The ngrok agent works with native OS services like systemd . This helps you ensure that the ngrok service is available even after the machine restarts. Before we do this though, it’s useful to reserve a TCP address in the ngrok dashboard which allows you to reuse the same address each time the device is restarted.

1. Navigate to the ngrok Dashboard and access Cloud Edge > TCP Addresses. Create a new TCP address with a description and click Save. Your new TCP address will look something like 1.tcp.ngrok.io:12345 .

Update the ngrok config file in your Linux device to start the ngrok agent using this TCP address.

tunnels: device-ssh: proto: tcp addr: 22 remote_addr: NGROK_TCP_ADDRESS ip_restriction: allow_cidrs: - ALLOWED_IP_ADDRESS_CIDR 

Note: Make sure to replace NGROK_TCP_ADDRESS with the address you reserved earlier in the ngrok dashboard (i.e. 1.tcp.ngrok.io:12345 ) and ALLOWED_IP_ADDRESS_CIDR with the CIDR notation of the allowed IP Address(es) (i.e. 123.123.123.0/24 ).

Note: Make note of the location of the ngrok.yml file.

ngrok service install --config $HOME/.config/ngrok/ngrok.yml 

You may need to run this command using sudo depending on your system

1. Run the following command to ensure your operating system launches ngrok with the ssh ingress whenever your device starts:

You may need to run this command using sudo depending on your system

1. With ngrok running on your device, you should be able to SSH into the device using the reserved address from the dashboard.

ssh -p NGROK_PORT user@NGROK_TCP_ADDRESS 

What’s next?​

Now that your device is integrated to ngrok, you can ​​execute tasks at the ngrok dashboard to operationalize your fleet:

Logging Traffic Events from ngrok​

Each action that happens in ngrok is published as an event, and Event Subscriptions allow you to subscribe to the events that are interested in and write them to one or more destinations.

An Event Subscription is made up of a set of event sources (some of which can be filtered), and event destinations. Each subscription can send the events to one or more destinations, such as Amazon CloudWatch Logs, Amazon Kinesis (as a data stream), or Amazon Kinesis Firehose (as a delivery stream).

Event subscriptions can be configured through the ngrok Dashboard or the ngrok API.

You can also forward all or some of your traffic events from ngrok to your preferred logging tool.

Remote checks, stop, start, and updates​

ngrok provides APIs and a dashboard UI for you to monitor the health of ngrok agents running in your fleet. The interfaces also allow you to remotely stop, start, and update agents.

Источник

How to Install and Use Ngrok on Linux

Learning how to install and use ngrok on Linux gives you complete access to the World Wide Web (www). Here’s everything you need to know about the service and how to deploy it.

Ngrok is a service that allows accessing remote services over the internet without port forwarding. It primarily hosts the services in the sub-domain of ngrok. The main benefit this service offers is it allows our websites to be accessed from anywhere over the internet—without actually owning any domain name.

Developers use it to show their projects and their functionality to clients.

How to Install and Use Ngrok on Linux

Here we will discuss ngrok, a service that allows making local resources available over the internet. We will talk about its installation, configuration, and usage in the following few sections.

Usage of ngrok

You can make these resources public or share local resources like websites. For instance, if you have a local server running on Linux at loop back address http://127.0.0.1:8080, then ngrok can generate a uniform resource locator (URL) http://website.ngrok.io pointing to your loopback address (http://localhost:8080 or http://127.0.0.1:8080).

Besides the use case discussed above, there is another usage of the ngrok service. You can share your services externally over ssh. Security specialists can also test clone phishing techniques using ngrok. The ngrok command exposes local services behind NAT and firewalls to the internet via tunneling.

Источник

SalahHamza / install_ngrok.md

ngrok allows you to expose a web server running on your local machine to the internet.

wget https://bin.equinox.io/c/4VmDzA7iaHb/ngrok-stable-linux-amd64.zip

if by any chance the url has been changed go to ngrok download page and copy the url of the linux .zip file.

unzip ngrok-stable-linux-amd64.zip

in case you don’t have unzip installed, you can do that like this

NAME: ngrok - tunnel local ports to public URLs and inspect traffic DESCRIPTION: ngrok exposes local networked services behinds NATs and firewalls to the public internet over a secure tunnel. Share local websites, build/test webhook consumers and self-host personal services. Detailed help for each command is available with 'ngrok help '. Open http://localhost:4040 for ngrok's web interface to inspect traffic. EXAMPLES: ngrok http 80 # secure public URL for port 80 web server ngrok http -subdomain=baz 8080 # port 8080 available at baz.ngrok.io ngrok http foo.dev:80 # tunnel to host:port instead of localhost ngrok tcp 22 # tunnel arbitrary TCP traffic to port 22 ngrok tls -hostname=foo.com 443 # TLS traffic for foo.com to port 443 ngrok start foo bar baz # start tunnels from the configuration file VERSION: 2.2.8 AUTHOR: inconshreveable - COMMANDS: authtoken save authtoken to configuration file credits prints author and licensing information http start an HTTP tunnel start start tunnels by name from the configuration file tcp start a TCP tunnel tls start a TLS tunnel update update ngrok to the latest version version print the version string help Shows a list of commands or help for one command 

this means that ngrok is working well

1. all you need to do is specify a port where your website is servered so that you expose it to the internet. Example

passing the above command will produce this output

ngrok by @inconshreveable Session Expires 7 hours, 59 minutes Version 2.2.8 Region United States (us) Web Interface http://127.0.0.1:4040 Forwarding http://********.ngrok.io -> localhost:8000 Forwarding https://*******.ngrok.io -> localhost:8000 Connections ttl opn rt1 rt5 p50 p90 0 0 0.00 0.00 0.00 0.00 

Источник