cosmicrelish

Sorry I can't be of any help. With everything I tried I ended up breaking the whole thing and just deleted all the app ata and the containers and started rom scratch

It's been a long time since I updated nextcloud and I can see that things have changed. Inside the nextcloud server page where I would go to update it tells me to use the command line to upgrade at this point. I have followed the instructions on how to do that but it is not updating. How do I bring myself from version Nextcloud Hub 7 (28.0.2) to the current version?

I just updated the docker image and after it starts I can't get into the server page. I looked at the logs and it is now telling me there was an error verifying my license. This has never been an issue before. I checked and my license file is in the data/config folder where it's always been.

Unfortunately they wouldn't tell me how it calculates the HWID. I will try the randomize Mac setting. They gave me a little app that when you run it then it will show the ID's of several things. Tech support said it looked like my BIOS was changing. I tried using that same app on a bare metal machine and there were no changes in any of the ID's each time I started the app. So I know it has something to do with my VM setup.

I'm running a VM with win10 solely for flight simming and one app I use has authorization tied to the hardware ID. The ID seems to change every time I run the app and I am wondering if it is because I am running it inside a virtual machine. Is there a way to lock a HWID in place so that it would only change if a major change is made to the computer itself?

Here is the conf file for Mealie that is in the swag proxy-conf folder. My subdomain is food.***.com I also have this domain listed in the SWAG container where the others are. ## Version 2024/07/16 # Ensure your DNS has a CNAME set for mealie and that mealie container is named. server { listen 443 ssl; listen [::]:443 ssl; server_name food.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth (requires ldap-location.conf in the location block) #include /config/nginx/ldap-server.conf; # enable for Authelia (requires authelia-location.conf in the location block) #include /config/nginx/authelia-server.conf; # enable for Authentik (requires authentik-location.conf in the location block) #include /config/nginx/authentik-server.conf; location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable for ldap auth (requires ldap-server.conf in the server block) #include /config/nginx/ldap-location.conf; # enable for Authelia (requires authelia-server.conf in the server block) #include /config/nginx/authelia-location.conf; # enable for Authentik (requires authentik-server.conf in the server block) #include /config/nginx/authentik-location.conf; include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app mealie; set $upstream_port 9000; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } }

I have several subdomains all pointing at my server and going through SWAG just fine, their conf files adjusted for the correct domain name and I am able to access them anywhere. Mealie however just wont work. I get a 502 bad gateway error. So I know it's getting to the server but stopping at swag. I have looked repeatedly at the conf file but it is exactly like the others that do work (mealie.*) and yet it wont point at the docker container.

I recently have been having an issue where I notice that docker containers aren't able to be accessed, like plex or nextcloud, etc. I'll open the unraid GUI and go to the docker tab and it just hangs on loading. If I reboot the server then things work fine for a while but then I'll notice everything has gone offline again. I have been chasing the problem for a while and I can't find any answers on google. I have run a memtest at boot and everything returned fine. I have checked the parity and that seems fine. All cables are secure and all drives appear healthy. I read somewhere about a corruption on the cache pool and I would format it except the app data folder on there I am not sure if it'll rebuild or what will happen. Docker was never this slow so I feel there's corruption somewhere. tower-diagnostics-20250128-2052.zip

UPDATE OK so since this all happened the server sounded very quiet. The fans were not as loud as normal. Today I bought a new PSU thinking maybe there was an issue with not enough power getting to the server for everything. While I am awaiting the delivery I tried launching the server again to see what it takes to shut it down. It wasn't liking a parity check or running updates or too many dockers. I decided to take a look at the fans and see why it was so quiet. I come to find out the CPU fan was not running. I gave it a little flick and now the server appears to be back to normal... almost. My 4 port usb card seems to have lost one of the ports. I do have a new card coming tomorrow as well that is a bit updated and I may still upgrade the PSU, just in case. No idea why the fan was stuck but I may end up replacing it as well. So in theory, the cpu got too hot and not enough cooling happening and it powered down to protect itself.

I was finally able to get some time to try to troubleshoot things. Also to get the server to stay powered up. I was able to get a diagnostic file which I will post here. What I have found is that I can get the array started and the server stays up as long as I dont turn on the docker containers. I am going to try to run a few containers today and see what happens. I was able to update a few containers but when I got to Krusader and it was extracting the last packet I received a docker utilization error, about %74, and the system powered off. When the server came back online it started a parity check which then powered it back off. I have found a few articles stating a possible back psu that maybe works until it gets overloaded. Could the psu have broken when powered off during the outage? I have noticed a few times after shutdown that if I attempt to power on right away it'll simply stop. power on, stop, wait a minute and then power on and it's ok, until it seems that I am pulling more power due to increased usage of the machine. I am thinking I'll order a new psu today and at least attempt that. Another oddity was that I have a 4 port usb extension card that one port no longer shows up in the vm section down at the bottom. I had something plugged into that port that also had an auxiliary power supply for a game controller to give the unit more power. This second power supply was not plugged into the UPS. Could that have damaged the usb port when the power returned? Thank you! tower-diagnostics-20250109-0859.zip

Oh this is a good idea. I was able to get a diagnostic that I'll post in a bit. But I will try the trial. I do have a back up I recently made when I upgraded to 6.12.

I will do so if I can get it to boot up long enough

I'm having the strangest problem. Yesterday there was a power outage and I wasn't able to shut down properly. When the power returned, unraid started acting weird. First my USB pci card is only showing 3 of 4 ports in the vm management pages. Secondly when I start my primary vm, win10, it is showing most cpu cores at 100% and the vm acts very sluggish. I shut down the vm within windows and the whole server then shuts down. Third, all shares that are mapped are unable to connect yet if I attempt to access those shares using another computer they do in fact connect. I feel something got corrupted and I don't know what to do.

Tha KS. I did and it took me to a Linux website which didn't look very support based.

Everything worked fine last night working remotely and accessing my server through reverse proxy domains. This morning I get errors showing the pages now won't load. Usually I just restart swag and things go back to normal. Today they did not so I took a look at the log and I get: Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet. Some challenges have failed. ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container I'm not sure what happened or how to fix it. I have rebooted swag and the server and still getting the same thing. Thanks for any help!