nug
Members-
Posts
38 -
Joined
-
Last visited
Converted
-
Gender
Undisclosed
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
nug's Achievements
Noob (1/14)
1
Reputation
-
I came here looking to solve this exact same issue as well. This started a few days ago when I updated the Nextcloud docker container.
-
Every email and on both accounts that I have fetching.
-
My Paperless was working well for a while but my mail fetching doesn't seem to work anymore. When I manually add files by drag and drop or browse files it all works fine. When I run the mail fetcher I get this in the paperless.log This is also shown in the docker log: The mail fetching side of things seems to be working fine: I have 777 permissions on my three mounted Media, Consume and Export directories and as I said - manual uploads work fine. Has anyone had any issues with mail fetching lately?
-
...and I'm an idiot. Thanks very much mate! Next question, does anyone have ssh connections working with public key authentication working with this container? No matter what I do I can only seem to connect successfully using a password. When I use a private/public key pair it always just asks for the passphrase - even if there isn't one and if I set a passphrase it doesn't like that either.
-
So I can get Duo authentication working with this container ok. The strange thing is that this only works when I connect via the local IP of the container internally. When I try and connect through my Nginx reverse proxy it shows me this: When I hit continue, I just get: It never attempt to send a push or anything. Has anyone else got this working through Nginx?
-
Thanks so much for this info guys, I went to check my graphs before and wondered what the hell was going on - I'd lost connection to everything! After reading your posts and changing the repo to be influxdb:1.8 I was back up and running in about 30 seconds. Much appreciated!
-
Thanks for all of your hard work SpaceInvaderOne - great stuff! Just a quick question to fix a niggling issue (everything else is working perfectly) - when I boot it up my Logitech bluetooth keyboard and mouse (using the supplied USB dongle passed through) don't work on the boot screen so I can't select the boot partition. If I plug a USB keyboard in I can use it to boot and then the Logitech peripherals work fine within Big Sur. Is there a way I can either get the keyboard working in the boot screen or get it to auto boot straight into Big Sur?
-
For the record - I'm an idiot. It would have been working all along if I didn't accidentally name the LE conf file - jitsimeet.subdomain.com. Fixed that up, restarted LE and bang! She's up and running. Thanks for the help anyway!
-
@tknx I noticed that but was trying to keep my current setup as the rest of my reverse proxy/containers work ok with what I have now, which is a VLAN created off of BR0: I like being able to use a VLAN as I have a bit more control in pfsense for firewalling, etc. I went back to original video that he setup that Proxynet (the first 'setup a reverse proxy' one) and all he does is 'docker create network proxynet' but that must register it differently for Docker to use. I noticed there is a difference between a VLAN created in Unraid and a Docker network: I suspect it's the 'bridge' that allows it to work with Docker better? I thought I might be onto something when I found an option in the Docker settings for 'Allow access to custom networks', which I've now enabled but that hasn't made a difference. I'll try swapping my LE container and the rest of my proxied containers across to a new docker network today and see how I go - thanks for the suggestion.
-
nug started following X399 Bluetooth and WIFI passthrough to Win10 VM , Jitsi? and Passthrough RX580
-
I just went through SpaceInvaderOne's vid for Jitsi (great work mate!) - all seems to be working internally. When I tried to connect via https://meet.domain.com/ I just get the default LetsEncrypt page, "Welcome to our server". I've got a pfSense firewall forwarding 4443 and 10000 to my unraid IP. I've got other containers working with the LetsEncrypt reverse proxy. I'm assuming I have something wrong in my jitsimeet.subdomain.conf file but I'm just using the one attached to SpaceInvaderOne's video with no changes. The only hint that I can see is that in Portainer I don't have any published ports against any of the containers (I see them in the video). I can ping 'meet.jitsi', etc from the LE container so I know it can see/reach the four jitsi containers - I'm just not sure about the ports. Any suggestions?
-
Yep, mine has been doing exactly the same thing for the last few days
-
I'll be keeping an eye on this post. I've just purchased a RX570 and having the same issue. I've had some luck with Linux VMs but not Windows.
-
I'm trying to have a consistant Bluetooth module in my Win10 VM. I seem to be able to passthrough my integrated WIFI module (Intel Corporation Dual Band Wireless-AC 3168NGW) and its attached Bluetooth to my main Win10 VM, which is great. However I don't seem to be able to keep this after a reboot of the VM. I've added the ID to my Syslinux config to isolate the device but I think the issue is because the WIFI card is a PCI device but the attached bluetooth actually shows up as a USB device (Bus 001 Device 002:ID 8087:0aa7 Intel Corp). In my VM config I have to select both of these for it to successfully passthrough, which is fine but I think that might be why it's not surviving a reset. I have a funny feeling that the solution might be adding/isolating the entire USB controller as well, which I wasn't overly keen on doing if I can avoid it. Does anyone know a solution for this?
-
I'm so close to getting working, it's so frustrating. I tried another way, just to test my networking setup. I used a USB Nic (yuck) passed through to pfSense and my second unused onboard NIC to setup another br1 and connected those together. I then setup another interface along with DHCP in pfSense. The VM successfully gets an address from DHCP and I can ping the router (interface on pfSense) and the Unraid br0 address but I can't seem to get any further. I'll have to look into virsh commands for networking, etc as I haven't really mucked around with that yet. EDIT: omfg, it was NAT. What an idiot.