> For the complete documentation index, see [llms.txt](https://docs.tcpshield.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tcpshield.com/premium-features/nethernet.md).

# NetherNet

This page covers how to use our HTTPS signaling, to enable end to end encrypted communications for players

By default, our edge assumes HTTP signaling only for maximum compatibility and setup flexibility. While this is convenient for getting something up quickly, it comes with drawbacks. Namely, users will face an in-game warning when connecting the first time, and player facing connections will not be encrypted.

{% hint style="info" %}
Bedrock support, including certificates, is a Premium Plan only feature. To upgrade, please go to our [plans](https://panel.tcpshield.com/billing/plans) page.
{% endhint %}

To get started, first enable `nethernet` transport mode in Geyser config and restart.

```yaml
bedrock:
  # How Bedrock players can connect. Changes require a restart.
  transport: nethernet
```

By issuing, or manually uploading a certificate for your domain, our edge responds with signaling over HTTPS instead. Players then receive an encrypted connection for your Bedrock tunnel and see no in-game trust prompt as well. For managed certificates, they are issued automatically via Let's Encrypt and renewed every [64 days](https://letsencrypt.org/2026/10/07/64-day-certs) automatically.

This guide covers how to generate a managed certificate for one or more domains, so you can get up and running quickly on serving HTTPS facing connections for your players.

#### A few things to note before you begin

1. You must enable HTTPS signaling on the underlying Bedrock tunnel first before it can work. Click "Edit" next to your Bedrock tunnel and enable the "Use HTTPS Signaling" option
2. In the case you upload your own certificate, you must manage its expiry yourself. If your certificate expires, players will fall back to HTTP
3. Proxy protocol is inferred from your backend automatically. If you have it active on Geyser, our edge picks it up and uses it automatically. Ensure you add `https://tcpshield.com/v4/` to your `haproxy-protocol-whitelisted-ips` section in the Geyser config
   1. Example: `haproxy-protocol-whitelisted-ips: ["https://tcpshield.com/v4/"]`

### Step 1: Add the certificate

From the Networks section, click Bedrock, and then Certificates tab.

If you have a domain verified already, you will see it listed under "Detected domains" with an "Enable HTTPS" button. You can simply click that, and it will walk you through the flow to add the DNS records you need for a managed certificate. Otherwise, you can add a domain yourself via the "+ Add Certificate" button.

<figure><img src="https://530345640-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MWXTvAX8gueFZ5txjDV%2Fuploads%2FJxICBqpi0E2mUTYUWbKO%2Fimage.png?alt=media&amp;token=63f4caf4-fdfa-42bd-81a4-26db77e0848a" alt=""><figcaption></figcaption></figure>

When you enable HTTPS or create a certificate, the following modal will appear. If you use subdomains, we recommend choosing the first option so that it covers both your apex domains and all subdomains within it. Click continue.

<figure><img src="https://i.imgur.com/S1XZp7W.png" alt="" width="563"><figcaption></figcaption></figure>

### Step 2: Add DNS record

This DNS record's purpose is to allow Let's Encrypt to issue your managed certificate.

If you are using Cloudflare, that record will look like so in our given example. Copy the values exactly as given to you from the panel.

<figure><img src="https://530345640-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MWXTvAX8gueFZ5txjDV%2Fuploads%2FdGdAfvtVbAMhe48Eofc5%2Fimage.png?alt=media&amp;token=9c870857-c6d8-49dd-aa7d-52c4bf83bc3d" alt="" width="563"><figcaption></figcaption></figure>

Copy the **Name** and **Target** exactly as shown in the popup. The DNS record will generally look like this if not using Cloudflare:

<table><thead><tr><th width="117.0794677734375">Type</th><th width="266.0103759765625">Name</th><th>Target</th></tr></thead><tbody><tr><td>CNAME</td><td><code>_acme-challenge.example.com</code></td><td><code>&#x3C;your-cname>.acme.bedrock.tcpshield.com</code></td></tr></tbody></table>

{% hint style="info" %}
A wildcard only covers one level deep. So if using \*.example.com, it will not cover \*.eu.example.com. Create an additional for eu.example.com if you are using more than one level deep.
{% endhint %}

<figure><img src="https://i.imgur.com/y7iAtnf.png" alt="" width="563"><figcaption><p>If no DNS record exists for the ACME challenge yet, a warning will be displayed like above</p></figcaption></figure>

If everything is correct, the Status will change to "Issuing". Give it a few minutes.

<figure><img src="https://i.imgur.com/dT6BDS7.png" alt=""><figcaption></figcaption></figure>

You can also click "Check now" to force a check instead of waiting for the next automatic one. If something goes wrong, it will show Failed under the status and the reason will be displayed when you click "Instructions"

<figure><img src="https://530345640-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MWXTvAX8gueFZ5txjDV%2Fuploads%2FxAgQJ0lGmO8yr8CMQVC5%2Fimage.png?alt=media&amp;token=fa7a0357-8452-457f-a082-f21497df0944" alt=""><figcaption></figcaption></figure>

If everything is correct, the status will flip to Active, and our edge will begin serving the certificate immediately. You do not need to worry about expiration, as we automatically renew and roll over managed certificates on your behalf.

### Step 3: Enable HTTPS signaling on the tunnel

With your certificate now active, it is time to enable HTTPS signaling on all Bedrock tunnels you wish to have it active on. Head on over to the Tunnels tab on the left side (in the Bedrock section) and click edit next to the tunnel of choice.

<figure><img src="https://530345640-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MWXTvAX8gueFZ5txjDV%2Fuploads%2FfjjTIeHNwFcUqz9W1ZrS%2Fimage.png?alt=media&amp;token=96729cc8-7cac-4aba-bae0-b88660e86d12" alt=""><figcaption></figcaption></figure>

Once you click edit, there will be a single checkbox. Enable HTTPS signaling on the tunnel.

<figure><img src="https://530345640-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MWXTvAX8gueFZ5txjDV%2Fuploads%2FYUs2HsENheNYI4GKll7s%2Fimage.png?alt=media&amp;token=0a79241f-a961-4126-a076-85bc9cd93789" alt="" width="563"><figcaption></figcaption></figure>

Click Save, and you are done. You can then head over to the Certificates tab again to see how many of your tunnels have HTTPS enabled. In my case, it will show "1 of 1 active".

Players who now join by your domain now connect over a secure, encrypted connection with no untrusted certificate warning shown by the client 🎉

### Troubleshooting

In the case your certificate issuance status is stuck on "Waiting for DNS", double check that you have copied the provided values in step 2 correctly to your DNS manager. For Cloudflare, proxied status must be turned off.

A quick `dig` command can also confirm the record is created correctly

```
dig +short CNAME _acme-challenge.example.com
```

You should see an output such as `your-acme-value.acme.bedrock.tcpshield.com.`&#x20;

You can click "Check now" as many times in the process via the table to force a re-check. Once a certificate is Active, and your Bedrock tunnel has HTTPS signaling enabled, there is nothing further to do. All player facing connections are end to end encrypted.
