eric.ruck

I have encountered the same issue after the 7.1.3 update. How ever I have 2 servers, one upgraded fine the other produced this issue. I tried what I saw above but still had issue. A reboot would correct the issue but after about 30 min it would start happening again. Most network features just would work. I have rolled back to 7.1.2 for now and everything is fine. It has to be something specific on this server as the other is running 7.1.3 just fine. The only real difference between server is PLEX is on the server that is having issues with 7.1.3.

SOLVED: Finally found the issue. I'm accessing it via CloudFlare tunnel and with that you need to add some additional lines in the seahub_settings.py file. It's working fantastic now.

New to Unraid/Linux, I got Seafile installed and working, this issue I'm having is with the upload links it generates. If I do it without password it functions perfectly, however when I set a password, it prompts me for password but when I enter it I get FORBIDDEN(403) CSRF verification failed, aborted. I have tried multiple different passwords. I not sure where to look for an error log, and have found nothing on this issue. any help would be appreciated... TKS

All of a sudden I noticed my parity disk has been disabled. I tried to rebuild but it after about a min or so it goes into a READ CHECK then just freezes. I have tried 3 new drives all pass SMART and have been precleared but as soon as I assign it to parity it starts to rebuild and it does the same. I have replaced cables, tried different drive slots, always the same result. I have reset and created new configs, I'm not very linux/unix savy so I'm at my wits end.

Thanks, I saw that but saw another post that mentioned it. It started working after I added a 3rd Key Variable called INTERFACE and set it to bond0. However didnt work initially, I stopped the array to adjust the network settings and when I restarted the array it started working perfectly.

Having issue with OpenVPN-as WebUI not working, I get a page not found error. I suspect this is an issue with bond0, I added an Interface variable for bond0 but still have same issue. Network Type is set to Bridge. I have removed and reinstalled docker always with same result. Any help would be apprecaited.

Awesome Vid, got this all up and running quickly and on the first try. Everything working great accessing from outside with phones and tablets. HOWEVER , now when I launch the WebUI for Letsencrypt I get an error page that says "Welcome to our server - website currently being setup under this address" I have restarted the containers, tried different browsers but still cannot get into the WebUI. Any ideas or help would be greatly appreciated.

New to Unraid and Unifi Video, have been up and running fine for 9 months. Yesterday my USB crashed and have to restore from backup, Since then Unifi Vid will not work properly, it launches fine but keeps using a 172.17.0.4 (Docker0) address and wont see all my cameras which are on my LAN at 192.168.13.0/24. I have removed the docker and reinstalled but it always wants to use the (Docker0) bridge. If I set the docker network type fm bridge to host I get both IP's. Im at a loss to where the real problem is. Any guidance would be appreciated.

Im having same issue, Started on Oct 1, the day I upgraded to 6.6.1 Scheduled to run every 90 days, but since the 1st runs at 11:39 everyday. Have reset the schedule now for Yearly, and rebooted. Will see what happens tomorrow. Update: As posted above in original, as long as I do not use a WEEKLY or MONTHLY setting it runs as scheduled, if one of these is selected it runs everyday at 11:39