Mlatx

Yup. It happened right after. Had the board for at least 2 years and first time this happened.

I wonder why it would just show up. I’ve hade this board for years. I may try and update the bios and see what that does. Then perhaps go to the latest beta. Yeah I need IOMMU. Thanks.

Hello, I'm attaching the diagnostics here. One of my 2 parity drives has read errors as does 1 of my 3 array drives. Funny, they are just shy of their warranty. Are these read errors a bad disk or something file system related? server-diagnostics-20201002-0739.zip

Hi All, I'm on Unraid 6.8. I'm seeing some weird behavior with macos catalina. If I reboot unraid, the shares don't connect with my mac unless I reboot it. Now, I'm having a situation where the shares are visible, but I cannot see the contents. I get the spinning loading symbol. Did something change in 6.8 that I need to address?

This thread has the fix for pfsense vm booting, So I guess this now becomes a pfsense issue on reaching dockers.

I took that line out. Here are the Unraid 6.8 diagnostics. pfsense is still not booting up in 6.8. I've shared a screenshot on where it is stuck. Regarding using my backup pfsense box, it seems to be the culprit to accessing docker containers through letsencrypt. I don't know why as the configs are the same. I guess I'll post in the netgate forum. diagnostics.zip

That is going to be painful to go back to 6.8. I can try to do it but won't be able to do it until later.

Here they are. diagnostics.zip

Do I post the zip file?

Not that I know of. How would I find out?

Hi All, I upgraded to version 6.8 this morning. I was running pfsense in a vm as my primary router and decided to switch configuration where I would run my backup separate box as my router and the vm as my backup. I was unable to hit any of my dockers that were using letsencrypt as the reverse proxy. I have my own domains setup. So I thought maybe it was the switch to my physical pfsense router. I tried to switch back to the vm, but it would not boot up and kept hanging before the startup screen (there is another post on this). The main issue for me was not being able to access my dockers. So I reverted back to 6.7.2. The pfsense VM starts and works accordingly. Now running my primary or my backup pfsense I am able to hit my dockers by their URL. What is causing this issue in version 6.8?

The only other thing worth trying would be to delete the container and reinstall it. All your app settings will be there. Unless someone else can chime in on another solution.

Any errors I had with the install occurred within the terminal window. Usually a google search copying the error found a solution. If you are having trouble starting the nextcloud container or getting the error upon restart, make sure you have the https port set to 444 otherwise it won't start with 443 (unraid uses that). That's about as much as I can help on this one.

The new installation sees everything as it was. I wish I could have started from scratch but didn’t want to deal with a potentially bigger headace. Version 13 sounds about right. You can’t jump from 13 to the current 16. It’s too many versions out (at least that was the error I got) so have to go to 14 first. It’s really not that difficult to follow those steps. It would have been a lot easier had I not had the password error.

I just resolved this issue today and spent a few hours. I'm going to try and help you not spend that much time. You'll need to upgrade Nextcloud itself (not done via the docker update in unraid). There is a link on the first page that takes you to the instruction on how to do this. After trial and error, this is what worked for me. I used this modified set of instructions to upgrade to version 14. Hopefully that works for you. All other version I tried (12, 13, 15, and 16 failed). Here was the initial process. ##Open terminal from unraid gui header (top right corner) docker exec -it nextcloud bash ##Turn on maintenance mode sudo -u abc php7 /config/www/nextcloud/occ maintenance:mode --on ##Backup current nextcloud install mv /config/www/nextcloud /config/www/nextcloud-backup ##Grab newest nextcloud release and unpack it (I had to do version 14 as I couldn’t go further without errors. You can update from nextcloud gui to other versions once this is completed) wget https://download.nextcloud.com/server/releases/latest-14.tar.bz2 tar -xvf latest-14.tar.bz2 -C /config/www ##Copy across old config.php from backup cp /config/www/nextcloud-backup/config/config.php /config/www/nextcloud/config/config.php ##Now Restart docker container exit docker restart nextcloud ##Open terminal (should already be open just wait for the docker to restart) docker exec -it nextcloud bash ##Perform upgrade sudo -u abc php7 /config/www/nextcloud/occ upgrade ##Turn off maintenance mode sudo -u abc php7 /config/www/nextcloud/occ maintenance:mode --off after you confirm all is working, do this ##remove backup folder rm -rf /config/www/nextcloud-backup ##Remove Nextcloud tar file rm latest-14.tar.bz2 I had an issue with the first installation completing saying the password was invalid. I found this https://github.com/nextcloud/server/issues/12750. So I followed the link on that page to the php file (well it's not a file but code) and copied all of the text into TextMate on my Mac (Notepad ++ on Windows). I saved the file in the name listed. I copied it to a director on one of my shares. Then you'll need to go into Krusader to copy this file into the directory listed on that website if you can't do it from your computer. I couldn't from my mac as the directory was inaccessible. It's a pain in the ass I know so hopefully you don't have this issue. If you do, you'll need to go through this update process again replacing version 14 with 15. I had to because the php file I created had some violation issue. But it at least got me back into Nextcloud. Good luck.

Issue: The reverse proxy header configuration is incorrect, or you are accessing Nextcloud from a trusted proxy. If not, this is a security issue and can allow an attacker to spoof their IP address as visible to the Nextcloud. Further information can be found in the documentation. I have tried all the suggestions on page 86 Nothing has worked. I've used the letsencrypt IP address and port number (both ports 1443 and another line for 180). I still get the error. What am I missing?

Thanks. It was an unassigned device.

I received this error after having to do a hard reset (did not want to powerdown clean). What does this mean, and I would I begin to fix it?

After a bit more research, I figured out my issue. Chrome seems to resolve the /zm folder. Whereas other browsers don't. So when I type zoneminder.mydomain.com in a browser other than Chrome I get the nginx page. When I type zoneminder.mydomain.com/zm it works. Is there any way to configure zoneminders so that when I type just zoneminder.mydomain.com it goes to the root folder?

There may be an issue somewhere. The thing I don't get is that I can see the events and feeds from zm ninja app, which uses my reverse proxy. Also I can see the feeds through Chrome but not the events. Every other browser shows that error.

I have a couple issues going on right now with the latest version. First, I setup a reverse proxy using letsencrypt. I am able to login through Chrome and the zmninja ios app. I cannot login through Firefox, Safari, or IE. I setup my proxy.conf file according to my last post https://forums.unraid.net/?app=core&module=system&controller=content&do=find&content_class=forums_Topic&content_id=56632&content_commentid=724628. I've attached the screenshot I get from Safari and IE, and Firefox say the connection was reset. The other strange thing going on is I am was able to see my events in Chrome, and now I see a white screen with no controls. This is a video I was able to see 2 days ago. When I try to download the video using the video link it says not video found. Then I click it again, and it shows my download options. However, when I try to access the video there is no content. Does anyone know how to fix this?

Thanks. I did some more research and got a working zoneminder.subdomain.conf file (I am using my own subdomain). I have the following: server { listen 443 ssl; listen [::]:443 ssl; server_name zoneminder.*; include /config/nginx/ssl.conf; client_max_body_size 0; location /zm { include /config/nginx/proxy.conf; proxy_pass https://IPADDRESSOFYOURSERVER:8443/zm; } }

Someone has posted about setting up zoneminder through a reverse proxy but left no explanation on how. How would I do that? I have letsencrypt running for nextcloud. Another post mentions you cannot use letsencrypt because zoneminder runs on apache and not nginx.

Here you go. Thanks for the help. server-diagnostics-20190106-1343.zip

Thanks. All working now.