If you previously connected your own subscription domain to Nodebuf, please verify ownership again and point its DNS record to the new subscription gateway. You can keep your existing dynamic subscriptions and files; there is no need to recreate them for this migration.
The new Nodebuf application is now available at nodebuf.com. Follow this guide to migrate your custom domain: open Custom domains. Your account, files and dynamic subscription addresses are retained.
You do not need to share a Cloudflare API token, DNS account password, or server password. You only need access to the DNS settings for a domain you control.
What you need to change
The new subscription gateway is ingress.nodebuf.com. Point your domain to it with a CNAME record, then add a TXT record to prove that you control the domain. After verification, Nodebuf automatically prepares and maintains the HTTPS certificate.
| Item | What to do |
|---|---|
| Your custom domain | Keep the existing subdomain, or add a new one |
| CNAME | Point it to ingress.nodebuf.com |
| Ownership verification | Add the _nodebuf TXT record shown in your account |
| Cloudflare proxy | Select DNS only, shown as a gray cloud |
| HTTPS | Wait for Nodebuf to show that HTTPS is ready |
| Existing subscriptions and files | Keep them; you do not need to recreate them |
| Addresses saved in clients | Check the complete link and preserve its path, query parameters, and access keys |
A previous Verified status records the result of the old setup. It does not replace the new verification. Even if your domain is already listed, open its card and verify it using the new DNS records. Do not delete the domain, subscription, or file before migrating.
Changing DNS for a domain that is already in use can involve a transition while DNS caches update and HTTPS is prepared. If you would prefer to test the entire process first, use a new subdomain, confirm that it works, and then update your clients.
Step 1: Find your domain in your account
- Sign in to the Nodebuf website.
- Open User space → Connections and files → Custom domains, or go directly to Custom domains.
- Find your existing domain and view its DNS settings. If it is not listed, add the subdomain you want to use, such as
sub.example.com. - Keep that page open so you can copy the CNAME and TXT values.
Enter the hostname only: for example, sub.example.com. Do not include https://, a port, /dynamic, or a complete subscription URL. Each account can currently manage up to 10 domains.
A dedicated subdomain such as sub.example.com or subscribe.example.com is the easiest choice. Using the root domain, such as example.com, can conflict with a website or mail settings. Some DNS providers also flatten root-domain CNAME records, preventing the system from checking the actual CNAME. Start with an ordinary subdomain to avoid these complications.
Step 2: Add two DNS records
The examples below assume that you own example.com and want to use sub.example.com for subscriptions. Make the changes at the service that actually hosts your DNS. If your nameservers point to Cloudflare, edit the records in Cloudflare rather than only adding them at your domain registrar.
| Type | Full record name | Value | Proxy status |
|---|---|---|---|
| CNAME | sub.example.com |
ingress.nodebuf.com |
DNS only / gray cloud |
| TXT | _nodebuf.sub.example.com |
Copy the value from your own Nodebuf page | No proxy setting required |
The TXT value belongs to your specific domain. Copy it from your own domain card. This guide does not contain a verification value that you can use. Do not copy another user's screenshot or enter the words “Copy the value” into your DNS settings.
If the DNS form asks for a short record name
Many DNS providers append the zone name automatically. When editing the example.com zone, you would usually enter:
- CNAME name:
sub; target:ingress.nodebuf.com. - TXT name:
_nodebuf.sub; value: the complete text shown by Nodebuf.
For my.sub.example.com, the names would usually be my.sub and _nodebuf.my.sub. Some providers accept full names and others expect these relative names. After saving, check the complete name shown in the record list. It must not accidentally become sub.example.com.example.com.
On a phone, you may need to scroll sideways or expand more options to see the record value and proxy status. Check the saved record list after adding each record.
Important settings for Cloudflare users
Set this subscription subdomain to DNS only, with a gray cloud. You can keep the existing proxy settings for your main website and other subdomains.
Nodebuf checks the CNAME and its final public DNS addresses. An orange cloud, another CDN, or an unsupported proxy layer can cause verification to fail. The new setup does not require Cloudflare custom hostnames, a Tunnel, or a Cloudflare API token.
If sub.example.com already has an A, AAAA, or old CNAME record, save the old value for reference, then replace the conflicting records for that same hostname with the CNAME above. Do not remove unrelated records for the root domain, mail, or other subdomains. The TXT record uses the separate name _nodebuf.sub.example.com, so it does not conflict with the CNAME at sub.example.com.
The default TTL or Auto setting is fine. Avoid repeatedly changing the records while waiting, as that makes it harder to tell which DNS answers are still cached.
Step 3: Verify the domain and wait for HTTPS
After saving both DNS records, return to Nodebuf and click the verification button for that domain.
The system checks ownership and the gateway destination. Once those checks pass, the certificate service prepares HTTPS for your domain. Domain verification and HTTPS readiness are separate stages. Wait until the page explicitly shows that the domain is ready to use before putting it into a client. Use the refresh button to check its latest status.
DNS propagation depends on the previous TTL, your DNS provider, and caches across different networks. Certificate issuance also requires external checks, so completion is not guaranteed immediately after you click. While the page shows that HTTPS is being prepared, leave the records in place and check again later. Do not disable certificate verification in your client to bypass the wait.
Nodebuf's gateway receives the public HTTP validation request and serves HTTPS. You do not need to rent another server, open ports on your home router, or install a certificate yourself. The gateway uses port 80 for HTTP-01 validation and port 443 for HTTPS; do not put a proxy in front of it that blocks those connections. See Let's Encrypt's HTTP-01 requirements.
Keep both the CNAME and TXT records after verification. Nodebuf continues to check the DNS destination and ownership, and maintains the certificate automatically. Pointing the domain elsewhere, removing the TXT record, or removing the domain from your account can interrupt this custom gateway.
Step 4: Copy a complete subscription link and test it
Once the domain and HTTPS are ready, open the link window for your dynamic subscription, file, or site short link. Select your custom domain and copy the complete generated address.
The custom domain changes the site portion at the beginning of a supported link. The following URLs are structural examples only. YOUR_PATH and YOUR_KEY are placeholders, not working credentials:
Original: https://nodebuf.com/dynamic?path=YOUR_PATH&security=YOUR_KEY&type=clash
Custom: https://sub.example.com/dynamic?path=YOUR_PATH&security=YOUR_KEY&type=clash
Preserve the full path and query string, especially path, security, and type. For static files, keep the file ID and access token. Repository subscriptions need their original signatures, and site short links need their original codes.
Migration does not automatically edit addresses already saved in your clients. If you keep the same custom domain, refresh the subscription in a client and check its content. If you choose a different hostname, replace the old subscription URL with the new complete URL. Do not replace it with the domain's homepage.
Test in one client first: check that it downloads the subscription, that the node count looks reasonable, and that the output format matches the client. Then update your other devices. The original main-site links remain available; a custom domain is an additional gateway. Keep a safe copy of your original complete link.
Which links can use your domain?
A custom domain serves resources owned by the account that owns the domain. It does not give the entire Nodebuf website a different hostname.
| Content | Supported? | Details |
|---|---|---|
Dynamic subscriptions at /dynamic |
Yes | Original paths, keys, and ownership checks still apply |
User file preview and download links at /files/… |
Yes | Original file IDs, tokens, and access limits remain in place |
Repository-forwarded subscriptions at /sub-file/… |
Yes | Original signatures and repository access rules still apply |
Site short links at /jump/… |
Yes | Only short links owned by the account; their targets must still pass the original checks |
| Homepage, tools, articles, sign-in, user space, or administration | No | Use the Nodebuf main site |
| Another user's subscription or file | No | Possessing their full link does not let you serve it through your domain |
| Temporary files or shares without persistent account ownership | No | Use their original generated addresses |
Third-party tt.vg short links |
Domain replacement is not supported | This hostname belongs to an external service |
If you open https://sub.example.com/ and see a notice that the domain is only for subscriptions, that is an explanation of its scope. It does not by itself indicate a broken subscription. Test with a real subscription URL, including its full path and parameters. Sign in, edit subscriptions, and manage files on the Nodebuf main site.
Custom domains do not remove subscription keys, file tokens, device limits, or account permissions. A complete subscription URL may still contain access credentials. Share it only with your own clients and people you trust, and remove credentials from public screenshots or support posts.
Troubleshooting
The TXT record cannot be found, or ownership verification fails
Check that its complete name is _nodebuf.YOUR_SUBSCRIPTION_DOMAIN. For sub.example.com, it must be _nodebuf.sub.example.com, not _nodebuf.example.com.
Confirm that you copied the entire value from the correct domain in the correct account. Check for extra spaces, line breaks, or manually added quotation marks. DNS dashboards sometimes display TXT values in quotes automatically; you generally do not need to type those display quotes again. If you just saved the record, allow cached DNS answers to update before verifying again.
The CNAME does not match or does not point to the gateway
The target must be ingress.nodebuf.com, without https://. Do not keep the old destination or point it to the main website hostname. In Cloudflare, this record must use the gray cloud.
Check for conflicting A, AAAA, old CNAME, or DNS routing records that might still return the previous address in some locations. Use the CNAME shown in the management page rather than manually entering the server IP. This also allows future gateway changes without requiring you to update an IP address yourself.
Verification passes, but HTTPS does not become ready
Wait briefly, refresh the status, and confirm that the DNS records have not changed again. If it continues to fail, check whether a CDN, forwarding service, or security rule is intercepting requests before they reach the Nodebuf gateway.
CAA restrictions, DNSSEC problems, or invalid authoritative DNS responses can also interfere with certificate issuance. Keep your existing security settings and ask your DNS provider or Nodebuf support to identify the cause. Where Let's Encrypt must be permitted, its CAA identifier is letsencrypt.org. Do not add CAA at the same hostname as an existing CNAME, or remove all CAA records as a troubleshooting shortcut. CAA checks can follow the CNAME target, so the actual DNS chain matters. See the official CAA explanation.
For support, provide the custom hostname, the displayed status, and the approximate time you tried. Do not send subscription keys, complete file tokens, account passwords, or DNS API tokens.
A browser reports a certificate mismatch, or a client cannot update
Confirm that the domain page shows HTTPS as ready, the URL starts with https://, the hostname is spelled correctly, and no extra port was added. After a DNS change, a device or network may still cache the previous answer. Retry later or check from another network. Do not ignore certificate warnings or disable TLS verification.
If HTTPS works but access is denied, confirm that the resource belongs to the same account as the domain, the full path and all query parameters were preserved, and the domain is still bound to that account. A scope notice at the domain's root is different from an error on an actual subscription URL.
Will old links still work after the DNS change?
Configuring a custom domain does not delete the original main-site URLs. How quickly an existing custom hostname switches depends on DNS caches, gateway verification, and HTTPS readiness. Test the new gateway before arranging client updates. The main website now runs the new application, but each custom domain still needs its DNS, ownership and HTTPS checks. A retained VERIFIED status alone does not mean that the new gateway is ready.
Migration checklist
- Find or add the correct domain in your own Nodebuf account. Keep the original subscriptions and files.
- Point the CNAME to
ingress.nodebuf.com. Use the gray cloud in Cloudflare and remove conflicts for that hostname only. - Match the complete
_nodebufTXT name and value to your management page. - Complete domain verification and wait until HTTPS is explicitly ready.
- Test a complete subscription URL, preserving its path, keys, tokens, and short-link code.
- Update clients and any other devices that need the new address.
- Keep the CNAME and TXT records in place and let the system maintain the certificate.
Finally, DNS-only routing does not consume Cloudflare custom-hostname quota, but it does publicly expose the IP address returned for the gateway. It should not be treated as a way to hide the server. You maintain your DNS records and subscription links; Nodebuf maintains the gateway service, certificates, and main-site protection.