Do you have an application spread across hundreds of client devices? Or a fleet of IoT sensors sending telemetry? Sooner or later the question arises: “What’s actually happening over there?” And right after it — “How do I collect logs without bankrupting myself on Splunk or Datadog?”

If your clients can send HTTP requests, you already have ninety percent of the solution. HTTP(S) is a universal and firewall-friendly protocol. All we need is a listener (endpoint) that will accept these logs.

Jitsi Meet is an open videoconferencing platform that easily integrates with Active Directory (AD). Such integration allows using corporate accounts for login, simplifying administration and improving security. In this guide we’ll go through how to connect Jitsi Meet (in Docker) to AD based on Windows Server 2016, and show proven debugging methods that help avoid common errors.

Important: using LDAP without encryption is insecure. For testing this is acceptable, but in production you must use LDAPS (port 636) with valid certificates.

Read more

How to run Jitsi Meet (Docker) behind an Nginx Reverse Proxy

In the previous article we deployed a basic Jitsi Meet server using Docker.
This is a great way to quickly start video conferencing, but in production a Jitsi server often needs to run on the same host where other web applications are already running.
To keep everything peaceful, you should hide Jitsi behind an Nginx reverse proxy.
Nginx will take care of SSL, ports 80/443 and will proxy requests to the Jitsi containers running on internal ports.

This guide will show how to configure two Linux servers so that all the Internet traffic from a specific local subnet (for example, 10.100.10.0/24) is routed not via its default gateway but through an IPIP tunnel to a remote server, which will then put that traffic onto the Internet.

This is useful if you need services in one subnet to go out to the world with the IP address of another server — for example, to bypass restrictions, centralize NAT, or hide the source.

In a world where data privacy and access to resources are often restricted by geoblocks or corporate policies, tools like ProxyChains become indispensable assistants. ProxyChains — or more precisely its modern fork ProxyChains-NG — is an open utility for Unix-like systems (Linux, macOS, etc.) that allows routing the network traffic of any application through a chain of proxy servers. It is especially popular among developers, pentesters, and security enthusiasts. In this article we’ll cover what ProxyChains can do, why it’s useful for developers, provide usage examples, and discuss its limitations.

Hello! If you’re new to the world of remote server administration, you’re probably familiar with SSH — a reliable tool for connecting to remote machines. But what do you do when the connection is unstable: Wi‑Fi drops, you switch to mobile data, or your laptop “sleeps”? This is where Mosh (Mobile Shell) comes in — a “mobile shell” that makes remote work comfortable even in poor conditions.

In this article we’ll look at what Mosh is, why it’s better than SSH in certain scenarios, how to install and use it. Everything simple and step‑by‑step — for absolute beginners. Let’s get started!

In today’s world of networking technologies, combining two remote offices into a single entity is a fairly routine task. Usually, L3 tunnels are used for this (for example, IPIP or IPsec). However, there are situations when simple routing is not enough and full L2 connectivity is required, as if remote devices were connected to the same switch.

Let’s figure out when this is necessary and how to configure such connectivity correctly so that it is not only working but also fault-tolerant.

The EoIP (Ethernet over IP) protocol from MikroTik is used to create an L2 tunnel over an IP network, allowing you to combine two remote local networks into a single broadcast domain.
If your EoIP tunnel does not establish (no “R” — Running flag), follow this step-by-step checklist.

1. Check IP connectivity (L3)

Before starting, make sure the routers see each other at the IP level.

Ping the remote side:

Running a site on WordPress is great, but data reliability and security are a priority. Regular backups protect the project from errors, attacks, and failures. In this guide we’ll look at how to create an automatic WordPress backup using:

• mysqldump — for the database,
• rclone — for uploading to Yandex Cloud,
• curl — for notifications in Telegram.

🛠️ Step 1. Creating a Local Backup

1.1 Checking WordPress Configuration

The wp-config.php file is located in the site root (/var/www/ваш_сайт/wp-config.php):

Local Telegram Bot API allows developers to run their own API server, providing significant advantages for handling large files, performance, and configuration flexibility. However, to understand the need for a local server, it’s important to consider the limitations of the standard Telegram Bot API that works via an HTTPS interface. In this article we’ll review the benefits of the Local Bot API, the limitations of the standard approach, and steps to set up a local server via Docker, including registering a bot to use with it.