Skip to content
IT-Tools
Documentation

How to install IT-Tools on VPSnet

Install IT-Tools from Applications with managed HTTPS. It opens to the tool catalog — no login, owner account, or one-time credentials.

Before you start

Prerequisites

Only what you need before the install steps below — nothing repeated from the guide.

  • A VPSnet account with access to the control panel.

  • A VPS or Cloud VPS that meets the IT-Tools resource guidance on the product page.

Install guide

Install IT-Tools from the panel

Follow the Applications panel path end to end. Each step covers one action only.

  1. Choose a plan for IT-Tools

    Open the IT-Tools product page and note minimum and recommended vCPU, RAM, and disk. Order a new Cloud VPS or VPS, or use a running server that still has free capacity.

    VPSnet server plan selection before application installation
  2. Install from Applications

    In the service panel open Applications → IT-Tools → Install. Leave VPSnet address selected unless you need another mode under Advanced access. This recipe version exposes no Additional settings, Optional packs, or one-time panel credentials. Click Install — defaults are enough. If the panel shows an Application runtime setup notice, Install still proceeds — there is no extra checkbox.

    Example Applications install dialog showing access and Additional settings
  3. Open the managed HTTPS URL

    When IT-Tools exposes a web UI, VPSnet assigns a *.vpsnet.cloud hostname. A short Certificate pending state is normal while DNS and SSL finish. When the status is active, use Open URL in Applications.

    Generic illustration of application access and lifecycle controls in Applications
  4. Hash, UUID, and Base64 on your VPS

    Open IT-Tools directly — there is no sign-in or first-run wizard. Use Hash text for MD5/SHA256, UUIDs generator for a v4 id, and Base64 string encoder/decoder for a short secret. Work stays in the browser on your server.

    IT-Tools Hash text showing SHA256 for a sample string
  5. Operate from the panel

    Use Applications for restart, logs, health, update, and uninstall. Avoid editing the host Compose by hand — catalog installs are version-pinned managed recipes.

    Generic illustration of application access and lifecycle controls in Applications
Install dialog

Options in the install dialog

The Applications → Install dialog is more than a single Install button. These controls appear when the recipe supports them. Safe defaults apply if you leave optional fields unchanged.

  • Application access

    Choose how you reach the app at install time: VPSnet HTTPS (managed *.vpsnet.cloud), Private (this server only), Public IP (cleartext HTTP), Managed HTTPS on a DNS zone you own, or External HTTPS when you terminate SSL. You can change this later on the installation page.

  • Additional settings

    This recipe version exposes no customer-editable Additional settings or Optional packs. Choose Application access and confirm a runtime restart if the panel asks.

  • Runtime restart

    The first managed app on a server may need a short runtime restart. The dialog asks for confirmation. Later installs on the same server usually skip this.

Initial setup

First usage of IT-Tools

IT-Tools has no owner account or setup wizard. Open the managed URL and complete one hash, one UUID, and one Base64 encode so the install is useful, not only healthy.

  1. Hash a string you care about

    Open Hash text. Paste a token, checksum input, or password candidate. Copy SHA256 (and MD5 if you need it). This stays in your browser on your VPS instead of a public toolbox.

    IT-Tools Hash text with SHA256 filled for a sample string
  2. Generate a UUID v4

    Open UUIDs generator, keep v4 selected, copy the id, and Refresh to rotate. Use it for a database row or request identifier.

    IT-Tools UUIDs generator showing a copied v4 UUID
  3. Encode a short secret as Base64

    Open Base64 string encoder/decoder. Encode a short config fragment before pasting it into chat or tickets, then decode it again on the same page when you need the original.

    IT-Tools Base64 encoder with a sample string encoded
Configuration

All configuration variables

This recipe version exposes no customer-editable configuration fields and does not generate one-time panel credentials. Complete account setup inside the application.

This recipe version exposes no customer-editable configuration fields and does not generate one-time panel credentials. Complete account setup inside the application.

Access & account setup

How you reach the app and set up your account

This recipe does not generate one-time panel credentials. Open the application and follow its own owner setup or sign-in flow.

Requirements & compatibility

Sizing and tested targets

VPS and Cloud VPS
RequirementvCPURAMNVMe
Minimum10.5 GB5 GB
Recommended11 GB10 GB
Server typeOperating systemArchitecture
VPSAlmalinux 10x86_64
VPS and Cloud VPSAlmalinux 9x86_64
VPSCentos stream 10x86_64
VPS and Cloud VPSCentos stream 9x86_64
VPS and Cloud VPSDebian 12x86_64
VPS and Cloud VPSDebian 13x86_64
VPSRocky 10x86_64
VPS and Cloud VPSRocky 9x86_64
VPS and Cloud VPSUbuntu 22.04x86_64
VPS and Cloud VPSUbuntu 24.04x86_64
VPSUbuntu 26.04x86_64
Cloud VPSAlmalinux 8x86_64
Cloud VPSArch latestx86_64
Cloud VPSDebian 11x86_64
Cloud VPSFedora 39x86_64
Cloud VPSFedora 40x86_64
Cloud VPSOpensuse 15.5x86_64
Cloud VPSOracle 9x86_64
Cloud VPSRocky 8x86_64
Cloud VPSUbuntu 20.04x86_64
Troubleshooting

FAQ

01

Why does Applications not show a generated password?

IT-Tools has no sign-in. The panel will not invent or email an admin user. Open the managed URL and use the tools directly.

02

Open URL is disabled or still preparing.

Confirm the installation health is green and wait for managed DNS and SSL to become active. Public HTTP under Advanced access is an emergency fallback, not the normal access method.

03

Open URL still shows Certificate pending after several minutes.

Confirm the install health is green, then wait for DNS/SSL to finish. If access settings offer temporary public HTTP, you can use it only as a short workaround.

04

I need environment variables that are not in the install form.

Only customer-editable blueprint fields are exposed at install and in the table below. Remaining env belongs to the managed recipe. Custom Compose is a separate advanced option when enabled on the service.