akshunj

Hello all. I'm not new to this game, but I've never even contemplated this particular issue before, so I have some really rudimentary questions if someone has the time to nurse me through this. BACKSTORY: I have been running my server with one ethernet connection (it supports 4) that comes directly from my router. My internet connection is Comcast, and I'm running up against data caps. Long story, I am subscribing to a second ISP (T-Mobile Home Internet) with no data caps, and dropping Comcast service down to the minimum package (ends up being cheaper than paying for Comcast without caps, and I can't bear to give Comcast another single penny). QUESTIONS: I'd like to run the T-Mo connection through my server on eth1, but expose two and only two Docker containers to exclusively use eth1. Can any brave soul point me to a wiki or give me some basic steps? I've poked into the Unraid network and docker settings, and I'm guessing there's some combo of interface bonding that needs to happen, but I am super out of my depth with any networking. Any help is appreciated. Thanks!

This solution worked fine (watch for Start in the log, then stop container, then start again). A note of some kind on the CA page would be super helpful.

confirming same here. Solved the problem for me

@Josh.5Seriously man, thank you for this. I use a Chromebook for my daily driver, and it can't run Steam. But I have a juiced-up Nvidia card in my UnRaid server. Now I get to use it. Thanks again

thanks for bringing this docker container to the Unraid app store. Works great!

Latest update to Ghost pushes to v.4. It will break the container. Please see this thread for how to correct. You will need to remove the "migrations" and "migrations_lock" tables from your mariadb database. More here: https://forum.ghost.org/t/db-error-after-upgrading-to-v4/20921/6 And if you're not database saavy (like me), check this out for some step by step: https://www.tutorialspoint.com/mariadb/mariadb_drop_tables.htm

Looks like Ghost 4 is out. Any plans to upgrade the container? It appears to be a major upgrade that requires a migration to the new version... Thanks for a great container!

Answered my own question. The spectre-importer has the same issue. Changing the container port and WebUI port from 80 to 8080 fixed the issue. Cheers

Hi. Trying to get the spectre-importer going. No errors in the docker log, but I can't even get to the WebUI. "connection refused". Tried changing ports, but nada. Any thoughts?

I'm using Nextcloud stable through Swag with MariaDB running off SSD cache drive. Redis also running. Seeing the same issues as you guys. It's awesome in terms of use-cases, but it is SLOW. Slow to navigate to site page, slow going between apps. Things like Talk and OnlyOffice take many seconds to load. I run Ombi, wallabag, and freshrss also through Swag and they are LOADS faster. Plex is lightning fast. Is it worth migrating the database to PostgreSQL? This doesn't feel like a database issue... like that initial connection time is wild just getting to the dashboard.

So, I am not understanding a few things. Why is this necessary? And what does it do? And Thanks, by the way!

Looks like if you're on the Nextcloud stable channel, update to 20.0.4 is available. Also, the internal onlyoffice nextcloud app/plugin is updated to 6.2.0. Anyone know if this fixes the onlyoffice container issues? Going to take the plunge while on vacation next week.

You've been running this exact same setup for years with no issues? But when you upgraded to the new beta unraid you started to experience issues? Is that correct? Just trying to piece together the timeline of when your issues began

Speaking only from personal experience, if all your devices are connected to the same controller, one bad drive can introduce kernel conditions where the unraid kicks it and every drive out of the array. Sometimes you need to do a little trial and error with hardware issues like this. Pull a suspect drive, replace cables, run the array for a bit, check diagnostics, etc. If you've been running this setup for years without issue, it's likely a bad drive or cable. I'm not an unraid expert, but I believe the disabled drive will stay that way till you decide if/how you want to re-integrate it. I would try to diagnose the problem drive first.

Maybe I am missing something... The logs end well before 21:19. No errors on anything I can see

Life saver! Thanks, man!

Hello. I had the OpenOfficeDocumentServer working well until the most recent update. Now I cannot connect. Not sure what changed. Using reverse proxy through SWAG. When I try to hit it via command-line, here's what I get: wget https://docserver.myserver.org --2020-12-05 11:55:55-- https://docserver.myserver.org/ Resolving docserver.myserver.org (docserver.myserver.org)... xxx.xxx.xx.xx Connecting to docserver.myserver.org (docserver.myserver.org)|xxx.xxx.xx.xx|:443... connected. HTTP request sent, awaiting response... 400 Bad Request 2020-12-05 11:55:55 ERROR 400: Bad Request. Been googling around. Tried reinstalling container. Copying over the key files again. Restarted SWAG. Same result. Document Server was working perfectly before the update and its error logs are empty. SWAG's error logs don't seem to show any problems with the document server access. Any ideas out there? UPDATE: Getting this error too, but unsure if its related... Not sure what this is referring to...

Each one of those should be a separate command: su - archivebox cd /data archivebox init archivebox manage createsuperuser All done inside of docker console

Love this docker!!! Precisely what I needed in life! For the life of me, I can't figure out how to make it sync a subfolder with a space in the filename. Grrr. I have tried quotes around the subfolder, and a "\" without quotes, but nothing works. Anyway, that's just a niggle. Thanks for this awesomeness!

I know this is months later, but: 1. the error message for the mobile app is because the api password is not set. If you set this and fill in the same password when prompted on the mobile app, you are set. 2. Readrops is a fine android RSS reader, and it supports freshrss.

Just pulled down the most recent archivebox docker version 0.4.21. Installed with default settings, then followed these instructions: https://github.com/A75G/docker-templates/blob/master/README.md#first-installation No issues. Everything working perfectly.

Try Luckybackup. Its an rsync front end. In the CA apps repository

You may also be able to see what's happening in your Plex logs: settings-->troubleshooting-->download logs You can post them to the Plex forum and the community there can be a second set of eyes. I will tell you from experience, mesh wifi and a plex server instance is a crapshoot. Especially if you are doing any type of transcoding (and I don't see an Intel CPU or a GPU capable of hardware transcodes), you could be running into a combination of issues with CPU transcoding and network bandwidth/performance. I'm a loooooongtime Plex user, and the only network setup that I can trust for my 20 person family/friend circle (averaging 4-8 simultaneous streams) is wired gigabit ethernet, and hardware transcoding with either Intel Quicksync or an Nvidia (patched) GPU.

Ah, sorry man. I try to help out with hardware issues, but with actual unraid stuff, I am still new myself. Will let someone else take a stab. I still don't quite understand what you're trying to do. I do know that if a drive fails (or goes missing), as long as parity is valid then you have access to the emulated contents of the drive.

Here's where your troubles begin: Oct 21 00:19:33 loki kernel: mpt2sas_cm0: log_info(0x31120101): originator(PL), code(0x12), sub_code(0x0101) Oct 21 00:19:33 loki kernel: mpt2sas_cm0: log_info(0x31110101): originator(PL), code(0x11), sub_code(0x0101) Looks like the sata controller is not getting along with the drive at /dev/sdf. I am BY NO MEANS an expert. I think after so many read errors at the kernel level, unraid is likely knocking the drive out of the pool. Someone correct me if I'm wrong. Looking at Smart for that device: UDMA_CRC_Error_Count -O--CK 200 199 000 - 9 You've got some CRC errors. I would check your cable connections, and try re-seating the drive. Then run an extended Smart test on the drive and post the results.