Device Agent problem

Vendors FlowFuse
1

Hi;

I was able to install flowfuse on an azure VM. But when I ty to connect my nodered-"edge"-device I get this error from my device agent docker.
Can somebody help with this? point me in the right direction?

thanks a lot...

[AGENT] 9/2/2024 9:44:23 AM [info] FlowFuse Device Agent
[AGENT] 9/2/2024 9:44:23 AM [info] ----------------------
[AGENT] 9/2/2024 9:44:23 AM [info] Agent starting...
[AGENT] 9/2/2024 9:44:23 AM [info] Version: 2.8.0
[AGENT] 9/2/2024 9:44:23 AM [info] Mode: Device Mode
[AGENT] 9/2/2024 9:44:23 AM [info] Device: bZ0YqZALmP
[AGENT] 9/2/2024 9:44:23 AM [info] ForgeURL: http://flowfuse.korrelatie.be
[AGENT] 9/2/2024 9:44:23 AM [info] Configuration :-
[AGENT] 9/2/2024 9:44:23 AM [info]   * Instance           : unknown
[AGENT] 9/2/2024 9:44:23 AM [info]   * Snapshot           : none
[AGENT] 9/2/2024 9:44:23 AM [info]   * Settings           : none
[AGENT] 9/2/2024 9:44:23 AM [info]   * Operation Mode     : autonomous
[AGENT] 9/2/2024 9:44:23 AM [info]   * Target State       : running
[AGENT] 9/2/2024 9:44:23 AM [info]   * Licensed           : unknown
[AGENT] 9/2/2024 9:44:23 AM [info] Starting MQTT heartbeat thread. Interval: 30s (±5s)
[AGENT] 9/2/2024 9:44:34 AM [warn] Timeout performing initial check-in
[AGENT] 9/2/2024 9:44:38 AM [info] MQTT reconnecting to platform
[AGENT] 9/2/2024 9:44:53 AM [info] MQTT reconnecting to platform
[AGENT] 9/2/2024 9:45:08 AM [info] MQTT reconnecting to platform
[AGENT] 9/2/2024 9:45:24 AM [info] MQTT reconnecting to platform
2

Hi @faelterman

The obvious question would be have you setup an MQTT broker as per the documentation? and verified it is running and connectable from your device(s) and flowfuse platform install?

3

@Steve-Mcl its tagged as Docker, so the broker should be running, but it looks like DNS is not setup correctly (no wildcard)

And did you setup the wildcard DNS entry?

How have you configured the entry_point? and broker urls?

There isn't enough info here to help.

4

Hi guys;

Thanks for helping.
The broker is indeed on docker. I followed the docker-compose install method . I can reach the flowforge admin pages. I think the wildcard is working because any (madeup)subdomain is pointed at my vps running the dockercompose. I do have nginxproxymanager, in front generating the certificate,

if by entrypoint you mean the flowforge.yml file
I post it here;

port: 3000
host: 0.0.0.0
domain: korrelatie.be
base_url: http://flowfuse.korrelatie.be
api_url: http://flowfuse:3000

#################################################
# Database Configuration                        #
#################################################

db:
  logging: false
  ## The database type: sqlite|postgres
  type: postgres
  ### SQLite options

  ## The database filename. Relative to $FLOWFORGE_HOME/var/
  ## Set to ':memory:' for a database that is wiped on restart
  # storage: forge.db

  ### Postgres options

  host: postgres
  user: forge
  password: secret

#################################################
# Project Driver Configuration                  #
#################################################

driver:
  ## The type of backend driver to use
  ##  Can be: localfs/docker/stub/k8s
  type: docker

  options:
    ## Options to be passed to the driver

    ### LocalFS options

    ## The first port number to assign to projects
    # start_port: 7880

    ## Path to find node executable if not on the default path
    # node_path: /usr/bin/node

    ### Docker options

    ## Docker socket path
    socket: /tmp/docker.sock
    # registry: hub.flowforge.com

    ### K8S options

    ## Kubectl conf file to contact the cluster
    # config_file: /opt/share/projects/flowforge/test/config
    # registry: hub.flowforge.com

#################################################
# Email Configuration                           #
#################################################

email:
  enabled: false
  debug: false
  smtp:
    host: localhost
    port: 587
    secure: false
    #auth:
    #    user: username
    #    pass: password

broker:
  url: mqtt://flowforge-broker:1883
  public_url: ws://mqtt.korrelatie.be

fileStore:
  url: http://file-server:3001

I'm sorry, I am by far no expert in this, I hope somebody can point me in the correct direction.
If someone knows how to test the connection to the mqtt that would be awsome...

Kind regards

5

Double check that the VIRTUAL_HOST and LETSENCRYPT_HOST environment variables are correct in the docker-compose.yml for the flowforge-broker service say mqtt.korrelatie.be

6

Thanks @hardillb and @Steve-Mcl ;

Finally, tonight I was able to get everything to work. NginxProxyManager in between was'nt a very good idea... So I started over from scratch keeping everything as close as possible to the documentation.
It seems that everything works now, only to notice a few features I was looking forward to are not available in the selfhosted version.... (project nodes, and remote editing of devices...).
Going to have to evaluate my usecase ....

Kind regards

7

They are available in the self hosted version, but they do require a license as they are not available for free.