BFC BFC Docs
Reference

Network ports and names

Default host ports, internal Docker names, and required network paths.

Controller host ports

Port Protocol Service Purpose
22 TCP SSH Setup Tool commands and file transfer
3306 TCP MariaDB Direct database access
5000 HTTP BFC Gateway Web pages, API, Swagger, health
5001 HTTPS BFC Gateway Self-signed HTTPS endpoint
8080 HTTP phpMyAdmin Database administration
1885 HTTP Node-RED Flow editor and dashboards

All service ports bind to the controller host in the current Setup Tool workflow. Use host firewall rules to limit them.

Docker resources

Type Name
Network bfc-network
Container bfc-mariadb
Container bfc-phpmyadmin
Container bfc-gateway
Container bfc-nodered
Script container BFC-{script-name}
MariaDB volume bfc-mariadb
Node-RED volume bfc-nodered

Internal addresses

Use container DNS names when the caller is attached to bfc-network:

Gateway: http://bfc-gateway:5000
MariaDB: bfc-mariadb:3306

Use CONTROLLER_IP and the published host port from a workstation, browser, or other machine.

Outbound access

During setup, the controller may require:

  • HTTPS access to Docker registries for MariaDB, phpMyAdmin, and Node-RED images.
  • HTTPS access to the npm registry for FlowFuse Dashboard.
  • Network access from BFC Console containers to configured IO-Link masters.

The operator workstation needs SSH access to the controller and browser access to the services it will administer.

Health and user interfaces

Gateway home:   http://CONTROLLER_IP:5000/
Gateway health: http://CONTROLLER_IP:5000/api/health
Swagger:        http://CONTROLLER_IP:5000/swagger/
Active tags:    http://CONTROLLER_IP:5000/tags
phpMyAdmin:     http://CONTROLLER_IP:8080/
Node-RED:       http://CONTROLLER_IP:1885/
Built with ASP.NET Core and Markdig. BFC user documentation · preview release