Back to all features
Security

Token-Free Repository URLs

Server Compass never writes a personal access token into the repository address stored on your server, so a token cannot be read out of a checkout later. Existing checkouts that still carry one are flagged, with guidance on whether to migrate the address or rotate the token.

How Token-Free Repository URLs Works

Using Token-Free Repository URLs is straightforward. Follow these simple steps to get started.

1

Connect an account normally

The token is kept by Server Compass. It is never written into the repository address stored on your server, so no checkout carries it.

2

Old checkouts are flagged

If a repository on your server still has a token in its URL, the app tells you — and separates an address that needs migrating from a token that was exposed.

3

Migrate or rotate

It walks you through replacing the address, and where the token was readable, through rotating it and confirming you revoked the old one.

4

Decide how much to trust a self-managed host

GitLab connections are HTTPS by default; plain HTTP or a self-signed certificate each need your explicit approval, remembered per account.

DIY Approach

What If You Don't Have Token-Free Repository URLs?

Before Token-Free Repository URLs, this is what server management looked like. Spoiler: it wasn't fun.

1

SSH into server

Connect to audit security.

terminal
ssh root@your-server-ip
2

Check open ports

See what's exposed.

terminal
netstat -tlnp
# Or:
ss -tlnp
# Now figure out which ports should be open
3

Review SSH config

Check security settings.

terminal
cat /etc/ssh/sshd_config | grep -E "^[^#]"
# PermitRootLogin yes  <- BAD
# PasswordAuthentication yes  <- RISKY
# Fix each one manually
4

Configure firewall

Set up UFW rules.

terminal
ufw status
ufw allow 22/tcp
ufw allow 80/tcp
ufw allow 443/tcp
ufw enable
# Lock yourself out? Hope you have console access!

Wrong rule = locked out of your server.

5

Install Fail2ban

Set up brute-force protection.

terminal
apt install fail2ban
cp /etc/fail2ban/jail.conf /etc/fail2ban/jail.local
nano /etc/fail2ban/jail.local
# Configure manually...
systemctl enable fail2ban
systemctl start fail2ban
The Easy Way

One Click > 50 Commands

Everything above in one visual interface. Token-Free Repository URLs handles the complexity so you can focus on building.

  • No SSH required
  • Guided workflows
  • Undo support
  • Multi-server management
Download Server Compass$29 • Lifetime license
Capabilities

Token-Free Repository URLs Features

Everything you need for security in one integrated tool, replacing complex CLI commands and manual configuration.

Get Started
Access tokens are never written into repository addresses on your server
Existing checkouts carrying a token are flagged for you
Migrating an address is distinguished from rotating an exposed token
Guided through replacing the address and confirming the old token was revoked
HTTPS by default for self-managed GitLab
Plain HTTP or a self-signed certificate needs explicit per-account approval
Swapping a token for one belonging to another user is refused
“Hide all data” also masks each server’s username, port, and auth type

Benefits of Token-Free Repository URLs

Server management shouldn't require a DevOps team. Token-Free Repository URLs makes professional-grade security accessible to everyone.

Proactive Protection

Token-Free Repository URLs identifies vulnerabilities before they're exploited with automated security scanning.

Visual Configuration

Token-Free Repository URLs makes firewall rules, SSH settings, and Fail2Ban configuration accessible through a GUI.

One-Click Hardening

Token-Free Repository URLs applies security best practices with a single click: disable root, change ports, enforce key auth.

Continuous Monitoring

Token-Free Repository URLs keeps watching your security posture and alerts you when new issues are detected.

Token-Free Repository URLs FAQ

Common questions about Token-Free Repository URLs in Server Compass

How do I access Token-Free Repository URLs in Server Compass?

Token-Free Repository URLs is available in the Security section of Server Compass. Simply connect to your server, navigate to Security, and you'll find Token-Free Repository URLs ready to use. No additional setup or plugins required.

Does Token-Free Repository URLs require any server-side installation?

No. Server Compass operates as a desktop application that connects to your server via SSH. Token-Free Repository URLs works through this connection without installing any agents or packages on your server (except the optional monitoring agent for resource tracking).

Is Token-Free Repository URLs included in all Server Compass plans?

Yes. Every Server Compass feature, including Token-Free Repository URLs, is included with the one-time $29 payment. There are no tier restrictions, add-ons, or per-server fees. You get all 132+ features for all your servers.

Can I use Token-Free Repository URLs with any VPS provider?

Token-Free Repository URLs works with any VPS or dedicated server that supports SSH access and Docker. This includes DigitalOcean, Hetzner, Vultr, Linode, AWS EC2, Google Cloud, Azure, and any other provider. It also works with local servers and homelab setups.

What makes Token-Free Repository URLs different from command-line alternatives?

Token-Free Repository URLs provides a visual, intuitive interface that replaces complex CLI commands and configuration files. You get real-time feedback, safety confirmations, and a consistent experience across all your servers without memorizing syntax or writing scripts.

Try Token-Free Repository URLs Today

Download Server Compass and get access to Token-Free Repository URLs along with 131 other features. One-time $29 payment. No subscriptions. No per-server fees.