Skip to content
flow8

Troubleshooting flow8 app installation

Can`t Install go with go mod tidy

Error:

git.qix.sx/gorgany/gorgany.git/app: no secure protocol found for repository

Description:

Go try`s get some private repositories

Solution:

Check this environment variables in .env file:

GOPRIVATE=<gorgany_framework_git_url>
GIT_HOST=<gorgany_framework_git_host>
GIT_USER=<gorgany_framework_git_user>
GIT_PASS=<gorgany_framework_git_token>

Run following commans:

source .env
git config --global url."https://$GIT_USER:$GIT_PASS@$GIT_HOST/".insteadOf "https://$GIT_HOST/"

Imagick not installed or configured on build

Error:

Error undefined: imagick.Initialize while using imagick

Description:

App uses Go Imagick a Go bind to ImageMagick’s MagickWand C API. which need`s dependencies.

Solution:

Run following commands:

Install it from source

sudo apt install build-essential
wget https://imagemagick.org/archive/ImageMagick.tar.gz
tar xvzf ImageMagick.tar.gz
cd ImageMagick-{{version}}
./configure
make
make install
sudo ldconfig /usr/local/lib

Verify installation with:

magick -version

MagickWand/MagickWand.h: No such file or directory

Error:

fatal error: MagickWand/MagickWand.h: No such file or directory

Description:

Incorrect version imagick is installed

Solution:

Install Imagemagick 7 version

Error: dial tcp: lookup mongo on 127.0.0.53:53: server misbehaving

Error:

{"level":"error","error":"server selection error: server selection timeout, current topology: { Type: Unknown, Servers: [{ Addr: mongo:27017, Type: Unknown, Last error: dial tcp: lookup mongo on 127.0.0.53:53: server misbehaving }, ] }","time":1732806764,"message":"Failed to save UIPath endpoints to the database"}

Description:

Database is not installed or properly configured.

Solutions:

Install an configure database see: Database installation

Check MONGODB_URI and MONGODB_DB variables in .env file.

Port already in use

Error:

Error response from daemon: driver failed programming external connectivity on endpoint flow8-app: Error starting userland proxy: listen tcp4 127.0.0.1:80: bind: address already in use

Description:

In Docker, the issue address already in use occurs when we try to expose a container port that’s already acquired on the host machine.

Solutions:

If port is in use, specify a different host port.

The container name is already in use by container

Error:

Conflict. The container name <name> is already in use by container

Description:

Every Docker container has a unique name assigned to it. If we don’t use the optional name argument in the docker run command, Docker assigns a random name.

Solutions:

To fix the stated issue, the user can either remove the existing Docker container and recreate the container, rename the existing container, and create a new one, or simply change the container name in the “–name” option of the “docker run” command.