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
    restart: unless-stopped
Add docker-compose.yml 2023-05-12 22:18:16 +04:30			`services:`
chore: build image in docker compose this makes it possible to run development build using Docker. 2025-06-13 15:25:13 +07:00			`3xui:`
			`build:`
			`context: .`
			`dockerfile: ./Dockerfile`
			`container_name: 3xui_app`
			`# hostname: yourhostname <- optional`
Add docker-compose.yml 2023-05-12 22:18:16 +04:30			`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 13:21:23 +07:00			`XUI_ENABLE_FAIL2BAN: "true"`
Add docker-compose.yml 2023-05-12 22:18:16 +04:30			`tty: true`
			`network_mode: host`
fix: enhance WebSocket stability, resolve XHTTP configurations and fix UI loading shifts (#3997) * feat: implement real-time traffic monitoring and UI updates using a high-performance WebSocket hub and background job system * feat: add bulk client management support and improve inbound data handling * Fix bug * 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 * This commit fixes structural payload issues preventing XHTTP from functioning correctly and eliminates WebSocket log spam. - [Fix X-Padding UI] Added missing `cookie` and `query` options to X-Padding Placement. Fixes the issue where using Cookie fallback triggers whole HTTP Cookie header interception and silent drop in Xray-core. (Resolves [#3992](https://github.com/MHSanaei/3x-ui/issues/3992)) - [Fix Uplink Data Options] Replaced the invalid `query` option with `cookie` in Uplink Data Placement dropdown to prevent Xray-core backend panic `unsupported uplink data placement: query`. - [Fix WebSockets Spam] Boosted `maxMessageSize` boundary to 100MB and gracefully handled fallback fetch signals via `broadcastInvalidate` to avoid buffer dropping spam. (Resolves [#3984](https://github.com/MHSanaei/3x-ui/issues/3984)) * Fix * gofmt * fix(websocket): resolve channel race condition and graceful shutdown deadlock * Fix: inbounds switch * Change max quantity from 10000 to 500 * fix 2026-04-19 22:01:00 +03:00			`restart: unless-stopped`