diff --git a/apps/docs/content/docs/core/manual-installation.mdx b/apps/docs/content/docs/core/manual-installation.mdx
index 92f69ee0..c5061a95 100644
--- a/apps/docs/content/docs/core/manual-installation.mdx
+++ b/apps/docs/content/docs/core/manual-installation.mdx
@@ -178,7 +178,7 @@ install_dokploy() {
         -p 80:80/tcp \
         -p 443:443/tcp \
         -p 443:443/udp \
-        traefik:v3.6.25
+        traefik:v3.7.16
 
     docker network connect dokploy-network dokploy-traefik
 
@@ -194,7 +194,7 @@ install_dokploy() {
     #     --publish mode=host,published=443,target=443 \
     #     --publish mode=host,published=80,target=80 \
     #     --publish mode=host,published=443,target=443,protocol=udp \
-    #     traefik:v3.6.25
+    #     traefik:v3.7.16
 
     GREEN="\033[0;32m"
     YELLOW="\033[1;33m"
@@ -339,7 +339,7 @@ docker run -d \
   -p 80:80/tcp \
   -p 443:443/tcp \
   -p 443:443/udp \
-  traefik:v3.6.25
+  traefik:v3.7.16
 
 docker network connect dokploy-network dokploy-traefik
 ```
@@ -424,15 +424,28 @@ curl -sSL https://dokploy.com/install.sh | sudo ADVERTISE_ADDR=192.168.1.100 sh
 
 Note: if you run the installer with `sudo`, pass the variable inline as shown above. Using `export` beforehand won't work because `sudo` resets the environment before executing the script.
 
-## Updating Traefik Manually
+## Updating Traefik
 
-Dokploy does not update the Traefik container automatically when you upgrade. This is intentional to avoid unexpected downtime for your services. If you need a newer Traefik version (for example, due to a breaking change or security fix), you can update it manually.
+Dokploy does not update the Traefik container automatically when you upgrade. This is intentional to avoid unexpected downtime for your services. Instead, you can check the Traefik version and update it from the dashboard:
+
+- **Dokploy server**: go to **Web Server**, open the **Traefik** menu and click **Check Version**.
+- **Remote servers**: go to **Remote Servers**, click **Web Server Actions** on the server, open the **Traefik** menu and click **Check Version**.
+
+The dialog shows the running Traefik version and the version recommended by your Dokploy release. The recommended version is updated in new Dokploy releases. Updating is optional: when Traefik is older than the recommended version, you can click **Update**. Dokploy downloads the new image first, then recreates Traefik with the same environment variables and port mappings, and puts the previous container back if the new one fails to start. Your applications may be unreachable for a few seconds during the update.
+
+<Callout type='info'>
+  The update is only offered when Traefik is running the official image and is older than the recommended version. Start a stopped Traefik with **Reload** first. A custom Traefik image is never updated by Dokploy.
+</Callout>
+
+### Updating Traefik manually
+
+To update Traefik yourself, for example to a different version:
 
 1. Remove the existing Traefik container.
 2. Create a new container with the desired Traefik image version and the same configuration.
 3. Connect the new container to the Dokploy network.
 
-Example (replace `v3.6.7` with the version you want):
+Example (replace `v3.7.16` with the version you want):
 
 ```bash
 docker rm -f dokploy-traefik
@@ -446,7 +459,7 @@ docker run -d \
   -p 80:80/tcp \
   -p 443:443/tcp \
   -p 443:443/udp \
-  traefik:v3.6.25
+  traefik:v3.7.16
 
 docker network connect dokploy-network dokploy-traefik
 ```
diff --git a/apps/docs/content/docs/core/remote-servers/index.mdx b/apps/docs/content/docs/core/remote-servers/index.mdx
index c41149ea..4a787d39 100644
--- a/apps/docs/content/docs/core/remote-servers/index.mdx
+++ b/apps/docs/content/docs/core/remote-servers/index.mdx
@@ -58,7 +58,7 @@ You can configure an application to use a build server by selecting it in the ap
    - **SSH Keys**: Steps to add SSH keys to the remote server.
    - **Deployments**: Steps to configure the remote server for deploying applications.
 3. **Edit Server**: Allows you to modify the remote server's details, such as SSH key, name, description, IP, etc.
-4. **View Actions**: Lets you perform actions like managing the Traefik instance, storage, and activating Docker cleanup.
+4. **View Actions**: Lets you perform actions like managing the Traefik instance (including checking and updating its version), storage, and activating Docker cleanup.
 5. **Show Traefik File System**: Displays the contents of the remote server's directory.
 6. **Show Docker Containers**: Shows the Docker containers running on the remote server.
 7. **Show Docker Swarm Overview**: Shows the Docker Swarm overview of the remote server.
diff --git a/apps/docs/content/docs/core/remote-servers/validate.mdx b/apps/docs/content/docs/core/remote-servers/validate.mdx
index 21d15ead..b196cc4d 100644
--- a/apps/docs/content/docs/core/remote-servers/validate.mdx
+++ b/apps/docs/content/docs/core/remote-servers/validate.mdx
@@ -9,7 +9,7 @@ Dokploy validates different components depending on the type of remote server yo
 
 ## Deployment Servers
 
-For **Deployment Servers**, Dokploy requires the following 7 components to be properly configured:
+For **Deployment Servers**, Dokploy requires the following components to be properly configured:
 
 1. **Docker Installed**: Docker must be installed on the remote server.
 2. **RClone Installed**: RClone must be installed on the remote server.
@@ -18,7 +18,8 @@ For **Deployment Servers**, Dokploy requires the following 7 components to be pr
 5. **Buildpacks Installed**: Buildpacks must be installed on the remote server.
 6. **Docker Swarm Initialized**: Docker Swarm must be initialized on the remote server.
 7. **Dokploy Network Created**: A Docker network for Dokploy must be created on the remote server.
-8. **Main Directory Created**: A directory must be created on the remote server to store applications.
+8. **Traefik Installed**: Traefik must be installed on the remote server to route traffic to your applications. The installed Traefik version is shown next to it.
+9. **Main Directory Created**: A directory must be created on the remote server to store applications.
 
 <Callout type="info">
   Deployment servers are used to run and host your applications. They require Docker Swarm and network configuration since they need to run containers and manage deployments.
diff --git a/apps/docs/content/docs/core/troubleshooting/instance.mdx b/apps/docs/content/docs/core/troubleshooting/instance.mdx
index 333387ab..0a2b9480 100644
--- a/apps/docs/content/docs/core/troubleshooting/instance.mdx
+++ b/apps/docs/content/docs/core/troubleshooting/instance.mdx
@@ -219,7 +219,7 @@ docker run -d \
     -p 80:80/tcp \
     -p 443:443/tcp \
     -p 443:443/udp \
-    traefik:v3.6.25
+    traefik:v3.7.16
 
 docker network connect dokploy-network dokploy-traefik
 
@@ -237,7 +237,7 @@ docker service create \
   --publish mode=host,published=443,target=443 \
   --publish mode=host,published=80,target=80 \
   --publish mode=host,published=443,target=443,protocol=udp \
-  traefik:v3.6.25
+  traefik:v3.7.16
 ```
 
 ### Recreate Dokploy Service
diff --git a/apps/website/public/install.sh b/apps/website/public/install.sh
index 2c0743d4..ff1ec768 100644
--- a/apps/website/public/install.sh
+++ b/apps/website/public/install.sh
@@ -349,7 +349,7 @@ install_dokploy() {
         -p 80:80/tcp \
         -p 443:443/tcp \
         -p 443:443/udp \
-        traefik:v3.6.25
+        traefik:v3.7.16
 
 
     # Optional: Use docker service create instead of docker run
@@ -363,7 +363,7 @@ install_dokploy() {
     #     --publish mode=host,published=443,target=443 \
     #     --publish mode=host,published=80,target=80 \
     #     --publish mode=host,published=443,target=443,protocol=udp \
-    #     traefik:v3.6.25
+    #     traefik:v3.7.16
 
     GREEN="\033[0;32m"
     YELLOW="\033[1;33m"