nucleo000/meshcentral
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix: Usar HTTP interno entre Traefik y MeshCentral (puerto 80)
All checks were successful
deploy-meshcentral / deploy (push) Successful in 13s
Details

Browse Source
This commit is contained in:
josedario87
2025-10-31 22:34:56 -06:00
parent 5b9be6ad51
commit df06054898
1 changed files with 2 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docker-compose.yml
View File

@@ -36,13 +36,8 @@ services:
- "traefik.enable=true"
- "traefik.docker.network=principal"
# Service
- "traefik.http.services.${APP_NAME}.loadbalancer.server.port=443"
- "traefik.http.services.${APP_NAME}.loadbalancer.server.scheme=https"
# ServerTransport para ignorar validación SSL del backend (certificados autofirmados)
- "traefik.http.serversTransports.meshcentral-transport.insecureskipverify=true"
- "traefik.http.services.${APP_NAME}.loadbalancer.serverstransport=meshcentral-transport"
# Service - Conexión HTTP interna (Traefik maneja HTTPS hacia el exterior)
- "traefik.http.services.${APP_NAME}.loadbalancer.server.port=80"
# Router principal con Authentik Forward Auth para rutas de usuario
- "traefik.http.routers.${APP_NAME}.rule=Host(`${APP_DOMAIN}`) && !PathPrefix(`/agent.ashx`) && !PathPrefix(`/meshrelay.ashx`) && !PathPrefix(`/devicefile.ashx`) && !PathPrefix(`/amtactivate`) && !PathPrefix(`/meshsettings`) && !PathPrefix(`/devicepower.ashx`)"