3x-ui/docker-compose.yml

services:
  3xui:
    build:
      context: .
      dockerfile: ./Dockerfile
    container_name: 3xui_app
    # hostname: yourhostname <- optional
    volumes:
      - $PWD/db/:/etc/x-ui/
      - $PWD/cert/:/root/cert/
    environment:
      XRAY_VMESS_AEAD_FORCED: "false"
      XUI_ENABLE_FAIL2BAN: "true"
    tty: true
    # network_mode: host # Отключено, так как на Windows 11/WSL эта опция не пробрасывает порты на localhost
    ports:
      - "2053:2053" # Веб-панель
      - "2054:2054" # Доп. порт панели/API
      - "2096:2096" # Порт подписки (Subscription port)
    restart: unless-stopped
-												Add docker-compose.yml

											
										
										
											2023-05-12 17:48:16 +00:00
+								services:
-												chore: build image in docker compose

this makes it possible to run development build using Docker.
											
										
										
											2025-06-13 08:25:13 +00:00
+xui:
 								    build:
 								      context: .
 								      dockerfile: ./Dockerfile
 								    container_name: 3xui_app
 								    # hostname: yourhostname <- optional
-												Add docker-compose.yml

											
										
										
											2023-05-12 17:48:16 +00:00
+								    volumes:
 								      - $PWD/db/:/etc/x-ui/
 								      - $PWD/cert/:/root/cert/
 								    environment:
 								      XRAY_VMESS_AEAD_FORCED: "false"
-												chore: `X_UI_ENABLE_FAIL2BAN` -> `XUI_ENABLE_FAIL2BAN` (#3030)


											
										
										
											2025-05-22 06:21:23 +00:00
+								      XUI_ENABLE_FAIL2BAN: "true"
-												Add docker-compose.yml

											
										
										
											2023-05-12 17:48:16 +00:00
+								    tty: true
-												**Fixes & Changes:**
1. **Fixed XPadding Placement Dropdown**:
   - Added the missing `cookie` and `query` options to `xPaddingPlacement` (`stream_xhttp.html`).
   - *Why:* Previously, users wanting `cookie` obfuscation were forced to use the `header` placement string. This caused Xray-core to blindly intercept the entire monolithic HTTP Cookie header, failing internal padding-length validations and causing the inbound to silently drop the connection.
2. **Fixed Uplink Data Placement Validation**:
   - Replaced the unsupported `query` option with `cookie` in `uplinkDataPlacement`.
   - *Why:* Xray-core's `transport_internet.go` explicitly forbids `query` as an uplink placement option. Selecting it from the UI previously sent a payload that would cause Xray-core to instantly throw an `unsupported uplink data placement: query` panic. Adding `cookie` perfectly aligns the UI with Xray-core restrictions.
### Related Issues
- Resolves #3992

											
										
										
											2026-04-06 12:00:43 +00:00
+								    # network_mode: host # Отключено, так как на Windows 11/WSL эта опция не пробрасывает порты на localhost
 								    ports:
 								      - "2053:2053" # Веб-панель
 								      - "2054:2054" # Доп. порт панели/API
 								      - "2096:2096" # Порт подписки (Subscription port)
-												Add docker-compose.yml

											
										
										
											2023-05-12 17:48:16 +00:00
+								    restart: unless-stopped