CorneliousJD

Members
  • Posts

    588
  • Joined

  • Last visited

Everything posted by CorneliousJD

  1. if I recall that's just how it was made -- but given the sensitive nature of what's being stored, even temporarily, i wouldn't run it without a redis pass anyways, no sense in leaving anything open for any reason.
  2. I suppose if the new PHOTOS show up, but the thumbnails dont, at least the scanning is working, but thumbnail generation is not. if the photos don't show up at all then something is off that's a deeper problem than just the thumbnails.
  3. That's odd, I double checked my instance and it's indeed still working and generating thumbs properly. Is your periodic scanner still setup to scan for new photos? If so and nothing else seems off, I'd suggest taking this to the github issues page since it isn't unraid-specific it seems. they would be the ones better equipped to help. Of course feel free to post solutions here if you find them for others to see!
  4. Just want to say "thanks" for the Vikunja containers. what a fantastic todo app. I did add the variable of VIKUNJA_SERVICE_JWTSECRET and gave it a big long (32 character, alphanumeric) password so that JWT tokens persist across container restarts (prevents you from being forcefully logged out) I also added in my e-mail server setup so it can send me mail as well, which is probably overkill to include in the template, but the JWTSECRET might be worthwhile
  5. All the thumbnails should be in your /mnt/user/appdata/photoview/ folder -- can you verify that they are actually there and accessible? You should be able to open them and actually view them. Also expand the settings in the docker container itself and make sure that the cache is set to app/cache -- since your app/cache is there the appdata is and where the thumbnails should be stored.
  6. Shouldn't matter to my knowledge, however I'm using it with MariaDB
  7. Try hosting your own image, not imgur. It sounds like the code is working to load the image in place of the default, but it's failing to actually grab said image file to display. if you have no other way to host your own image you could always fire up an nginx docker, reverse-proxy that, and serve the image from there.
  8. Do you have n HTTP/HTTPS mis-match between the container being served (HTTPS via reverse proxy) and the logo image (http link to a logo?) If so an HTTPS page may not load the HTTP image. I am serving my container via reverse proxy (NginxProxyManager) and the logo and favicon are both linked via HTTPS as well, working fine on my end.
  9. Of course, just configure it like any other reverse proxy in nginx. If you're unfamiliar with what's required, I would suggest possibly trying NginxProxyManager instead, it vastly simplifies the process of adding new reverse proxy services.
  10. FYI for Filerun, a filerun/filerun:latest container/template already exists in CA.
  11. The default port in the template (6000) isn't liked by Chrome. It says "unsafe port" - changing it to 6100 like in the GitHub/DockerHub documentation works fine. I'd suggest updating the template.
  12. Well it is an uptime monitor so I would expect constant writes. Every time it checks it has to log if it's up, or if it's down.
  13. Thats just part of SQLite and how it functions. Iirc it's similar to journal
  14. There should be a web UI demo/trial environment on onlyoffice/documentserver Make sure you're using that container specifically if you're trying to replicate my setup, as that's the official container. As far as reverse proxy goes, I'm using NGINX Proxy Manager (NPM) and I just had to plug in the reverse proxy info, HTTP source w/ the proper port and that was it.
  15. yes, very easy to get it working w/ FileRun! I installed the onlyoffice/documentserver container, set JWT enabled and created a JWT secret (this protects my onlyoffice from random public use) and threw it behind my reverse proxy, and pointed FileRun to it and gave it the JWT secret so it can authenticate. NOTE: I could not get it to work unless I put it behind my reverse proxy, but the JWT token makes that not a concern. That's it. easy peasy If needed, here's the bottom two variables referencing JWT, you'll need to add those yourself - as the template doesn't have them included by default.
  16. I honestly chased this for months/years. Never got any better honestly. I just eventually gave up on Nextcloud completely. I wasn't willing to run dedicated VM for it, so that was out of question for me. I ended up installing FileRun in place of Nextcloud, and it is BLAZING fast in comparison. Unbelievably so honestly, and it does what i needed from Nextcloud. All the extra nextcloud crap I didn't use was probably contributing to the slowdowns so it feels good to ditch that and move on honestly. Good luck to anyone who continues to chase NC performance. I've seen countless threads and posts about it, and usually people just blame the OP for it being slow for "doing something wrong" but I never see the threads actually get RESOLVED with someone saying they found/fixed their performance issues. GL;HF
  17. Thanks, I was only part correct here then - I didn't know it required extra variables, but thank you for linking to the process so others can get this setup as well!
  18. Are you using the ephemeral version? Since that's wiped 100% every time a container restart or update happens then there's no way to persist login info. You would at a minimum need to be using the Postgres version to setup logins if that was something you required. I am not using the Postgres version myself though so I can't say with certainty that it would be available there either, but based on the demo website it should be!
  19. Well hang on a minute, lol. No need to bury the project. I didn't create and I do not maintain Tandoor Recipes, I only made a docker template for it on unraid. The project is still very much active and in-use by many. I just don't personally use it. I'd suggest reaching out on the devs github page if you have issues with the project itself.
  20. i don't personally use this container anymore, I opted to manage my recipes a different way, however there shouldn't be any GUI performance issues, espcially w/ an external database. The only way I could see it getting slow is if you've packed it with a ton of recipes. Is there anything specifically that is slow?
  21. I would assume TZ is being set by unraid, but if it's not reflecting properly I'd check with the dev of uptimekuma instead on the github/issues page. Sorry I can't be of more direct help!
  22. The second section in the template is asking where you want to map /app/cache to, as a volume. It should default to your cache (appdata) directory.
  23. So it seems the root cause of this issue is NGINX Proxy Manager (NPM) issue as noted here: https://github.com/jc21/nginx-proxy-manager/issues/1717 I would say the real fix here is to roll back until they fix the problem. 2.9.13 seems to work fine. If you're using the jlesage NPM image, you can add :v1.23.1 to the end of the docker image it pulls to downgrade, and that fixes the issue as well. When NPM fixes the problem itself, this .env modification we are talking about shouldn't be needed anymore.
  24. In that directory there's only one file that is .env (no filename, just .env extension) \appdata\heimdall\www\.env
  25. If you aren't a fan of command line you can just edit it via going to \appdata\heimdall\www and then opening the .env file with a text editor of your choice and editing it there. I put in https://sub.domain.com and saved it, restarted container, and I'm good to go now again.