<Support> Kru-x - Wekan and MongoDB-wekan templates


Kru-x

75 posts in this topic Last Reply

Recommended Posts

4 hours ago, tamito said:

imageproxy.php?img=&key=e5eec7c5c933ca16I try to install this docker follow you guide. However, I get The command failed at the end. Any idea how can i fix it. I am on unraid 6.8.

 

image.thumb.png.4605161c6a6064d7e5021b0fefa8b025.pngimage.thumb.png.83a385f5db08b42dc68908bb36d940e8.png

Hi, if this is a new install, try to completely remove the extra parameters: "--link "MongoDB db"" and in the MONGO_URL add for ex.: mongodb://192.168.1.121:27017/wekan (where the ip address is your server where you have Mongo DB and the exposed port of it.

 

Hope it helps and let me know,

Kru-x

Link to post
  • Replies 74
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

It's not much to show, the key is the --link "mongodb-wekan:db" in Extra Parameters in Advanced View this links the DB to the wekan container. The rest should be straight forward, the variables ex. RO

I just came here to say THANK YOU!   Installed this in our small office on our unraid server! this board is AMAZING for planning small and big projects.   We love it, again thank y

Please read release notes: https://github.com/wekan/wekan/blob/master/CHANGELOG.md#v300-2019-07-25-wekan-release   Master branch now uses MongoDB 4.0.10, so it requires that you backup

Posted Images

Hi Kru-x

It installed successfully. However, when I run it, log file shows

 

MongoError: database name must be a string
at Function.create (/build/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/error.js:43:12)
at validateDatabaseName (/build/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/operations/db_ops.js:720:22)
at new Db (/build/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/db.js:182:3)
at MongoClient.db (/build/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/mongo_client.js:237:14)
at packages/mongo/mongo_driver.js:186:25
at runWithEnvironment (packages/meteor.js:1286:24)

Link to post
On 12/28/2019 at 3:00 PM, tamito said:

Hi Kru-x

It installed successfully. However, when I run it, log file shows

 

MongoError: database name must be a string
at Function.create (/build/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/error.js:43:12)
at validateDatabaseName (/build/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/operations/db_ops.js:720:22)
at new Db (/build/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/db.js:182:3)
at MongoClient.db (/build/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/mongo_client.js:237:14)
at packages/mongo/mongo_driver.js:186:25
at runWithEnvironment (packages/meteor.js:1286:24)

Hi Tamito,

Sorry for the late reply, was a away for a while. As I don't know what MongoDB container you are using I am not sure what the DB name is in it, but the last word in mongodb://192.168.1.121:27017/wekan (in this case "wekan") is the name of the DB you have to connect to, could be "wekan", "admin", you can check it by logging in to the container with the console in unraid, then write "mongo" to open mongos shell and then "show databases".

Hope it helps,

Kru-x

Link to post

Hi Kru-x,

 

I got it. It is database name that is incorrect. After I changed to mongodb://192.168.1.121:27017/db, it worked. I have one question for you. Where does configuration location? I check in my appdata folder but nothing there. What does "unRAID Share Path:" in docker setup mean?

 

Thanks,

Link to post
1 hour ago, tamito said:

Hi Kru-x,

 

I got it. It is database name that is incorrect. After I changed to mongodb://192.168.1.121:27017/db, it worked. I have one question for you. Where does configuration location? I check in my appdata folder but nothing there. What does "unRAID Share Path:" in docker setup mean?

 

Thanks,

Happy you found it, there is no configuration to be done, except from within the user interface. All data is stored in the db so the unraid share path in this case is not really needed. I think there is a previous thread about it.

Link to post

Not sure if normal but this is where I get redirected when clicking the support thread for the godaddy ddns docker.

 

I was wondering if you were doing anything special since I've modified some script I found on the web and run it with cron and it gets the job done.

#!/bin/bash
keys=(key1 key2)
secrets=(secret1 secret2)
domains=(domain1 domain2)
Type=A
Name=@
TTL=600
CachedIP=/tmp/current_ip
CheckURL=http://api.ipify.org

echo -n "$(date +%Y%m%d%H%M%S) Checking current 'Public IP' from '${CheckURL}': "
PublicIP=$(curl -kLs ${CheckURL})
if [ $? -eq 0 ] && [[ "${PublicIP}" =~ [0-9]{1,3}\.[0-9]{1,3} ]]; then
  echo "${PublicIP}."
else
  sleep 120
  PublicIP=$(curl -kLs ${CheckURL})
  if [ $? -eq 0 ] && [[ "${PublicIP}" =~ [0-9]{1,3}\.[0-9]{1,3} ]]; then
    echo "[retry] ${PublicIP}."
  else
    echo "[retry] Fail! ${PublicIP}"
    exit 1
  fi
fi

if [ "$(cat ${CachedIP} 2>/dev/null)" != "${PublicIP}" ]; then
  for ((i = 0; i < ${#domains[@]}; ++i)); do
    echo -n "$(date +%Y%m%d%H%M%S) Checking '${domains[$i]}' IP records from 'GoDaddy': "
    Check=$(curl -kLsH"Authorization: sso-key ${keys[$i]}:${secrets[$i]}" -H"Content-type: application/json" https://api.godaddy.com/v1/domains/${domains[$i]}/records/${Type}/${Name} 2>/dev/null|jq -r '.[0].data')>/dev/null
    if [ $? -eq 0 ] && [ "${Check}" = "${PublicIP}" ]; then
      echo -e "unchanged.\n$(date +%Y%m%d%H%M%S) Current 'Public IP' matches 'GoDaddy' records. No update required."
    else
      echo -e "changed.\n$(date +%Y%m%d%H%M%S) Updating '${domains[$i]}' from '${Check}' to '${PublicIP}'."
      Update=$(curl -kLsXPUT -H"Authorization: sso-key ${keys[$i]}:${secrets[$i]}" -H "Content-type: application/json" https://api.godaddy.com/v1/domains/${domains[$i]}/records/${Type}/${Name} -d "[{\"data\":\"${PublicIP}\",\"ttl\":${TTL}}]" 2>/dev/null)
      if [ $? -eq 0 ] && [ "${Update}" = "" ]; then
        echo "$(date +%Y%m%d%H%M%S) Success."
      else
        echo "$(date +%Y%m%d%H%M%S) Fail. ${Update}"
        exit 1
      fi
    fi
  done
  echo ${PublicIP}>${CachedIP}
else
  echo -en "$(date +%Y%m%d%H%M%S) Current 'Public IP' matches 'Cached IP' recorded. No update required.\n"
fi
exit $?

I'm trying to understand in what use case scenario would a docker be a better solution than a simple 40ish lines script (could probably be optimized to < 30 lines).

Link to post
6 hours ago, dnLL said:

Not sure if normal but this is where I get redirected when clicking the support thread for the godaddy ddns docker.

 

I was wondering if you were doing anything special since I've modified some script I found on the web and run it with cron and it gets the job done.


#!/bin/bash
keys=(key1 key2)
secrets=(secret1 secret2)
domains=(domain1 domain2)
Type=A
Name=@
TTL=600
CachedIP=/tmp/current_ip
CheckURL=http://api.ipify.org

echo -n "$(date +%Y%m%d%H%M%S) Checking current 'Public IP' from '${CheckURL}': "
PublicIP=$(curl -kLs ${CheckURL})
if [ $? -eq 0 ] && [[ "${PublicIP}" =~ [0-9]{1,3}\.[0-9]{1,3} ]]; then
  echo "${PublicIP}."
else
  sleep 120
  PublicIP=$(curl -kLs ${CheckURL})
  if [ $? -eq 0 ] && [[ "${PublicIP}" =~ [0-9]{1,3}\.[0-9]{1,3} ]]; then
    echo "[retry] ${PublicIP}."
  else
    echo "[retry] Fail! ${PublicIP}"
    exit 1
  fi
fi

if [ "$(cat ${CachedIP} 2>/dev/null)" != "${PublicIP}" ]; then
  for ((i = 0; i < ${#domains[@]}; ++i)); do
    echo -n "$(date +%Y%m%d%H%M%S) Checking '${domains[$i]}' IP records from 'GoDaddy': "
    Check=$(curl -kLsH"Authorization: sso-key ${keys[$i]}:${secrets[$i]}" -H"Content-type: application/json" https://api.godaddy.com/v1/domains/${domains[$i]}/records/${Type}/${Name} 2>/dev/null|jq -r '.[0].data')>/dev/null
    if [ $? -eq 0 ] && [ "${Check}" = "${PublicIP}" ]; then
      echo -e "unchanged.\n$(date +%Y%m%d%H%M%S) Current 'Public IP' matches 'GoDaddy' records. No update required."
    else
      echo -e "changed.\n$(date +%Y%m%d%H%M%S) Updating '${domains[$i]}' from '${Check}' to '${PublicIP}'."
      Update=$(curl -kLsXPUT -H"Authorization: sso-key ${keys[$i]}:${secrets[$i]}" -H "Content-type: application/json" https://api.godaddy.com/v1/domains/${domains[$i]}/records/${Type}/${Name} -d "[{\"data\":\"${PublicIP}\",\"ttl\":${TTL}}]" 2>/dev/null)
      if [ $? -eq 0 ] && [ "${Update}" = "" ]; then
        echo "$(date +%Y%m%d%H%M%S) Success."
      else
        echo "$(date +%Y%m%d%H%M%S) Fail. ${Update}"
        exit 1
      fi
    fi
  done
  echo ${PublicIP}>${CachedIP}
else
  echo -en "$(date +%Y%m%d%H%M%S) Current 'Public IP' matches 'Cached IP' recorded. No update required.\n"
fi
exit $?

I'm trying to understand in what use case scenario would a docker be a better solution than a simple 40ish lines script (could probably be optimized to < 30 lines).

Bugger, forgot to put in the support start tag, thanks for pointing this out. I moved your post to the right forum and answered you there @ https://forums.unraid.net/topic/86922-support-kru-x-godaddy-ddns/

R

Kru-x

 

Link to post
On 1/2/2020 at 11:48 AM, Kru-x said:

Happy you found it, there is no configuration to be done, except from within the user interface. All data is stored in the db so the unraid share path in this case is not really needed. I think there is a previous thread about it.

Thx Kru-x for supporting such a great docker.

Link to post
  • 2 weeks later...

I updated unraid to V6.8.1 today. I then also decided to update all our dockers, unfortunately this resulted in Wekan just disapering from the dockers list.

I figured annoying but I will just re-install it.

This was unfortunately impossible for me as no matter what i do I just get The Command Failed error:

 

image.thumb.png.3a08d43e8ff608fe753abfb2d06b8773.png

 

Any suggestions as to what has happened and if It can be resolved? 

 

all the other dockers updated nicely except for wekan.

Link to post
11 hours ago, nik82 said:

I updated unraid to V6.8.1 today. I then also decided to update all our dockers, unfortunately this resulted in Wekan just disapering from the dockers list.

I figured annoying but I will just re-install it.

This was unfortunately impossible for me as no matter what i do I just get The Command Failed error:

 

image.thumb.png.3a08d43e8ff608fe753abfb2d06b8773.png

 

Any suggestions as to what has happened and if It can be resolved? 

 

all the other dockers updated nicely except for wekan.

Sorry, I'm away from my computer 4 a few days. But read the previous threads,  most likely you got the new version of wekan and docker that don't support the "-link". It changed, but all of that is discussed in the last few threads. Let me know if you figure it out, else I step you thorough it in a few days time. 

Kru-x

Link to post
  • 3 months later...

Has anyone gotten this to work behind their nginx reverse proxy? I am getting 502 errors for some reason. Following is my config in the letsencrypt docker container by linuxserver: Welp, I fixed it. Following is an example config that works.
 

 server {
         listen 443 ssl http2;
         #listen [::]:443 ssl http2;
         server_name kanban.example.com;
 
         # root /config/www;
         # index index.html index.htm index.php;
 
         ###SSL Certificates
         ssl_certificate /config/keys/letsencrypt/fullchain.pem;
         ssl_certificate_key /config/keys/letsencrypt/privkey.pem;
 
         ###Diffie-Hellman key exchange ###
         ssl_dhparam /config/nginx/dhparams.pem;
 
         ###SSL Ciphers
         ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AE
 S128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:E
 CDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-
 GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-S
 HA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA';
 
         ###Extra Settings###
         ssl_prefer_server_ciphers on;
         ssl_session_cache shared:SSL:1m;
         ssl_protocols TLSv1 TSLv1.1 TSLv1.2;
 
         ### Web Browser Security REdirect ###
         if ($http_user_agent ~ "MSIE" ) {
             return 303 https://browser-update.org/update.html;
         }
 
         ### Add HTTP Strict Transport Security ###
         # add_header Strict-Transport-Security "max-age=63072000; includeSubdomains";
         # add_header Front-End-Https on;
 
         client_max_body_size 0;
 
         location / {
                 proxy_pass http://192.168.0.3:8089;
                 proxy_http_version 1.1;
                 proxy_set_header Upgrade $http_upgrade;
                 proxy_set_header X-Forwarded-For $remote_addr;
                 proxy_set_header X-Forwarded-Proto https;
                 proxy_max_temp_file_size 2048m;
                 include /config/nginx/proxy.conf;
         }
 }

 

Edited by codecitymayor
Link to post
  • 2 months later...

Forgive me as I am completely new to unRAID so I am probably missing something completely simple.

 

I am not able to get this container running. 

I am trying to get the container running behind a reverse proxy (NPM) and have the following settings:2123344659_Annotation2020-07-05175847.png.0e5c7974cd20cab876a69d5479441922.png

 

I am getting this error:

/usr/bin/docker: links are only supported for user-defined networks.
See '/usr/bin/docker run --help'.
The command failed.

I have tried the various methods for links including 

  • --link mongodb://db
  • --link mongodb://192.168.0.37/db
  • mongodb://db
  • mongodb://192.168.0.37/db

All of them have resulted with the same error.

 

My other question will be that I am going to try and transfer my database from another instance (in the process of going from Ubuntu Server with Docker to unRAID) to this one. Is there a way that I can just transfer the database or maybe export it from my old server to the new one? Or would it be best for me to start fresh?

Link to post
2 hours ago, LTM said:

Forgive me as I am completely new to unRAID so I am probably missing something completely simple.

 

I am not able to get this container running. 

I am trying to get the container running behind a reverse proxy (NPM) and have the following settings:2123344659_Annotation2020-07-05175847.png.0e5c7974cd20cab876a69d5479441922.png

 

I am getting this error:


/usr/bin/docker: links are only supported for user-defined networks.
See '/usr/bin/docker run --help'.
The command failed.

I have tried the various methods for links including 

  • --link mongodb://db
  • --link mongodb://192.168.0.37/db
  • mongodb://db
  • mongodb://192.168.0.37/db

All of them have resulted with the same error.

 

My other question will be that I am going to try and transfer my database from another instance (in the process of going from Ubuntu Server with Docker to unRAID) to this one. Is there a way that I can just transfer the database or maybe export it from my old server to the new one? Or would it be best for me to start fresh?

Hi,

For Varible MONGO_URL use:  mongodb://192.168.1.121:27017/admin, witch is the admin login for MongoDB. Also if you are behind a revers proxy the varible ROOT_URL should be https://yourdomain.com, else if you are only using it internally it should be http://192.168.0.37:5555

 

I know you can export from Wekan to another instance, but if you can live without the old todo's and depending on how many, I would start again. Another factor I would personally consider is the requirements and future setup.

 

I moved away from Wekan myself, not that I don't like it it's brilliant, but it is for professional use "like big organizations" and for my to remember to water my garden or feed the Cat 🙂 is for sure an overkill. I use Nextcloud for my file system and it has a good task manager as a plugin, much of my needs consolidated in to one.


Kru-x

Link to post
  • 2 weeks later...

It errors for me as well, telling me links aren't supported. Can you please make a version where MongoDB is integrated into the package? This would certainly avert a lot of problems (see above) and would make it easier to get started.

 

The way I understand Docker, is that a docker should be self-contained. So it should contain everything it needs to run, and only go to the "outside world" for file system storage, and configuration files.

 

If you are unable to do this, could you at least make an easy to follow "getting started" guide? Docker being Docker, and unRAID being unRAID, it should be more or less identical for nearly everyone.

Link to post
16 hours ago, thany said:

It errors for me as well, telling me links aren't supported. Can you please make a version where MongoDB is integrated into the package? This would certainly avert a lot of problems (see above) and would make it easier to get started.

 

The way I understand Docker, is that a docker should be self-contained. So it should contain everything it needs to run, and only go to the "outside world" for file system storage, and configuration files.

 

If you are unable to do this, could you at least make an easy to follow "getting started" guide? Docker being Docker, and unRAID being unRAID, it should be more or less identical for nearly everyone.

Hi thany,

You are right, I should probably do a "getting started" guide as it all change a few years ago making the --link option redundant and that the unraid team rightfully deleted my MongoDB that was setup for wekan in lieu of the official newer MongoDB container that has different credentials, but its all there in the latest post's how to set it up today. The reason I have not bother too much with it is that wekan is more for companies and organizations that probably would have an IT guy to figure out the setup. For me as a nob, I have moved away from wekan even if it is a nice system. I have gone for simpler systems and more all around like nextcloud (not that NC is a simple system, very powerful) that has the similar functions and more other goodies to choose from. 

 

As for integrating the MongoDB, not sure if it is a docker out there to do that, but the main reason not to, is that it is better to separate the program from the DB and have two separate instances for easier and safer retention of the data. Most and many containers are doing this and it is just to get the head around it, then most containers are working in the same way with similar setup.


Kru-x

Link to post
  • 1 month later...

if anybody else is looking for a working reverse proxy config, here is a config that works fine for me. This one is based on the template of wekans github pages. All you have to do is to change the domain names in lines 12, 16, 23 and the internal IP of your Unraid server in line 38.

 

# this section is needed to proxy web-socket connections
map $http_upgrade $connection_upgrade {
    default upgrade;
    ''      close;
}

# HTTP
server {
    listen 80; # if this is not a default server, remove "default_server"
    listen [::]:80 ipv6only=on;

    server_name wekan.your-domain.com;

    # redirect non-SSL to SSL
    location / {
        rewrite     ^ https://wekan.your-domain.com$request_uri? permanent;
    }
}

# HTTPS server
server {
    listen 443 ssl http2; # we enable HTTP/2 here (previously SPDY)
    server_name wekan.your-domain.com; # this domain must match Common Name (CN) in the SSL certificate

    include /config/nginx/ssl.conf;

    # If your application is not compatible with IE <= 10, this will redirect visitors to a page advising a browser update
    # This works because IE 11 does not present itself as MSIE anymore
    if ($http_user_agent ~ "MSIE" ) {
        return 303 https://browser-update.org/update.html;
    }

    # Pass requests to Wekan.
    # If you have Wekan at https://example.com/wekan , change location to:
    # location /wekan {
    location / {
        # proxy_pass http://192.xxx.xxx.xxx:5555/wekan;
        proxy_pass http://192.xxx.xxx.xxx:5555; #Change to your internal unraid IP and the Wekan container port
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade; # allow websockets
        proxy_set_header Connection $connection_upgrade;
        proxy_set_header X-Forwarded-For $remote_addr; # preserve client IP

        # this setting allows the browser to cache the application in a way compatible with Meteor
        # on every applicaiton update the name of CSS and JS file is different, so they can be cache infinitely (here: 30 days)
        # the root path (/) MUST NOT be cached
        #if ($uri != '/wekan') {
        #    expires 30d;
        #}
    }
}

 

Link to post
  • 2 months later...

Is there any trick to getting this to work with nginx proxy manager?

EDIT: Nevermind. Solved. Nginx scheme needs to be http not https. Not sure why though. But nextcloud does that to me too. If I visit https://subdomain.mydomain.com it seems fine.

I had to use the docker link fix with MONGO_URL earlier in the thread, which worked great (so mongo and wekan on same docker network as nginxproxymanager). I changed the ROOT_URL to https://subdomain.mydomain.com

In nginx config I've got https://<unraid_ip>:5555 linked to subdomain.mydomain.com

But I keep getting 502 bad gateway errors when I visit https://subdomain.mydomain.com

Thanks!

Edited by njdowdy
SOLVED
Link to post
13 minutes ago, njdowdy said:

Is there any trick to getting this to work with nginx proxy manager?

EDIT: Nevermind. Solved. Nginx scheme needs to be http not https. Not sure why though. But nextcloud does that to me too. If I visit https://subdomain.mydomain.com it seems fine.

I had to use the docker link fix with MONGO_URL earlier in the thread, which worked great (so mongo and wekan on same docker network as nginxproxymanager). I changed the ROOT_URL to https://subdomain.mydomain.com

In nginx config I've got https://<unraid_ip>:5555 linked to subdomain.mydomain.com

But I keep getting 502 bad gateway errors when I visit https://subdomain.mydomain.com

Thanks!

You worked it out, it needs to be http in NPM as it is pointing to the internal adress that is just that, not the external one.

 

Glad you figured it out.

Kru-x

Link to post
  • 1 month later...

Can't figure what I miss...

I got to do something with mongoDB docker, or just install?

 

MongoDB:

A.thumb.png.4b55e4e11640bcd98470d3cc695f71f3.png

 

wekanteam \ WekanB.thumb.png.6f8e95375013b6d46aea6da5f790f894.png

C.thumb.png.7c864d1860b77564af8b7ef13365380e.png

 

Wekan LOG:

Quote

 

ErrorWarningSystemArrayLogin


/build/programs/server/node_modules/fibers/future.js:313
throw(ex);
^

MongoNetworkError: failed to connect to server [192.168.1.10:27017] on first connect [Error: connect EHOSTUNREACH 192.168.1.10:27017
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16) {
name: 'MongoNetworkError'
}]
at Pool.<anonymous> (/build/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/topologies/server.js:438:11)
at Pool.emit (events.js:314:20)
at /build/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/pool.js:562:14
at /build/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/pool.js:995:11
at /build/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:32:7
at callback (/build/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:280:5)
at Socket.<anonymous> (/build/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:310:7)
at Object.onceWrapper (events.js:421:26)
at Socket.emit (events.js:314:20)
at emitErrorNT (internal/streams/destroy.js:92:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
at processTicksAndRejections (internal/process/task_queues.js:84:21)

 

 

can somebody help me?

thanks!

 

Link to post
3 hours ago, Jack_T said:

Can't figure what I miss...

I got to do something with mongoDB docker, or just install?

 

MongoDB:

A.thumb.png.4b55e4e11640bcd98470d3cc695f71f3.png

 

wekanteam \ WekanB.thumb.png.6f8e95375013b6d46aea6da5f790f894.png

C.thumb.png.7c864d1860b77564af8b7ef13365380e.png

 

Wekan LOG:

 

can somebody help me?

thanks!

 

Sorry I answered a little bit too quick and now when I have read your post properly: I have seen several time that when people uses custom networks it fails, I would set it to bridged and remove the custom IP, next remove the link option and try. Ones you got it working then try with custom networks, but I think that is the problem.

 

Kru-x

Link to post
  • 2 weeks later...
1 hour ago, kyphos said:

Please can you just point me in the direction of a step by step guide....I cannot get this to work

What's the problem? Check this post screenshots:

 but leave the network to bridged. And remove the --link property. 

Kru-x

Link to post
  • 2 weeks later...

Hi everyone,

 

I am totally new to this and if you get an install error, ensure you delete the "orphan" docker container under Docker Containers; see first picture. After you delete it, go to apps, search for Wekan, and toggle the advanced view slide. Then delete --link "MongoDB db"

 

I hope it helps someone to get the last picture.

unraid_advanced_view.PNG

wekan_advanced_view.PNG

wekan_success.PNG

Link to post
  • 1 month later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.