TSPU Filtering Disrupts Timeweb Cloud Servers: Diagnosis, CDN Failures, and Reverse Proxy Bypass
Russian hosting provider Timeweb Cloud began experiencing selective TSPU filtering in early June that prevented clients from accessing WordPress sites without a VPN. Two commercial sites hosted on the same VPS stopped opening for users in the same city and later for the administrator connecting over a wired connection.
Initial troubleshooting ruled out fail2ban, Google Captcha, registry blocks by Roskomnadzor, and judicial decisions. Competitors on other providers remained accessible, pointing to a provider-specific issue. The observed behavior showed TCP connections on port 443 establishing successfully, followed by a missing Server Hello and a 20-second timeout, while SSH on port 22 and ICMP traffic continued without loss.
The filtering proved dynamic: it initially blocked by SNI at night, later switched to IP-based blocking by midday, and intermittently relaxed in the evening. Timeweb support acknowledged the problem on June 5 in ticket 12068181, attributing it to changes in TSPU settings and noting that the issue varied by operator, region, and browser. Similar reports appeared from Beget and Selectel around the same period.
Obtaining new IP addresses proved ineffective, with filtered behavior recurring on fresh addresses. DNS record updates after IP changes also caused extended outages. Attempts to place Yandex Cloud CDN in front of the origin succeeded for static content but failed for any POST requests, returning 405 errors for wp-login.php, cart operations, and AJAX calls.
A stable workaround used a minimal nginx reverse proxy on a separate Russian cloud VPS. The configuration correctly forwards the Host header and SSL server name, supports all HTTP methods, and includes tuned proxy buffers to prevent 502 errors on large cookie responses from logged-in WordPress administrators. ACME challenge paths are explicitly proxied to allow Let's Encrypt certificate issuance, and a synchronization script copies updated certificates from the origin server.
Testing with curl --resolve allowed validation of both GET and POST functionality before DNS cutover. Additional community suggestions include disabling TLS 1.3 or requesting subnet whitelisting through legal entities, though these were not tested in this case.
Later tickets submitted to Timeweb in July received requests for mtr traces, which cannot detect selective DPI interference because the mechanism allows TCP establishment before dropping TLS packets. Support closed the tickets claiming resolution despite ongoing symptoms reported by clients.
Related articles
WebRTC IP Leaks Explained: Why Disabling the Protocol Harms Anonymity in Anti-Detect Browsers
The article from Aurorium details how WebRTC technology can leak real IP addresses even when users route traffic through proxies. It explains the peer-to-peer mechanics of WebRTC, the role of STUN servers in generating ICE candidates, and why standard TCP proxies fail to handle UDP traffic. Disabling WebRTC via flags or JavaScript extensions creates detectable anomalies that anti-fraud systems flag as non-standard environments. The recommended approach involves native emulation inside the browser kernel so that STUN requests return proxy IPs while preserving full API integrity across workers. Additional leaks through local network addresses, mDNS candidates, and IPv6 are also covered with practical verification methods using tools like BrowserLeaks and CreepJS.
Docx Anonymizer: Open-Source Chrome Extension Uses Fine-Tuned rubert-tiny2 to Anonymize Personal Data Before AI Uploads
A Russian developer has released Docx Anonymizer, a browser extension that automatically detects and replaces personal data in documents using a lightweight NER model before they reach public AI services such as ChatGPT. The tool was created to help organizations comply with Russia’s 152-FZ personal data protection law while avoiding the risks of uploading contracts and other sensitive files to cloud-based LLMs. It runs entirely locally via ONNX Runtime and WebAssembly, requires no network calls, and supports any AI chat interface. The underlying model, rubert-tiny2, was further trained through knowledge distillation on WikiANN, factRuEval, and synthetic business documents, reaching strong F1 scores for person and organization entities after int8 quantization. The extension intercepts text on the fly, performs named-entity recognition in under two seconds for typical contracts, and replaces detected entities with placeholders. The project is fully open source and designed for minimal user friction, addressing the growing problem of employees inadvertently leaking corporate and personal data to public AI platforms.
Hybrid Post-Quantum Message Sealing: X25519 + ML-KEM-1024 in Umbera Messenger with Public Rust Tests
Umbera messenger has open-sourced its cryptographic core and published seven Rust tests that anyone can run to verify its hybrid post-quantum message sealing scheme. The design combines X25519 with ML-KEM-1024 so that an attacker must break both algorithms to decrypt a message. Messages are protected by Double Ratchet for forward secrecy, sealed sender packaging, and per-message ephemeral keys derived via HKDF-SHA256 into AES-256-GCM. The relay server stores only an opaque box identifier and encrypted blob with no sender or recipient fields visible. Media calls use DTLS-SRTP end-to-end while TURN servers see only encrypted datagrams. Addresses for message boxes rotate weekly and are derived solely from the shared secret between the two parties.
Free Ad Blocker for iPhone, Android, and Desktop Uses DNS Parsing Without Libraries and Skips YouTube Influencer Ads From the First Second
A new free ad-blocking solution has been released for iPhone, Android, and desktop platforms. The tool relies on a lightweight DNS parser that operates without external libraries. It includes a dedicated mode for users who already run VPN connections. An accompanying browser extension automatically skips sponsored segments in YouTube videos, even when the advertisement begins at the zero-second mark. The developer describes the technical challenges encountered after launch and the fixes applied to maintain compatibility across operating systems. The project emphasizes user privacy by avoiding unnecessary data collection and third-party dependencies.