Kru-x

I got this post from user "dnLL", just wanted to answer and maybe clarify to others! Hi, "dnLL" First of all I didn't create this container merely added it to unraid for others like me to use. I guess there is no specific reason that it would be better (or worse to my knowledge) to use a docker or this container made in python, your solution might even be better For me it is the easiness to throw in a container, fill out the detail's and away you go, I can toss it away if needed. I am more in too web development I am not that confident to make my own script's , don't like the copy and paste to get it working and if I don't fully understand it i rather trust in others that do, to make the task. Similar to all other docker containers I use, but most others are more advanced then this one thought. Hope it answer your question, R Kru-x

Used this docker for years now on my server, handy tool to update my dynamic DNS directly on my Godaddy account. "Docker image to provide a DDNS service for godaddy domains. Uses the GoDaddy REST API to update the given domain's DNS IP address to the public IP address of the host it is executing on. Performs a check every 10 minutes, but you can alter this if you like by modifying /etc/cron.d/godaddy-ddns inside the container." If you have problems with adding multiple Domains, you might have to add them as A names, refer to this post by JamiePhonic

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.

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

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

Hi, Not sure what you are asking? To set up a Nginx proxy server or the settings for Wekan to work in the setup with one? Proxy server: ~ I recently switched and now use the brilliant "Nginx Proxy Manager" docker container (you find it in apps) for all my internal domains connected to internet. Wekan setup: ~ The setting "Varible ROOT_URL:" is where you set the external/internal address you have, ex. https://cloud.mysite.com for external address, or http://192.168.1.100:3300 for internal only access Hope it helps, Kru-x

Hi Nik82, Yea you are right and it is a bug that the wekan team would be aware about, sure it is going to be rectified within days. Meantime if you don't want to wait just put the version tag on the "repository" you want to use. ie, revert to the older container. Just add the version number after the repository like "wekanteam/wekan:v3.44". You can see all he version numbers in wekan teams image in docker hub. Just keep an eye on it and delete version number to use the lastest build when the problem is fixed.

Sorry not MONGO_URL I meant ROOT_URL,

Im not sure if this is the problem for the moment as mine works fine, I think many people uses the old mquandalle's container and not the Wekanteam ones as described in the first post of this thread. But thanks for pointing me to the issue, good to know if it causes problems in the future.

See the above answer or my first post in this thread, the --link mongodb:db should be included. That's a docker function for the containers to link the containers to each other. In your case I am not sure as I don't use separate networks but the MONGO_URL is for the the internal working ex. if you access wekan from a different ip address eg. if you are behind a reverse proxy. How did your configuration look like b4 the "crash" as the data resides in the DB saved in your wekan DBfolder, in your case I would delete both containers (NOT the wekanDB folder) follow the instruction on the updated versions. And try to put your "mongodb://10.72.0.140:27017/db" in front of the --link. But if you got it to work, great.

Hi, You should probably try to change the containers to the official ones, see the first post in this thread, I don't use mquandalle container anymore . On the other hand you got it to work with a solution I would have used if it goes haywire, and if it works why change if you are not like me wanting the absolute latest version.

Hmm, it's above my knowledge. But I would try to delete both containers and add them again, as long as you don't delete the mongo DB folder the information within should be retained. Sorry

It works fine, used it for years. The -- link (if you mean in the setup, is a docker function ) and is used to link the two containers together. it should say --link "MongoDB:db" if "MongoDB" is your mongo container. And where did you get the "Mongo_URL" from? My template is using "ROOT_URL" and that should be set to "http://yoursite.com" to make it work behind your proxy. Hope it helps, Kru-x

Hi, No such as stupid .. 🙂 without knowing what you are looking for, the image itself do not need to be mapped to unraid or any folder within as the container only stores any info in the mongo-database, maybe I shouldn't have added that option. I am not sure what logs are kept but if there is any they are stored in the container itself, had a quick look and there is a few logfile is var/log.

Hi, it was that I had used an template that should have been used with my mongoDB container, that changed. I have update the template, so try this. Leave the mongo db as it is and delete the wekan template and the container when asked, add go to community applications and add the template from there, make sure the template are using from https://hub.docker.com/r/wekanteam/wekan/ (you see it in advanced settings). Then adjust your settings as per your settings above, you don't have to use "mail url & mail from" just leave them blank until you want wekan to send mails. You can leave port 5555 if you have not assigned it to another container. That should do it, let me know, Kru-x

Sorry for any inconvenience there was a change that I didn't take in to account, I have now updated my repo and are using the container from the wekanteam/wekan. Until the Community Application has merge the changes you can install the container by: Installation Go to the unRAID control panel -> extensions -> Docker In the textarea for Template repositories add https://github.com/Kru-x/unraid-docker-templates and press save. Use the MongoDB container from Taddeusz' Repository, can as well be found in Community Applications.

Hi and yes it is a great program I use it all the time, you have to link the DB container under Extra Parameters, have you done this? If not flick the switch "Advance View" and in the field add --link "mongodb:db" this will link (connect) the two containers together. Let me know if it works for you, R Kru-x

Sorry you are right, I misunderstood the problem with Radarr. The downloaded files won't get processed by radarr and are showns as "no file exist to be processed", I thought it was a permission problem. But it has something to do with how I mount the folders in the docker containers, still don't know why but got it to work by mounting a root folder eg I couldn't mount the "download" folder directly in the containers and had to mount a root folder to get it to work. eg unraid and then point all the way to the DL folder in the program. Strange.

Permission issues, I just installed this container on my second unraid server EXACTLY the same as on my first one, but when I download a file SABnzbd unpacks the folder with permission 777 but the file within get a 666 permission and this prevents radarr to process the file. Any ideas what I can do? And yes I have set the "Permissions for completed downloads" to 777. Tnks!

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. ROOT_URL is for connecting from the outside world and I use port 5555, so in my setup I connect to it 192.168.1.100:5555, I also have it setup so I reach it from internet but that is a longer story not needing it to work from the internal network. The share path I use /mnt/user and the AppData Config Path: /mnt/user/appdata/mongodb-wekan/ where the DB is stored. Hope it helps,

Now I am really confused, it wont show up in the community application but if I add my repo it will, so it should work. In the docker tab under Docker Repositories: is this where you added my repo? If you did it should show up in templates when you add a new container.

Sorry Boxland, It seem like it is gone from there as well, don't know what have happened, but you can use the mongodB that is there it won't matter what MongoDB container u use. I have to look in to what have happened.

Hi Boxland, The easiest to do is to install the brilliant Unraids Community plugin (made by Squid, that answered you earlier), read: https://forums.unraid.net/topic/38582-plug-in-community-applications/ There you can install and search most of the apps for unraid and no need to add individual template libraries, let me know.

What version is pulled? When I did the template I used mquandalle's official image but now it seems like the project has been tanken over by someone else, but still the image should have been updated with the latest version. Have not used it for a while but is going to install it again and will update to right docker if needed in due time. And for the http's connection it would work, just a matter how you do it, have you set up your server for it it wouldn't be any problem. But to be honest I wouldn't open-up my server just to have access to this program, but it depends on your requirements of-course. I have only opened up my server for my web site and ftp, all other tasks I need to do in my server I use openvpn to connect to it when on the road.

No worries and I am not entirely sure what you mean with "still the best way"? Docker is the best way to keep any program separated from unraid (the server) itself and even if you probably could install it or make a plugin for it, why would you? So yes I believe it is still the best way, depending on what exactly you mean of course.