Configure the macOS firewall for Dermi Atlas Professional connections. Dermi Atlas Manager publishes the service ports through Docker, so no manual macOS firewall rule is required.
No manual macOS firewall configuration is required for LAN access. Dermi Atlas Manager publishes the Dermi Atlas Professional service ports (webapp, websocket, and gateway) through Docker, and macOS does not need per-port inbound rules for those published ports. Reserve any allow-list step for the Docker application, and only when the firewall is set to block all incoming connections.
On macOS no per-application firewall change is required for LAN access, because the Dermi Atlas Manager handles port exposure through Docker and the macOS Application Firewall does not gate the published service ports. If the firewall is set to block all incoming connections and clients cannot connect, the application to allow is Docker, not Dermi Atlas Manager:
Manual socketfilterfw configuration is not needed on macOS for Dermi Atlas Professional, because the service ports are published by Docker rather than by Dermi Atlas Manager. If the firewall is set to block all incoming connections and clients still cannot reach the host after the allow-list step above, the application to add and unblock is Docker, not Dermi Atlas Manager. Verify the Docker.app bundle path on the target macOS and Docker Desktop version before running these commands:
# Add Docker to the macOS Application Firewall
sudo /usr/libexec/ApplicationFirewall/socketfilterfw --add /Applications/Docker.app
# Unblock the application
sudo /usr/libexec/ApplicationFirewall/socketfilterfw --unblockapp /Applications/Docker.appYour feedback helps us improve our documentation
Contact our support team for personalized help