உள்ளடக்கத்திற்குச் செல்
Localtonet Localtonet டாஷ்போர்டு

இந்தப் பக்கம் இன்னும் தமிழ் மொழியில் கிடைக்கவில்லை. ஆங்கிலத்தில் காட்டப்படுகிறது.

Install Localtonet on Windows

இப்பக்கத்திற்கு உதவி
இந்தப் பக்கத்தில் 9 பிரிவுகள்
  1. Before you start
  2. Choose a build
  3. Use the app
  4. Install and open the app
  5. Sign in with your token
  6. Start a tunnel
  7. Use the console client
  8. Download and extract
  9. Start it with your token
  10. Check the session
  11. Run as a Windows service
  12. Install the service
  13. Check that it runs
  14. Service commands
  15. Update
  16. Uninstall
  17. Troubleshooting
  18. Related pages

On Windows you can use the Localtonet app from the Microsoft Store, a portable build of the same app, or the console client. The console client can also install itself as a Windows service that starts on every boot.

Before you start #

  • A Localtonet account. Create one for free if you do not have one.
  • Your AuthToken. Select Copy on the AuthToken card of the Dashboard, or copy a token from My Tokens.
  • For the Windows service: a Command Prompt or PowerShell window that runs as Administrator.

Choose a build #

BuildDownloadNotes
Microsoft Store appLocaltonet in the Microsoft StoreAn app window with a sign-in screen. Needs Windows 10 version 1809 (build 17763) or later.
Desktop app, portable ZIPx64, x86, ARM64The same app without the Store. Extract the ZIP and start the app from the extracted folder.
Console client64-bit, 32-bit, ARM64A ZIP that contains one file, localtonet.exe. This is the build that offers the service commands.

The Downloads page offers the Microsoft Store app and the three console builds under Binaries.

Use the app #

  1. Install and open the app #

    Install Localtonet from the Microsoft Store, or extract the portable ZIP and start the app. The app opens on the Sign in to Localtonet screen.

  2. Sign in with your token #

    Paste your AuthToken into the Authtoken or PIN field and select Connect. If the token is on the clipboard when the screen opens, the app fills it in for you. Instead of the token you can type the 6-digit PIN that My Tokens shows for a token. A PIN is valid for one minute.

    If the app answers Pin or authtoken is not valid., copy the token again and check that all 33 characters are there.

  3. Start a tunnel #

    After you sign in, the app lists the tunnels that run on this device. While the list says No active tunnels, create and start a tunnel in the dashboard, see Quick start. Sign Out removes the token from the app, Quit Localtonet closes it.

Use the console client #

  1. Download and extract #

    Download the ZIP for your CPU and extract it to a folder that stays in place, for example C:\Localtonet. A service that you install later starts localtonet.exe from this folder.

  2. Start it with your token #

    Open Command Prompt or PowerShell in that folder and run:

    Command Prompt
    localtonet --authtoken <YOUR_TOKEN>

    PowerShell only runs a program from the current folder when you write the path, so there the command is:

    PowerShell
    .\localtonet --authtoken <YOUR_TOKEN>

    The client stores the token locally. The next time you can start it with localtonet alone. If you start it without a stored token it asks Please Enter AuthToken or PIN.

  3. Check the session #

    The window shows Session Status: Connected above a table with one row per running tunnel: IP/Url, Protocol, Client IP, Client Port, Ping and Status. The table is empty until you start a tunnel in the dashboard. The name of your token appears below the table.

    Press Ctrl + C to stop the client. Press F12 to remove the stored token and exit.

Run as a Windows service #

A service starts Localtonet on every boot, keeps it running after you log out and does not need an open terminal. Run these commands with the console client, in Command Prompt or PowerShell that runs as Administrator.

  1. Install the service #

    Command Prompt (Administrator)
    localtonet --install-service --authtoken <YOUR_TOKEN>

    The command registers a Windows service for this token, sets its startup type to automatic and starts it right away. It answers with the name of the service:

    [CLI] Installed service 'Localtonet_<TOKEN_PREFIX>'

    <TOKEN_PREFIX> is the first 9 characters of your token. Every token gets its own service, so the other service commands need the same --authtoken to find it.

  2. Check that it runs #

    Command Prompt (Administrator)
    localtonet --status-service --authtoken <YOUR_TOKEN>

    A running service answers [CLI] Service 'Localtonet_<TOKEN_PREFIX>' status: Running. The service is also visible in services.msc under the same name, with the description Localtonet Service. In the dashboard, the token shows Online under My Tokens.

Service commands #

Add --authtoken <YOUR_TOKEN> to each command.

CommandWhat it doesNeeds Administrator
--install-serviceCreates the service with automatic startup and starts it. Windows restarts the service one minute after a failure.Yes
--start-serviceStarts the installed service, for example after you stopped it.Yes
--stop-serviceStops the service. It starts again on the next boot.Yes
--status-servicePrints the state: Running, Stopped, Installing while the service is starting, Paused, NotFound when no service exists for this token, Error or Unknown.No
--remove-serviceStops the service and deletes it.Yes

The service is installed with the options you pass together with --install-service, so add client options such as --net and --ip to that command. The options are listed in the CLI reference.

The service runs localtonet.exe from the folder it was in when you installed the service, with the token as part of its start command. Do not move or delete the file while the service is installed.

Update #

  • Microsoft Store app: the Microsoft Store updates the app.
  • Console client and portable app: download the current ZIP from the Downloads page and replace the old files. Windows does not let you replace localtonet.exe while it runs, so close the client first. If it runs as a service, run --stop-service, replace the file, then run --start-service.

localtonet --version prints the installed version. Under My Tokens, the Client column shows the version the device last reported and a Need Update badge when a newer one is available.

Uninstall #

  1. If you installed the service, remove it: localtonet --remove-service --authtoken <YOUR_TOKEN> as Administrator.
  2. To remove the stored token, start the console client and press F12.
  3. Delete the folder with localtonet.exe, or uninstall the Store app from Windows Settings.

Troubleshooting #

'localtonet' is not recognized

The terminal is not in the folder that contains localtonet.exe, or you are in PowerShell. Change to the folder first. In PowerShell, start the client as .\localtonet.

Install failed: 'Windows service installation' requires elevated (admin/root) privileges.

The terminal does not run as Administrator. Open Command Prompt or PowerShell with Run as administrator and repeat the command. --start-service, --stop-service and --remove-service answer with the same kind of message.

Install failed: Service 'Localtonet_…' already exists.

A service for this token is already installed. Check it with --status-service. To install it again, for example with other options or from another folder, run --remove-service first.

Start failed: Service could not be started

The message includes the answer of the Windows sc tool. Error 1056 means the service is already running. That is expected when you run --start-service directly after --install-service, because the install command already starts the service. Error 1060 means no service exists for this token.

Status is NotFound, but I installed the service

The service name is built from the token. If you pass a different token than the one you installed the service with, the client looks for a different service. Use the same token, or look for a service that starts with Localtonet_ in services.msc.

Service installation cannot persist proxy passwords.

You combined --install-service with --proxy-user or with a proxy URL that contains a password. A service is not installed with proxy passwords. Use --proxy env and provide the credentials in the environment of the service. See the CLI reference.

Wrong Token!

The client expects the 33-character AuthToken from My Tokens, or a 6-digit PIN that has not expired. Copy the token again and enter it at the prompt.

This token is used in another localtonet application!

Another Localtonet window on this computer already runs with the same token. Close it, or start this one with a different token. Use one running client per token.

The token stays Offline in the dashboard

Offline means the device is disconnected. Check that the client window is still open or that the service status is Running, and that the client was started with the token you are looking at.

இந்தப் பக்கம் குறித்து உதவி வேண்டுமா? சமூகத்திடம் கேளுங்கள் அல்லது ஆதரவு டிக்கெட்டைத் திறங்கள்.

ஆதரவு