ElPoulpo Comments - Answer Overflow

Topics

ElPoulpo

Explore posts from servers

ZZITADEL DDokploy

•Created by ElPoulpo on 11/28/2024 in #old-help

RabbitMQ connection impossible from another service

Hey @Tom

services:
  <your-dokploy-service-id>: #replace by the service ID 
    image: rabbitmq:4.0.4-management-alpine
    restart: unless-stopped
    environment:
      RABBITMQ_DEFAULT_USER: ${RABBITMQ_DEFAULT_USER}
      RABBITMQ_DEFAULT_PASS: ${RABBITMQ_DEFAULT_PASS}
      RABBITMQ_DEFAULT_VHOST: your-vhost-name
    volumes: 
      - rabbitmq_data:/var/lib/rabbitmq/
      - rabbitmq_config:/etc/rabbitmq/
    port: #This is only if you want to push and pull messages from outside your server, remove it if not needed
      - <port>:5672 #here choose the <port> of your choice (for example 35456), it shouldn't be used by another service on your server.

volumes:
  rabbitmq_data:
  rabbitmq_config:

services:
  <your-dokploy-service-id>: #replace by the service ID 
    image: rabbitmq:4.0.4-management-alpine
    restart: unless-stopped
    environment:
      RABBITMQ_DEFAULT_USER: ${RABBITMQ_DEFAULT_USER}
      RABBITMQ_DEFAULT_PASS: ${RABBITMQ_DEFAULT_PASS}
      RABBITMQ_DEFAULT_VHOST: your-vhost-name
    volumes: 
      - rabbitmq_data:/var/lib/rabbitmq/
      - rabbitmq_config:/etc/rabbitmq/
    port: #This is only if you want to push and pull messages from outside your server, remove it if not needed
      - <port>:5672 #here choose the <port> of your choice (for example 35456), it shouldn't be used by another service on your server.

volumes:
  rabbitmq_data:
  rabbitmq_config:

<your-dokploy-service-id> is not needed is you are not accessing rabbtimq:5672 from outside To access the console you have to setup a domain inside Domains tabs of your Dokploy service. And the console is on port 15672 no extra config needed in traefik or compose

12 replies

•Created by ElPoulpo on 11/28/2024 in #old-help

RabbitMQ connection impossible from another service

SOLUTION Internal naming the service as the dokploy service name and using it as host External just add a ports to map on the host machine 34567:5672

12 replies

•Created by ElPoulpo on 11/28/2024 in #old-help

RabbitMQ connection impossible from another service

No description

12 replies

•Created by ElPoulpo on 11/28/2024 in #old-help

RabbitMQ connection impossible from another service

or where I can find generated config for inspiration 🧐

12 replies

•Created by ElPoulpo on 11/28/2024 in #old-help

RabbitMQ connection impossible from another service

@Siumauricio How I can replicate what's done for database services but for custom service ? With external port settings

12 replies

•Created by ElPoulpo on 11/28/2024 in #old-help

RabbitMQ connection impossible from another service

already have this into traefik.yml file

entryPoints:
  web:
    address: ':80'
  websecure:
    address: ':443'
    http:
      tls:
        certResolver: letsencrypt
  rabbitmq:
    address: ':5672'

entryPoints:
  web:
    address: ':80'
  websecure:
    address: ':443'
    http:
      tls:
        certResolver: letsencrypt
  rabbitmq:
    address: ':5672'

What should i do in provider section ?

12 replies

•Created by ElPoulpo on 11/28/2024 in #old-help

RabbitMQ connection impossible from another service

Also tried that

rabbitmq:
    image: rabbitmq:4.0.4-management-alpine
    restart: unless-stopped
    environment:
      RABBITMQ_DEFAULT_USER: ${RABBITMQ_DEFAULT_USER}
      RABBITMQ_DEFAULT_PASS: ${RABBITMQ_DEFAULT_PASS}
    volumes: 
      - rabbitmq_data:/var/lib/rabbitmq/
    networks:
      - dokploy-network
    labels:
      - traefik.tcp.routers.ingress.rule=HostSNI(`*`)
      - traefik.tcp.routers.ingress.entrypoints=rabbitmq
      - traefik.tcp.services.ingress.loadbalancer.server.port=5672

rabbitmq:
    image: rabbitmq:4.0.4-management-alpine
    restart: unless-stopped
    environment:
      RABBITMQ_DEFAULT_USER: ${RABBITMQ_DEFAULT_USER}
      RABBITMQ_DEFAULT_PASS: ${RABBITMQ_DEFAULT_PASS}
    volumes: 
      - rabbitmq_data:/var/lib/rabbitmq/
    networks:
      - dokploy-network
    labels:
      - traefik.tcp.routers.ingress.rule=HostSNI(`*`)
      - traefik.tcp.routers.ingress.entrypoints=rabbitmq
      - traefik.tcp.services.ingress.loadbalancer.server.port=5672

12 replies

•Created by ElPoulpo on 11/5/2024 in #old-help

Impossible to deploy using API as applicationId is always NOT FOUND

@Siumauricio I see, make sens now 😅 Didn't get the general point about application vs compose service

17 replies

•Created by ElPoulpo on 11/5/2024 in #old-help

Impossible to deploy using API as applicationId is always NOT FOUND

@Siumauricio any idea on what's going on ?

17 replies

•Created by ElPoulpo on 11/5/2024 in #old-help

Impossible to deploy using API as applicationId is always NOT FOUND

and so when using

curl -X 'POST' \
  'https://your-domain/api/application.deploy' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer <token>' \
  -d '{
  "applicationId": "string"
}'

curl -X 'POST' \
  'https://your-domain/api/application.deploy' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer <token>' \
  -d '{
  "applicationId": "string"
}'

It fails

17 replies

•Created by ElPoulpo on 11/5/2024 in #old-help

Impossible to deploy using API as applicationId is always NOT FOUND

this is responses from Swagger API

17 replies

•Created by ElPoulpo on 11/5/2024 in #old-help

Impossible to deploy using API as applicationId is always NOT FOUND

No description

17 replies

•Created by ElPoulpo on 11/5/2024 in #old-help

Impossible to deploy using API as applicationId is always NOT FOUND

another one

17 replies

•Created by ElPoulpo on 11/5/2024 in #old-help

Impossible to deploy using API as applicationId is always NOT FOUND

No description

17 replies

•Created by ElPoulpo on 11/5/2024 in #old-help

Impossible to deploy using API as applicationId is always NOT FOUND

curl -X 'GET' \
  'https://your-domain/api/project.all' \
  -H 'accept: application/json'
  -H 'Authorization: Bearer <token>'

curl -X 'GET' \
  'https://your-domain/api/project.all' \
  -H 'accept: application/json'
  -H 'Authorization: Bearer <token>'

All the project insight the response of that request come without applicationID

17 replies

•Created by ElPoulpo on 11/5/2024 in #old-help

Impossible to deploy using API as applicationId is always NOT FOUND

More details : I follow this docs page https://docs.dokploy.com/en/docs/core/application/auto-deploy#api-method

17 replies

•Created by ElPoulpo on 11/5/2024 in #old-help

Impossible to deploy using API as applicationId is always NOT FOUND

Yes not working etheir

17 replies