Web Certificate
By default, TCAdmin uses a self-signed certificate for HTTPS, which causes your browser to show a security warning every time you visit the panel. This guide shows you how to replace it with a trusted certificate so the warning goes away.
An SSL certificate encrypts the connection between your browser and the TCAdmin panel, keeping your login credentials and data safe. A self-signed certificate provides encryption but isn't trusted by browsers (hence the warning). A Let's Encrypt certificate is free, trusted by all browsers, and auto-renews.
TCAdmin supports four ways to set up a trusted certificate:
| Method | Best For | Requirements |
|---|---|---|
| HTTP Validation | Most setups — fully automatic | Domain name, ports 80 & 443 open |
| DNS Validation | Servers behind firewalls or NAT | Domain name, access to DNS records |
| Custom Certificate | Using your own certificate (purchased or from another CA) | A .pfx or .p12 certificate file |
| Monitor's Certificate | Accessing the panel through your server's <name>.tca.sv hostname | The web panel and a monitor on the same server |
Before You Begin
For HTTP Validation or DNS Validation, you need:
- A domain name pointing to your server (e.g.,
panel.yourdomain.com) — set up a DNS A record that points to your server's public IP address - OR you can use TCAdmin's built-in dynamic DNS if you don't have a domain (see Dynamic DNS below)
For Custom Certificate, you just need your certificate file in .pfx or .p12 format with the private key included.
For the Monitor's Certificate, you don't need a domain; see Method 4.
Method 1: HTTP Validation
This is the simplest method. Let's Encrypt automatically verifies you own the domain by connecting to your server over HTTP.
Requirements
- Ports 80 and 443 open and accessible from the internet
- No other web server (like Apache or Nginx) running on ports 80/443, unless it forwards port 80 of your domain to the panel (the panel can sit behind IIS or another reverse proxy)
Step 1: Change TCAdmin to Use Ports 80 and 443
By default, TCAdmin runs on ports 31000/31001. Let's Encrypt requires your site to be on the standard web ports (80 for HTTP, 443 for HTTPS).
Edit the web configuration file:
- Windows
- Linux
Edit C:\Program Files\TCAdmin3\config\web\appsettings.Production.json:
{
"TCAdmin": {
"Type": "Web",
"Web": {
"Port": 80,
"SecurePort": 443,
"Prerender": true
}
}
}
Edit /opt/tcadmin3/config/web/appsettings.Production.json:
{
"TCAdmin": {
"Type": "Web",
"Web": {
"Port": 80,
"SecurePort": 443,
"Prerender": true
}
}
}
Restart the Web Service
After editing the config, restart the web service for the changes to take effect:
- Windows
- Linux
Restart-Service TCA3Web
sudo systemctl restart tca3web
Make sure ports 80 and 443 are open in your firewall. Let's Encrypt connects to port 80 to verify that you control the domain — if it can't reach your server, certificate generation will fail.
Your panel URL changes too! Instead of https://YOUR-IP:31001, you'll now access it at https://YOUR-IP (port 443 is the default HTTPS port, so you don't need to type it).
Step 2: Generate the Certificate
- Log in to your control panel
- Go to Settings > Web Certificate
- Select the HTTP Validation tab
- In the Domains field, enter your domain name (one per line if you have multiple)
- Optionally enter your Email address — Let's Encrypt will send you a reminder if your certificate is about to expire
- Check Accept terms of service (after reviewing the Let's Encrypt Terms of Service)
- Click Create
TCAdmin will:
- Create a test certificate first (using Let's Encrypt staging) to make sure everything works
- If the test passes, create the real certificate
- Automatically configure the web service to use it
The new certificate is applied immediately, with no web-service restart. The page shows "Applying the new certificate..." and then confirms.
Automatic Renewal
Let's Encrypt certificates are valid for 90 days. TCAdmin automatically renews HTTP certificates 30 days before they expire — you don't need to do anything. A renewed certificate is also applied immediately, with no web-service restart.
Method 2: DNS Validation
Use this method if your server is behind a firewall, NAT, or you can't open port 80. Instead of connecting to your server, Let's Encrypt verifies ownership by checking a DNS TXT record that you create.
Step 1: Initiate DNS Validation
- Log in to your control panel
- Go to Settings > Web Certificate
- Select the DNS Validation tab
- In the Domains field, enter your domain name (one per line if you have multiple)
- Optionally enter your Email address
- Check Accept terms of service
- Click Initiate DNS Validation
TCAdmin will display one or more DNS TXT records that you need to create:
| Field | Example |
|---|---|
| Domain | yourdomain.com |
| Record Name | _acme-challenge.yourdomain.com |
| Record Value | a1b2c3d4e5f6... (a long random string) |
Use the copy button next to each record value to copy it to your clipboard.
Step 2: Create the DNS Records
Log in to your DNS provider (e.g., Cloudflare, Namecheap, GoDaddy) and create a TXT record for each entry shown:
- Name/Host:
_acme-challenge(or the full record name shown) - Type:
TXT - Value: The record value shown in TCAdmin
DNS changes can take anywhere from a few minutes to several hours to propagate. Wait at least 5-10 minutes before proceeding to the next step. You can verify propagation using an online DNS checker or by running nslookup -type=TXT _acme-challenge.yourdomain.com.
Step 3: Complete Validation
Once the DNS records are in place, click Complete Validation in TCAdmin. It will verify the DNS records and generate your certificate.
If you need to cancel the DNS validation process (e.g., you entered the wrong domain), click Cancel and Start Over to restart.
DNS validation certificates are not automatically renewed. You will need to repeat this process before the certificate expires (90 days). The system health indicator will warn you when your certificate is approaching expiry.
Method 3: Custom Certificate
If you already have an SSL certificate (purchased from a CA or generated elsewhere), you can upload it directly.
Requirements
- Certificate must be in
.pfxor.p12format - Certificate must include the private key
- Maximum file size: 10 MB
Upload Your Certificate
- Log in to your control panel
- Go to Settings > Web Certificate
- Select the Custom Certificate tab
- Click Browse and select your
.pfxor.p12file - Enter the certificate password (if the certificate is password-protected)
- Click Upload
TCAdmin will validate the certificate, check that it contains a private key, and apply it to the web service.
Custom certificates are not automatically renewed. You will need to upload a new certificate before the current one expires. The system health indicator will warn you when your certificate is approaching expiry.
Method 4: Use the Monitor's Certificate
Every licensed server is assigned a public hostname by the TCAdmin license server, in the form <name>.tca.sv, which points to the server's public IP address. The monitor on that server automatically obtains a trusted certificate for that hostname and renews it, with no setup and no restart.
Requirements
- The web panel runs on the same server as a monitor (the usual all-in-one install)
- The monitor has already received its certificate (it checks daily, and a fresh install gets it shortly after the license is validated)
Use the Certificate
- Log in to your control panel
- Go to Settings > Web Certificate
- Select the Use the monitor's certificate option
- Click Use monitor certificate
The panel switches to the monitor's certificate and follows its renewals automatically. Open the panel through its <name>.tca.sv hostname so your browser trusts the certificate.
This method needs no port 80, no DNS records and no Let's Encrypt terms.
The option isn't shown on a web-only (standalone) panel without a monitor on the same server, or while the monitor has not yet received its certificate. If you already use your own domain, you can keep using Methods 1-3.
Dynamic DNS
If you don't have a domain name, TCAdmin offers a free dynamic DNS service. Use this as your domain:
YOUR-PUBLIC-IP.dyn.tcadmin.net
Replace dots in your IP with dashes. For example, if your IP is 203.0.113.50, use:
203-0-113-50.dyn.tcadmin.net
This works with both HTTP and DNS validation methods.
Checking Your Certificate
After setting up a certificate (using any method), the Web Certificate page shows:
| Field | What It Shows |
|---|---|
| Domain(s) | The domain name(s) the certificate was issued for |
| Expires on | When the certificate expires |
| Issued by | Who issued the certificate (e.g., Let's Encrypt, your CA) |
The system health indicator in the bottom status bar also monitors your certificate:
- Healthy — Certificate is valid with plenty of time remaining
- Degraded — Certificate expires within 20 days
- Unhealthy — Certificate has expired
Troubleshooting
"This website is not listening on port 80" warning
The web service isn't listening on port 80. This is a warning, not a block: you can still click Create, and automatic renewal still runs. It works as long as port 80 of your domain reaches this panel some other way, such as an IIS or Nginx reverse proxy or a router port forward that sends http://YOUR-DOMAIN/.well-known/acme-challenge/ to the panel's HTTP port. If nothing forwards port 80 to the panel, go back to Step 1 of HTTP Validation and change the port, or use DNS Validation instead. This only applies to the HTTP Validation method.
Certificate generation fails (HTTP Validation)
| Possible Cause | How to Fix |
|---|---|
| Port 80 not accessible | Open port 80 in your firewall. Test by visiting http://YOUR-DOMAIN — you should see the TCAdmin panel (without HTTPS). |
| Domain doesn't point to your server | Make sure your domain's DNS A record points to your server's public IP. You can check with nslookup YOUR-DOMAIN or an online DNS checker. DNS changes can take up to 24 hours to propagate, but usually take 5-30 minutes. |
| Rate limiting | Let's Encrypt limits how many certificates you can request per domain per week. If you've been testing repeatedly, wait an hour and try again. |
| Another service on port 80 | If Apache, Nginx, IIS, or another web server is using port 80, either stop it or configure it as a reverse proxy that forwards /.well-known/acme-challenge/ (or the whole site) to the panel's HTTP port. Only one service can listen on a port at a time. |
DNS validation fails
| Possible Cause | How to Fix |
|---|---|
| DNS records not propagated | Wait longer (up to a few hours) and try again. Use an online DNS checker to verify the TXT record is visible. |
| Wrong record name or value | Double-check the record name and value match exactly what TCAdmin showed. The record name should be _acme-challenge.yourdomain.com. |
| Multiple TXT records | If you have old _acme-challenge TXT records from a previous attempt, delete them before creating new ones. |
Custom certificate upload fails
| Possible Cause | How to Fix |
|---|---|
| Wrong format | The certificate must be in .pfx or .p12 format. If you have .pem or .crt files, convert them first using openssl pkcs12 -export -out cert.pfx -inkey key.pem -in cert.pem. |
| Missing private key | The .pfx file must include the private key. Re-export it with the key included. |
| Wrong password | Make sure you're entering the correct password for the .pfx file. |
| File too large | The certificate file must be under 10 MB. |
What's Next?
- Plugin Repository — import game configurations to start hosting
- Remote Server Configuration — add more servers to your setup