Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

26 Good

About Marshalleq

  • Rank
    Advanced Member
  • Birthday October 17


  • Gender
  • URL
  • Location
    New Zealand
  • Personal Text

Recent Profile Visitors

450 profile views
  1. Oh! OK then, I'll check that out. Thanks.
  2. I’m fairly sure that storing the key isn’t the issue it’s that it’s plain text. I’m also fairly sure that other apps can successfully utilise stored keys that include some kind of encryption / salt, so they’re not plain text - not that I’m an expert. I’m just saying it seems like the issue is that it’s plain text not that it’s stored and I think that should be resolvable. Sorry if someone already suggested this, the thread is long on my tiny phone. Sent from my iPhone using Tapatalk
  3. It isn't a host network. It's a custom network actually. The host part in the screenshot is just the default naming from the container maker. It looks confusing because the container port is missing.
  4. I've noted on the last two 8.4 rc5 and rc4 that docker does not seem to have a field for entering the container port. This seems to happen on newly downloaded or created docker apps only. I assume don't need logs for this, but happy to provide if need be. Note in the screenshot the container port is a description of a container port, not an actual container port. This makes a new docker impossible to install, unless you don't require any port mapping. Probably could do it manually.
  5. Anyone know if the nginx portion within the letsencrypt image includes the cache capability? I added the below (+ server bloc) When I add this: proxy_cache_path /config/nginx/cache levels=1:2 keys_zone=my_cache:10m max_size=10G inactive=60m use_temp_path=off I get this: nginx: [emerg] invalid parameter "include" in /config/nginx/nginx.conf:77(edited) Line 77 is actually this line: include /etc/nginx/conf.d/*.conf;
  6. I upgraded today, thinking that because there is not a new kernel, it would upgrade. However it doesn't as I think it has a specific lock to the version? Or at least I assume kernel firmware is not the same as a kernel upgrade afaik. Downgrading requires going to a backup of libvirt.img
  7. In case it's the same here, I find this happens from time to time and I just have to delete the VM without deleting the actual VM image, then create a new one and manually point back at the original image. This tends to get me going. I'd suggest trying that, as if so, this is a long standing issue, that's probably more to do with KVM/XEN versions than unraid - though I can't be sure obviously.
  8. OK I've now read those - I don't see most of that applying except it did get me thinking about permissions again. Maybe something in the new security changes is being applied to docker files (wild and probably unlikely guess). Further if we set up dockers as root.root, that's going to be challenging for dockers that need to write files as a non-root account because how do you tell it to do that only for e.g. media folders, but not for appdata data? The way I used to get round this was to write to a share and have the share set to write as an explicit user with explicit permissions. (Written up in a three year old post of mine here). However, that would then require shares instead of direct mounts for files which is kinda horrible to be honest. But before all of that, I need to know if I should be running dockers as root now or not. The ones I've tried ARE being created as root - so maybe I should try living with it like that and see where it leads me.
  9. Since I haven't explained above, until about a week ago, I was running my dockers on an SSD, used by unassigned devices. I have recently migrated this setup to ZFS, which as expected has the same issues. I was having the issues on both configurations though. I think there's been funny business since the 6.7 series to be honest - but it's hard to tell as I didn't add any new containers during that time and I'd really rather not go back. @Frank1940thanks for the links - reading now!
  10. I'm actually not sure what the default permissions for docker are meant to be. But I 'think' they're meant to be groups set to nobody.users. Many dockers are being created root.root and I'm having weird things happen even if I try changing to nobody.users. For example downloading the official wordpress docker, creates a root.root permissions. If I add PUID / PGID variables into the docker, again it remains at root.root (even after deleting the wordpress appdata folder and starting from scratch). Further, the below line occurs in the docker log at each start and never actually writes anything into the html folder, though it DOES create the folder. "WordPress not found in /var/www/html - copying now... Complete! WordPress has been successfully copied to /var/www/html" I've changed the folder permissions and set to 777 and still the same issue. If I go into the docker container itself, e.g. docker exec -it wordpress - the html folder IS populated there - it's just not writing it to the config directory, which is set correctly and is shown by the folder name html showing up within the wordpress docker appdata folder. I had thought this issue was limited to one container, however it is also occurring in Tdarr. Is there some kind of setting I need to add I'm not aware of? Is there some rule for the template developers need to be aware of to stop this? Many thanks, Marshalleq
  11. Yeah - those routers do the loopback / rebind thing we've been talking about. Your hosts file should have worked too, but this is even better. Also the Asus usually do take the WRT. The archer if I recall correctly is actually even better than the Asus in terms of it's hardware so that could have also been an option. Great that it's sorted!
  12. I'd suggest you watch the spaceinvaderone video on youtube first.
  13. I've been poking all round your emulator trying to find a loopback / multi-homed thing or perhaps even a DNS rebind and not found anything. I've also looked in the software for custom DNS records which is also not available. Someone else may have better luck than me, but to be honest this is not uncommon with consumer routers. Which is why DD-WRT was born - you can flash your router with firmware that does have these kinds of features. The router compatibility list is here: https://wiki.dd-wrt.com/wiki/index.php/Supported_Devices#TRENDnet It appears your router is still a work in progress, but perhaps you can have a poke around there - they may have a working beta or something. So for you, the best thing will be to put the settings manually into the hosts files of your internal computers. Or get a different router firewall. If you want to go the whole hog you can get your own firewall like opnsense. Or take your luck with another consumer router. Sorry to be the bearer of bad news.
  14. And RC4 is out with a new kernel.
  15. That is the same thing as item 5 in my list. Damn these threads with multiple topics are confusing though... Sent from my iPhone using Tapatalk