MySQL Workbench support access

Prerequisites and authority

Start with read-only checks and authorized records. Capture evidence before changes. Stop and escalate when data replacement, financial changes or wider outages are possible.

Connect MySQL Workbench for approved diagnostics

Advanced and temporarily disruptive. Install MySQL Workbench on the BryanNet host before starting. Use the dedicated read-only support account, not root or the application account. Recreating MySQL interrupts database connections, so schedule access appropriately.

The existing guide and inspected support overlay use a localhost-only mapping. Verify the target package contains the files before executing. On Windows open PowerShell and enter the installed Docker directory:

cd C:\ProgramData\BryanNet\docker
docker compose --env-file ..\.env -f compose.release.yaml -f compose.support.yaml config --services

Stop if configuration reports missing required variables. Confirm the actual release paths and support-account password provisioning. Then enable only the approved binding:

docker compose --env-file ..\.env -f compose.release.yaml -f compose.support.yaml up -d --no-deps --force-recreate mysql
docker ps

Confirm 127.0.0.1:3306->3306/tcp. A display of only 3306/tcp is internal exposure and will not accept a host Workbench connection. Never change the binding to 0.0.0.0.

Create a Workbench connection with host 127.0.0.1, port 3306, user bryannet_support, the configured support password and actual database name, conventionally bryannet. Use Test Connection, then open the schema. Execute only approved read-only queries from Database diagnostics and safe query reference; avoid fetching credential columns.

Remove temporary access after the session:

docker compose --env-file ..\.env -f compose.release.yaml up -d --no-deps --force-recreate mysql
docker ps

Confirm the host mapping disappeared and application/worker health recovered. If the account does not exist, use the supported reconciliation procedure for your release or contact support; do not substitute a broadly privileged account.

Related guides

Related guides: Troubleshooting start here: observe, scope and collect evidence, Database diagnostics and safe query reference, Restore BryanNet safely, Logs, audit history and incident records.