TeamSpeak NPL Investigation Timeline

Last Updated: January 9, 2026 Anno Vanguardi

Brothers and sisters of the Vanguards, what follows is a chronicle of the long night in which our ancient Non‑Profit License was called into question. These entries record each missive sent and received, every clarification sought, and every step taken to defend the legacy of our server and the community that has gathered within its halls for more than a decade.

This is not merely a log of dates and times, but a record of intent, diligence, and persistence in the face of uncertainty. Should the Keepers ever question our lineage again, these lines will stand as proof that we met every trial with clarity, patience, and unwavering resolve.

Detailed Timeline of Events

• 2025‑12‑16 – 21:09 PST: Event – First Symptom Observed

  A user reports that the TeamSpeak server is unavailable, marking the first visible symptom of the emerging licensing/accounting issue affecting the long‑running NPL server.

• 2025‑12‑16 – 22:16 PST: Email Sent – Richard → TeamSpeak Support

  Richard reports that the long‑running Non‑Profit License (NPL) TeamSpeak server has suddenly stopped accepting connections. He explains that the logs show repeated warnings such as “license expires in 24/23/22 hours,” which is unexpected given the server’s continuous operation since the TeamSpeak 2 era. He asks whether the accounting servers are experiencing issues, whether the perpetual NPL remains valid, and whether an updated license file is required. He notes that the NPL was originally issued on 2011‑12‑17 and that the server has operated daily with minimal downtime.

• 2025‑12‑17: Event – Temporary Server Deployment

  A temporary TeamSpeak server instance is created to maintain clan communications during the NPL investigation. The server launches with default permissions, no license key, and a fresh database, confirming it is a clean emergency installation rather than a continuation of the original instance.

• 2025‑12‑17 – 05:38 PST: Email Received – Juro (TeamSpeak Support) → Richard

  Juro acknowledges the request and asks for additional proof of server usage, specifically requesting logs to verify long‑term operation under the NPL and to confirm that the server has been actively used over the years.

• 2025‑12‑18 – 17:46 PST: Email Sent – Richard → Support

  Richard replies with a ZIP file containing server logs from July 2010 through the present, demonstrating continuous operation. He reiterates that the NPL was issued in December 2011 and that the recent expiration warnings are new and unexpected. He asks whether accounting server issues or a new license file might be responsible and offers to provide any additional files, excerpts, or configuration details needed.

• 2025‑12‑19 – 02:25 PST: Email Received – Dave (TeamSpeak Support) → Richard

  Dave thanks Richard for providing the logs but notes that vonclan.net is not loading on their side. He asks whether there is still an active website for the community or any links that demonstrate the project’s online presence, as this is required under the NPL terms.

• 2025‑12‑22 – 10:00 PST: Email Sent – Richard → Support

  Richard explains that the website had been offline due to a hosting migration, but the domain remained active for email and the TeamSpeak server.

• 2025‑12‑23 – 00:26 PST: Email Received – Dave (TeamSpeak Support) → Richard

  Dave states that the absence of a functioning website violates NPL requirements and lists prohibited items associated with the license. He informs Richard that he has 10 business days to correct all issues or risk license deactivation, emphasizing the need for a proper project website and compliance with the listed restrictions.

• 2025‑12‑23 – 11:36 PST: Email Sent – Richard → Support

  Richard confirms that the website is now back online. He explains that the content is minimal but the site is publicly accessible and meets the requirement for external community presence. He asks whether this satisfies the NPL requirement or if there are specific elements that still need to be added or corrected.

• 2025‑12‑29 – 07:13 PST: Email Sent – Richard → Support

  Richard follows up regarding the 10‑business‑day correction window, noting that the request arrived during the holiday slowdown when little processing or review is likely to occur. He asks whether the window can be extended so that his changes can be properly evaluated and offers to make any additional adjustments requested.

• 2026‑01‑02 – 02:42 PST: Email Received – Dave (TeamSpeak Support) → Richard

  Dave reports that the website still appears unreachable from their side and asks whether any specific regions are being blocked in Richard’s hosting or network configuration.

• 2026‑01‑02 – 07:09 PST: Email Sent – Richard → Support

  Richard confirms that the site is online and attaches a screenshot showing it loading normally. He explains that there are no regional blocks or filters in place and that users in the United States, Ireland, and Venezuela have successfully accessed the site. He notes that the site is currently available only over HTTP, not HTTPS, and explains that attempts to reach it via HTTPS will make it appear offline. He instructs Dave to test using plain HTTP at http://www.vonclan.net and offers to run additional checks if needed.

• 2026‑01‑06 – 09:25 PST: Email Sent – Richard → Support

  Richard sends a follow‑up asking whether Dave has been able to reach the site on his end. He requests details about what Dave is seeing during his tests so that Richard can help narrow down where the problem lies.

• 2026‑01‑07 – 02:32 PST: Email Received – Dave (TeamSpeak Support) → Richard

  Dave replies that the result is unchanged and that they still cannot review the website from their side, without additional diagnostic detail.

• 2026‑01‑07 – 06:23 PST: Email Sent – Richard → Support

  Richard sends a highly detailed diagnostic email to help Support identify where the failure is occurring. He reports successful access to the site from multiple US cities (including Seattle, Chicago, Indianapolis, Moore, and Union Park) and international locations such as Dublin, Caracas, and Reykjavik. He also confirms successful Asia‑Pacific and other regional reachability using the Site24x7 global site checker. He then provides a structured set of tests for Support to run, including HTTP access checks, DNS lookups, traceroutes, TCP connectivity tests, and HTTP HEAD requests. He explains why each test matters, provides example outputs, and asks Dave to send back the results so they can pinpoint exactly where the connection is failing.

• 2026‑01‑07 – 10:10 PST: Event – HTTPS Enabled Without Certificate

  Richard opens port TCP 443 on both the Server firewall and the Network Security Group, enabling the server to respond to HTTPS requests. Because the site serves only static informational content and does not process logins, forms, or sensitive data, an SSL certificate is not required for its operation. Commercial certificates cost money, and given the nature of the site, such an expense is unnecessary. As a result, the server intentionally operates without a certificate so clients connecting via HTTPS will receive a certificate warning, but may choose to continue. This confirms that HTTPS traffic now reaches the server correctly and that the remaining browser warnings are expected behavior rather than a configuration fault.

• 2026‑01‑08 – 23:30 PST: Email Sent – Richard → Support

  Richard sends a follow‑up message to Dave asking whether he has been able to run any of the diagnostic tests previously requested. He explains that the results from those tests are essential for determining where the connection is failing on TeamSpeak’s side. Richard also informs Dave that port 443 has now been opened on both the server and the Azure firewall, allowing the site to respond to HTTPS requests. He clarifies that the site intentionally does not use an SSL certificate because it serves only static informational content, does not handle sensitive data, and purchasing a certificate would add unnecessary cost. As a result, HTTPS visitors will receive a certificate warning but may choose to continue. Richard expresses continued interest in resolving the issue and notes his curiosity about why the site remains unreachable from TeamSpeak’s environment.

• 2026‑01‑09 – 06:41 PST: Email Received – Support → Richard

  Dave from TeamSpeak Support sends a message confirming the restoration of the clan’s Non‑Profit License. He provides the renewed licensekey.dat file as an attachment and notes that TeamSpeak will periodically review license usage to ensure continued compliance with their standards. This message marks the official return of the original license and the conclusion of the investigation.

• 2026‑01‑09 – 09:50 PST: Event – Primary Server Restored

  The original TeamSpeak server is fully restored to operational status with the new NPL. All rooms, artwork, permissions, and member‑only access return to their rightful configuration. The temporary installation used during the license investigation is retired, and the clan’s voice once again flows through the true stronghold of VON.

---

Thus the record stands: each message sent, each reply received, each test proposed in defense of our claim. Whatever judgment the Keepers render, the Vanguards will know that their history was neither forgotten nor left to rumor, but written clearly in the light of truth.