MattFaz

I'm getting the same error and cannot figure out why either. My Unraid Server is at 192.168.0.25, using bridge for MongoDB and br0 for the UniFi Network Application but I don't believe that should be an issue. I've tried moving MongoDB to the same network (using br0) and it didn't change anything. MongoDb: docker run -d --name='MongoDB' --net='bridge' -e TZ="Australia/Sydney" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tower" -e HOST_CONTAINERNAME="MongoDB" -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://raw.githubusercontent.com/jason-bean/docker-templates/master/jasonbean-repo/mongo.sh-600x600.png' -p '27017:27017/tcp' -v '/mnt/user/appdata/mongodb/':'/data/db':'rw' 'mongo:4.4' 0f7783e566a2de9b4d39d316d114ed69b88110c2e8abb76078e130bad6178db5 I create the user etc. by connecting to the console of that MongoDB container and running the 2 commands: db.getSiblingDB("UniFi").createUser({ user: "UniFi", pwd: "xxxxx", roles: [{ role: "dbOwner", db: "UniFi" }] }); db.getSiblingDB("UniFi_stat").createUser({ user: "UniFi", pwd: "xxxxx", roles: [{ role: "dbOwner", db: "UniFi_stat" }] }); unifi-network-application: docker run -d --name='unifi-network-application' --net='br0' --ip='192.168.0.99' -e TZ="Australia/Sydney" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tower" -e HOST_CONTAINERNAME="unifi-network-application" -e 'TCP_PORT_8443'='8443' -e 'UDP_PORT_3478'='3478' -e 'UDP_PORT_10001'='10001' -e 'TCP_PORT_8080'='8080' -e 'UDP_PORT_1900'='1900' -e 'TCP_PORT_8843'='8843' -e 'TCP_PORT_8880'='8880' -e 'TCP_PORT_6789'='6789' -e 'UDP_PORT_5514'='5514' -e 'MONGO_USER'='UniFi' -e 'MONGO_PASS'='xxxxx' -e 'MONGO_HOST'='192.168.0.25' -e 'MONGO_PORT'='27017' -e 'MONGO_DBNAME'='UniFi' -e 'MEM_LIMIT'='1024' -e 'MEM_STARTUP'='1024' -e 'MONGO_TLS'='' -e 'MONGO_AUTHSOURCE'='' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='022' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/unifi-network-application-icon.png' -v '/mnt/user/appdata/unifi-network-application':'/config':'rw' 'lscr.io/linuxserver/unifi-network-application' fe2fadf61cd8f3ff452dd6be5484be2a5f54a6a6edf1e516ed925155958431fb I just get this in the UniFi logs: *** Waiting for MONGO_HOST 192.168.0.25 to be reachable. *** *** Defined MONGO_HOST 192.168.0.25 is not reachable, cannot proceed. *** Any help would be much appreciated. EDIT: Got it working, I had to go to Settings > Docker and make sure 'Host access to custom networks' was set to Enabled.

@maddog @john_smith @AirRicB You need to setup the Postgres database yourself, it will not create one for you. You then need to provide the details when setting up the FIrefly-iii container. You can use an app like pgadmin to perform this, you don't need to create any tables. Just create the database, user, and password (if not using an existing user and pass).

Do you mean on the official Firefly-iii docs? If so I'm not sure the developer himself would create the documentation but I'm sure they'd be willing to accept it if someone wrote it up and created a PR on the docs repo: https://github.com/firefly-iii/docs Hmm sorry I'm not sure, have you checked logs or inspected console when you try to login to see if it's reporting any errors? I use SWAG and access firefly via subdomain and it is working fine for me. Here is my `firefly.subdomain.conf` file if it helps: server { listen 443 ssl; listen [::]:443 ssl; server_name firefly.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app 192.168.0.25; set $upstream_port 5555; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } } I'm not sure how easily you can move the old container to this new one, I've only performed fresh installs of the container and it's related data. Looking at the Github repo it looks like there may be some issues when backdating, are you trying to set the date to a date in the past? The developer advised when creating you should enter a future date, then edit to back date: https://github.com/firefly-iii/firefly-iii/issues/7683 Above I posted my .conf file if you're using SWAG, wouldn't need to deal with .env files in that case. Otherwise you could add the .env variables as a variable to the container, or create a folder path and map it to the container. This can be done when editing the container:

Thanks for posting the solution @wieli99, makes sense! Glad you've been able to get it running now

Are you using the Postgresql15 community app by jj9987? I just did a fresh install of that Postgres15 container and Firefly-iii and it worked without issues. Are you using the default Postgres port of 5432? I've just realised I forgot to include the DB_PORT variable so if you're using something different it may have caused issues. I've updated the template just now to add it and it should be live in the next couple hours.

Hey all 👋🏼 This is a support thread for any apps hosted in my repository: https://github.com/MattFaz/unraid_templates Firefly-iii Project: https://www.firefly-iii.org/ GitHub https://github.com/firefly-iii/firefly-iii Documentation: https://docs.firefly-iii.org/ Note: You need to create the Database in PostgreSQL, it does not create it for you. Firefly-iii Data Importer Project: https://docs.firefly-iii.org/data-importer/ Github: https://github.com/firefly-iii/data-importer Documentation: https://docs.firefly-iii.org/data-importer

Thanks for this container @kostecki, really like Ntfy as a self hosted solution. Is there any reason adding the extra Variable: `web-root: disable` wouldn't work as mentioned in the FAQ? I can't find any server.yml file to edit it so figured this would work...

Nevermind! Settings > Management Access and provision a certificate. Worked after I did that

Installing plugin provides the following output: plugin: installing: dynamix.unraid.net.plg plugin: downloading: dynamix.unraid.net.plg ... 100% plugin: downloading: dynamix.unraid.net.plg ... done Executing hook script: pre_plugin_checks Installing dynamix.unraid.net.plg 2022.11.29.0742 with Unraid API 2.54.0 plugin: downloading: dynamix.unraid.net-2022.11.29.0742.txz ... plugin: dynamix.unraid.net-2022.11.29.0742.txz download failure (SSL verification failure) Executing hook script: post_plugin_checks It then gets stuck in Pending state. How do I resolve this error?

Helpful to know thanks blaine07! That guide is written by me and I didn't face the AVX issues, I will add that as a note.

Would you be able to provide a guide on how you installed this plugin? I'm comfortable with the rest but really struggling at this step.

Are you sure you're referring to the correct WikiJS container? The Linuxserver.io container does not ask for any Postgres host/urls. You might be referring to the selfhosters one? Which does require the steps you mentioned above.

Just stumbled across the DebianBullseye container, wanted it as a good way to be able to browse personal sites while on a work device 🙈 Props to @ich777, this works really well! Super fast, easy to setup, I am super impressed. Thank you for creating this!

Facing issues when trying to install wikijs, receiving the following error message: Unable to find image 'requarks/wiki:beta' locally docker: Error response from daemon: manifest for requarks/wiki:beta not found: manifest unknown: manifest unknown. See 'docker run --help'. Edit: Updated repository value from requarks/wiki:beta to requarks/wiki:latest and it installed successfully. However once you login it receives auth errors, same issue as the linuxserver.io container, must be a WikiJS issue.

Exactly the same for me, currently no way to get past this that I can find.

Just installed this, the "--runtime=nvidia" value was already there by default. I also didn't modify "Nvidia GPU UUID" value as it was set to "all" by default and that seemed to work fine. Got it running, have tried playing Factorio and all worked well! Thanks OP!

Latest version of this container is not working for me either, cant load the webpage at all. What is the best method to downgrade in UnRaid? Delete it and add it again from CA? Ensuring I specify a specific release? Will all the repos/data I had in Gitea be restored or have I lost all that now?

Looks like the docker container for this is a disaster, struggling to get anywhere as well. Doesn't look there is a single person who has managed to get it working yet...

Chkdisk appears to have solved the issue, so we've made a backup for next time this happens! Thank you

The Unraid server at my parents house has gone down and is not responsive via WebUI. I can still access it via SSH though, my parents had already tried the "IT 101" methods of powering it off/on. I have attached the Syslog however. Looks like it is just hanging at the following and repeating it indefinitely: Dec 4 22:01:01 Tower kernel: FAT-fs (sda1): Directory bread(block 393910) failed Any advise? I think this means the USB or USB port are stuffed is that correct? The USB is quite old so not totally surprised if that is the case. Is there a guide on how to replace it (with the license key etc.) and just put a new USB back in? Thank you. logs.txt

Anybody have a solve for the following issue: Domain name abc.com hosted in Cloudflare and dynamic dns updated automatically by the Cloudflare docker (Cloudflare Proxy = Enabled) CNAME wg points to abc.com (Cloudflare Proxy = Enabled) Anything coming in via abc.com goes through NGINX Proxy Manager docker and goes to the relevant application there (relevant for other domains) Wireguard doesn't seem to work if I add Cloudflare Proxy = Enabled to the wg CNAME, however if I don't then it exposes the ip of the domain name (abc.com) which I'd rather keep proxied. All my other services use a CNAME pointing to abc.com and proxied that works fine. But no luck with Wireguard.

Is there any current issue with this? A completely fresh install the Username and Password don't work, just always says they are invalid.

Ohhh right, sorry I totally misunderstood. I'm still confused on how to setup LSIO's LE container with Authentication (and multiple domain names), but regardless I can confirm this solution has worked brilliantly: Thanks @jonathanm - all sorted now

Sorry, I should've clarified that having Authentication in front of the Static Site is a requirement. Which is the reason I went for NPM.

Boom! Okay I can confirm it does prompt for username and password if I remove the advanced config! So for some reason adding this to the advanced config kills the authentication: location / { root /websites/guide; } That is the only way I know how to host a static site with Auth though... Is this expected behavior? Is there another method of hosting a static site on my UnRaid Server with Auth that I am not across?