nug

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?

Is anyone else having issues when restarting the server/docker service? I can't get these four containers to start automatically. When I check them in Portainer it says 'Failure network ******* not found'. I have to remove them from that network and re-add them. They all start fine after that.

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.

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

That does make sense but clearly I have more to learn about dockers and how their networks work. I've set it as static, all looks ok but I can't ping it from my unraid box. All good I think I'll go back to the idea of using one of my VMs to do this. Thanks mate! Edit: So I went back and refreshed that page a few hours later and bang! It had worked. I'm not sure why it took hours to kick in but it seems like the static IP has fixed the issue - thanks mate. I'm sure that will help me with future docker issues too.

Hey guys, I'm having some trouble getting this docker to work on my unraid. I'm assuming that the best way to configure the network for this docker is a bridge? I managed to get an Apache page up (like mentioned in a previous post) but nothing when I use http://IP:8080/zm I was able to muck around using 'host' and changing the listening port within the docker's Apache2 ports.conf and managed to get Zoneminder's page working. So I know it's in there somewhere! So to me it looks like the ports aren't being passed from the unraid network into the docker's. I've tried a few different ports in the UI field with no luck. I also noticed that when I click on edit for the webUI port that it is greyed out and is the same as what I chose for the host port. Any suggestions?