The Existing Docker Swarm section only created the network and the dokploy
service, so installs failed against current versions that require the
dokploy_postgres_password and dokploy_auth_secret Docker secrets, the
dokploy-postgres service, and Traefik (issue #111). It now mirrors what
install.sh does today, minus the swarm re-initialization.
Also remove the ADVERTISE_ADDR env passed to the dokploy service in
install.sh and the docs: the app stopped reading process.env.ADVERTISE_ADDR
in February 2025, and the private-IP lookup step in troubleshooting only
existed to fill it. The recreate-service commands now also mount the auth
secret so recreated instances don't fall back to the insecure hardcoded
default, and the advertise-addr customization section documents the
ADVERTISE_ADDR env override instead of a script line that no longer exists.
Documents the fix for builds and domain validation failing with DNS
errors when the provider's default resolvers misbehave inside Docker
containers (reported in Dokploy/website#146 and Dokploy/dokploy#3981).
The install script's get_private_ip() fallback picked the first RFC1918
address from `ip addr show`, which matches the docker0 bridge (172.17.0.1)
when Docker is already installed — an address other swarm nodes can never
reach. Exclude docker0/br-*/veth* interfaces so a real host/VPN interface
wins, and fall back to the public IP when no private interface exists
(e.g. servers with only a public IP).
Verified end-to-end in Ubuntu 24.04 and Debian 13 containers (Docker
pre-installed, WireGuard-like interface, public IP on eth0), plus the
detection logic on Debian 12, AlmaLinux 9, Fedora 44 and openSUSE Leap 15.6.
Fixes#153
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- Clarified instructions for setting the ADVERTISE_ADDR variable when running the installation script with sudo, emphasizing the need to pass the variable inline.
- Added warnings in the installation and troubleshooting sections to prevent confusion regarding environment variable handling with sudo.
The docs claimed the Command field appends to the default command, but
createCommand in dokploy fully replaces it with the custom command.
Update both pages to describe the override behavior.
Fixes#142
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- Added instructions for installing a specific version of Dokploy using the release asset `install.sh`, emphasizing this as the recommended method for older versions.
- Included a note highlighting potential compatibility issues with the latest installation script for older versions.
- Updated the architecture documentation to reflect the removal of Redis from the Dokploy setup, ensuring accuracy in the description of the system components.
- Updated the architecture documentation to reflect the removal of the Redis database from the Dokploy setup.
- Modified the manual installation guide to eliminate Redis configuration instructions.
- Adjusted troubleshooting documentation to indicate that only three containers should be running, following the removal of Redis.
- Cleaned up the installation script by removing Redis service creation commands.
- Expanded the description of Enterprise features to include Application Authentication and Unlimited Concurrent Builds, enhancing clarity and detail.
- Added links to specific documentation sections for SSO, Custom Roles, Audit Logs, Whitelabeling, and the new features, improving navigation and user experience.
- Updated images related to the Enterprise features to ensure visual consistency and support the new content.
- Revised the "Differences" section to clarify the operational distinctions between Dokploy editions and introduced a comprehensive table summarizing features across Self-Hosted and Cloud options.
- Added a new section in the "Enterprise" documentation outlining the two flavors of Enterprise offerings, detailing their features and operational differences.
- Enhanced the overall structure and clarity of the documentation to improve user understanding of Dokploy's offerings.
- Added detailed sections for Enterprise features including SSO, Custom Roles, Whitelabeling, and Audit Logs, each with descriptive text and accompanying images for better understanding.
- Introduced new images to visually represent the configuration settings for these features, improving the overall documentation quality.
- Updated the existing documentation to include links and references to the new content, ensuring comprehensive coverage of Enterprise capabilities.
- Introduced a new documentation page titled "Interface Overview" that provides a visual tour of the Dokploy dashboard, including detailed descriptions and screenshots of major sections such as Home, Projects, Applications, Databases, and more.
- Updated meta.json to include the new "interface-overview" entry for improved navigation.
- Added multiple new images to enhance the visual representation of the dashboard features.
- Introduced a new documentation page for Application Authentication, detailing how to protect deployed applications with SSO using oauth2-proxy and Traefik.
- Updated the main SSO index to link to the new Application Authentication section.
- Modified meta.json to include "application-authentication" for navigation purposes.
- Introduced a new section on how Dokploy manages build and deployment concurrency per server, including configuration details and limits based on the plan.
- Updated meta.json to include the new "concurrent-builds" entry for navigation.
Documents the login-hangs-behind-Cloudflare-Access issue and the required
configuration (BETTER_AUTH_SECRET, BETTER_AUTH_TRUSTED_ORIGINS, Web Server
host/HTTPS settings) to fix it. Closes#4361.
- Introduced a new section detailing the integration of AI providers for generating Docker Compose templates in Dokploy.
- Provided step-by-step instructions for setting up AI providers and generating configurations from natural language prompts.
- Included examples of compatible AI providers and usage scenarios to enhance user understanding and accessibility.
- Updated the cloud documentation to clarify the managed service model and its benefits.
- Added a new section comparing Cloud vs Self-Hosted versions, detailing operational differences.
- Introduced a comprehensive guide on multi-tenancy, explaining resource organization and access control.
- Improved overall structure and clarity of the documentation for better user understanding.
- Added documentation for Custom Roles, allowing Enterprise users to create tailored roles with granular permissions.
- Introduced a new Audit Logs section, detailing how to track actions performed by organization members for security and compliance.
- Updated meta.json to include references to the new features.
These enhancements provide greater control and visibility for Enterprise users, improving overall user management and compliance capabilities.
- Changed the health check route in both rollback and zero downtime deployment sections from `/api/health` to `/health` for consistency and accuracy.
- Ensured that the documentation reflects the correct endpoint for NodeJS applications, enhancing clarity for users.
Close here https://github.com/Dokploy/dokploy/issues/3994
- Updated the meta.json file to include Zitadel as a supported SSO provider alongside existing options, enhancing the configuration capabilities for enterprise users.
- Introduced a new guide for configuring SSO with Zitadel, detailing application setup, issuer URL retrieval, and Dokploy integration steps.
- Updated the main SSO index to include Zitadel as a supported provider, enhancing the documentation for enterprise users.
- Removed the Pricing component from the homepage and created a new dedicated Pricing page.
- Updated navigation links to point to the new Pricing page instead of the homepage section.
- Enhanced the Pricing component with an animated grid pattern for improved visual appeal.
- Updated the core meta.json file to include 'patches' in the list of features, enhancing documentation related to applying patches during the build process.
- Introduced a new section on patches, detailing how to apply file-level modifications to repositories during builds.
- Included use cases, step-by-step instructions for creating, editing, and deleting patches, and information on managing patches effectively.
- Introduced a new Whitelabeling documentation page detailing customization options for branding, appearance, metadata, and error pages.
- Updated the enterprise index to include a description of the Whitelabeling feature.
- Included Microsoft Teams in the list of supported notification providers in meta.json.
- Updated overview.mdx to describe Microsoft Teams notifications.
- Created a new teams.mdx file with detailed setup instructions for Microsoft Teams notifications.
- Updated the documentation to specify two methods for injecting environment variables into containers: using the `env_file` option to load all variables or referencing specific variables with the `${VAR_NAME}` syntax.
- Introduced new files detailing the Audit Logs and Whitelabeling features for Enterprise users.
- The Audit Logs section outlines logged events, access methods, retention policies, and compliance support.
- The Whitelabeling section describes customization options, configuration steps, and best practices for branding the application.
- These additions enhance the documentation by providing comprehensive guidance on key Enterprise functionalities.
Included a new section detailing the steps to manually update the Traefik container in Dokploy, emphasizing the importance of checking for breaking changes in Traefik versions before upgrading.
Close https://github.com/Dokploy/website/issues/127
