Feat  add docs on how to disable the published port once domain is setted up #65
This commit is contained in:
Mauricio Siu
2025-11-30 01:55:31 -06:00
committed by GitHub

View File

@@ -73,6 +73,11 @@ After running the installation script, Dokploy and its dependencies will be set
Open your web browser and navigate to `http://your-ip-from-your-vps:3000`. You will be directed to the initial setup page where you can configure the administrative account for Dokploy.
<Callout type='warn'>
**Important:** Ensure that your server's firewall allows traffic on port
3000 to access the Dokploy web interface.
</Callout>
### Initial Configuration
1. **Create an Admin Account:** Fill in the necessary details to set up your administrator account. This account will be the admin account for Dokploy.
@@ -86,3 +91,24 @@ Open your web browser and navigate to `http://your-ip-from-your-vps:3000`. You w
alt="home og image"
className="rounded-lg"
/>
### Secure Your Installation
After setting up your admin account, it's crucial to secure your Dokploy installation by enabling HTTPS.
To configure a domain with SSL/TLS certificates for your Dokploy panel, please refer to the [Domains](/docs/core/domains) section where you'll find detailed instructions for different SSL configurations including Let's Encrypt, Cloudflare, and custom certificates.
### Disable access via ip:port (Optional but Recommended)
To enhance security, it's advisable to restrict access to Dokploy via the server's IP address and port.
<Callout type='warn'>
**Important:** Before disabling IP:port access, make sure you have configured a domain with HTTPS working properly. Otherwise, you will lose access to your Dokploy installation. See the [Domains](/docs/core/domains) section to set this up first.
</Callout>
Once you have verified that your domain is working correctly, you can disable IP:port access by running this command on the server:
```bash
docker service update --publish-rm "published=3000,target=3000,mode=host" dokploy
```
To further secure your installation, consider reading the [Security recommendations](/docs/core/multi-server/security#security-recommendations) section.