• Content Count

  • Joined

  • Last visited

Everything posted by CorneliousJD

  1. Thank you for continuing to update everyone on this, I appreciate it even though I've been able to work around the issue with a VLAN. My only "fixes" are workarounds for now - I'm only sharing them here to help people who are frustrated by the crasahes to do something free or at least very cheap (add a $15 NIC for another interface) to get around the issue. hoping someone here has real answers at some point though, that would be great! If there's anything else I can provide from my system please let me know, happy to keep providing logs/diags/etc.
  2. What service is it? Out of curiosity at this point really. What about adding another NIC (if your motherboard doesn't already have 2 or more LAN ports?) That could be a very cheap $15 card for a gigabit NIC. (referral link) I beleive that way you could keep the same IP address, but give it its own network interface instead?
  3. Is there a reason you can't run a VLAN? (hardware doesn't support it?) Alternatively, you could add a 2nd NIC into your server and run it on a separate IP address from that I believe? I don't know the specifics of this exactly, but I think that would work so it's not assigned to br0 anymore? Also, are you able to simply not run that container on its own IP? I don't know of any other way besides those two options personally that will fix this. I had success with the VLAN method, and implemented it in less than 10 minutes total.
  4. To each their own, a single vlan for Dockers is easier than setting up ESXi IMO. Well I agree, I didn't want to complicate my home network any further either, it was an extremely simple process that took me less than 10 minutes to complete. In my eyes 10 minutes to avoid crashes was definitely worth it. I've already linked to post somewhere in this thread that goes over the details of adding a docker VLAN, complete with photos!
  5. Not a dev, but as noted in this thread a few times it's your br0 ones causing the issue. Not bridge vs host. You probably need to put those on a separate vlan. This is admittedly a workaround, but one that's worked for me. Stable with zero crashes since doing it over a month ago
  6. So I would actually strongly recommend against using SQLite. SQLite in photo apps like this scales HORRIBLY and is bound to cause you all sorts of slowness, issues, and headaches. You would probably need to specify sqlite as a db driver tho. see here: PHOTOVIEW_DATABASE_DRIVER=mysql is the default. I would really just suggest spinning up MariaDB though, it's not difficult to do.
  7. You can, or you can just create multiple databases inside of one MariaDB container. Choice is yours
  8. @limetech Is there work being done on this still since it wasn't resolved as previously thought?
  9. It's case sensitive, try /photos in the container, no capital.
  10. New send container is working, however I cannot seem to get passwords to work, I enter something easy like "test" or "test123" as a password and it then tells me later the password is incorrect. EDIT - Disregard, once I actually set it all up via reverse proxy, it seems to be accepting passwords now. PS you do need some Redis persistence. I have mine setup like this, databse saved to appdata, and AOF disabled, to keep the Redis database extremly small (given it's expiring nature)
  11. Sorry, I'm not using custom scrapers, but is there a config page that you have to tell it where the scrapers live? Would need to make sure that it matches up with what the container expects so the container path and your appdata for scrapers line up. Maybe someone else with Scrapers enabled can chime in here?
  12. In the container template you need to pick "Show more settings ..." at the bottom and configure all your Postgres stuff there. the /data/recipes.db is the default location of the SQLite database. If you're using postgres that should just be a database name like "tandoorrecipes" Here's my config as an example, with password redacted
  13. Bottom right, you don't need a business email. Just use your personal email account when you pay.
  14. So that was just merged into develop branch 4 commits ago, it's likely not live yet and not in the container yet unfortunately.
  15. This is likely a question suited for their github page or more direct contact w/ the developers, this thread should be used for unraid-specific releated issues/support.
  16. I don't beleive so, this container would have no way of communicating with that file.
  17. Unraid-specific support for Pastey, please post here. For Pastey-related issues, it's best to contact the dev on GitHub
  18. You still need to have something automatically checking for upates. I would definately suggest using CA Auto Update for this. Yes, I am on Current Version: 0.15.1 There has been updates the past 2 days.
  19. Do you have ca auto update installed? It will check for updates and install per your config.
  20. Ok, so I came to post about this (FTP server running). I deleted the /boot/config/plugins/fix.common.problems/ignoreList.json file completely, rescanned and saw that error, ignored it, resacnned again and it's still showing up like this (listed both as an active one, and an ignored one) Version: 2021.03.30a
  21. It should stay like that now that you've manually activated, you should be able to stop/restart the docker, and do "force update" and verify that it still works after that.
  22. In settings - amp core, make sure startup mode is "start the application" This actually causes it to start the instance AND startup the server. Also make sure your instance itself is set to start on boot too.
  23. I was able to get pings to work by chaning --user 99:100 to --user 0:0 in advanced config of the template. this lets ping work it seems. EDIT: Then it was stuck in setup mode, but I fixed that too. Went to console on unraid, and did the following commands. cd /mnt/user/appdata/statping sudo chown root:users . Restarted container and it's running as root now, reads/accepts the config, and ping tests work in StatPing as expected. PS - For what it's wroth, it seems the SQLite database gets corrupted all the freaking time. Haven't had the i
  24. Complete server halt, local console wouldn't respond (it just displayed the kernel panic/halt on the screen). All connections severed to the server, had to reboot it by power button.
  25. FWIW I was never able to create them on demand despite trying to, although for me it seemed to happen every ~60 hours or so (roughly) I would never hit 3 days of uptime before I made VLANs. I also never had call traces "build up" - it was one and done, resulting in a kernel panic for me. I still have host access enabled with VLANs and I've eliminated my call traces and kernel panics so far. Uptime 17 days 4 hours 8 minutes since making those changes. If anyone finds a way to force this to happen I would consider purposely recreating the issue to help