Tenno23

Figured out my problem. Somehow the psu cables got pinched somewhere when I went into the system recently to check a fan positioning. Panels off and no more issues.

Ah well nothing else connected to it has lost power and I actually just had a crash while I was in the room looking at the ups. The other hardware running on it all have more than a month of uptime and no issues. I'll probably pull the server and check the psu now. Last logs were these entries: Jun 23 09:00:47 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Jun 23 09:29:04 Tower kernel: docker0: port 6(veth5c21fcc) entered disabled state Jun 23 09:29:04 Tower kernel: veth421c45c: renamed from eth0 Jun 23 09:29:05 Tower kernel: docker0: port 6(veth5c21fcc) entered disabled state Jun 23 09:29:05 Tower kernel: veth5c21fcc (unregistering): left allmulticast mode Jun 23 09:29:05 Tower kernel: veth5c21fcc (unregistering): left promiscuous mode Jun 23 09:29:05 Tower kernel: docker0: port 6(veth5c21fcc) entered disabled state Jun 23 09:29:05 Tower kernel: docker0: port 6(veth49d4bd4) entered blocking state Jun 23 09:29:05 Tower kernel: docker0: port 6(veth49d4bd4) entered disabled state Jun 23 09:29:05 Tower kernel: veth49d4bd4: entered allmulticast mode Jun 23 09:29:05 Tower kernel: veth49d4bd4: entered promiscuous mode Jun 23 09:29:06 Tower kernel: eth0: renamed from veth8ad5358 Jun 23 09:29:06 Tower kernel: docker0: port 6(veth49d4bd4) entered blocking state Jun 23 09:29:06 Tower kernel: docker0: port 6(veth49d4bd4) entered forwarding state Jun 23 09:29:24 Tower kernel: docker0: port 5(veth9231b47) entered disabled state Jun 23 09:29:24 Tower kernel: vethcc6bd9a: renamed from eth0 Jun 23 09:29:24 Tower kernel: docker0: port 5(veth9231b47) entered disabled state Jun 23 09:29:24 Tower kernel: veth9231b47 (unregistering): left allmulticast mode Jun 23 09:29:24 Tower kernel: veth9231b47 (unregistering): left promiscuous mode Jun 23 09:29:24 Tower kernel: docker0: port 5(veth9231b47) entered disabled state Jun 23 09:29:25 Tower kernel: docker0: port 5(veth5052c84) entered blocking state Jun 23 09:29:25 Tower kernel: docker0: port 5(veth5052c84) entered disabled state Jun 23 09:29:25 Tower kernel: veth5052c84: entered allmulticast mode Jun 23 09:29:25 Tower kernel: veth5052c84: entered promiscuous mode Jun 23 09:29:26 Tower kernel: eth0: renamed from vethd24050e Jun 23 09:29:26 Tower kernel: docker0: port 5(veth5052c84) entered blocking state Jun 23 09:29:26 Tower kernel: docker0: port 5(veth5052c84) entered forwarding state Jun 23 09:30:24 Tower kernel: docker0: port 1(veth66d38cf) entered disabled state Jun 23 09:30:24 Tower kernel: veth9bbbf06: renamed from eth0 Jun 23 09:30:24 Tower kernel: docker0: port 1(veth66d38cf) entered disabled state Jun 23 09:30:24 Tower kernel: veth66d38cf (unregistering): left allmulticast mode Jun 23 09:30:24 Tower kernel: veth66d38cf (unregistering): left promiscuous mode Jun 23 09:30:24 Tower kernel: docker0: port 1(veth66d38cf) entered disabled state Jun 23 09:30:25 Tower kernel: docker0: port 1(veth29e0f67) entered blocking state Jun 23 09:30:25 Tower kernel: docker0: port 1(veth29e0f67) entered disabled state Jun 23 09:30:25 Tower kernel: veth29e0f67: entered allmulticast mode Jun 23 09:30:25 Tower kernel: veth29e0f67: entered promiscuous mode Jun 23 09:30:26 Tower kernel: eth0: renamed from vethafbfa67 Jun 23 09:30:26 Tower kernel: docker0: port 1(veth29e0f67) entered blocking state Jun 23 09:30:26 Tower kernel: docker0: port 1(veth29e0f67) entered forwarding state

UPS is actually pretty new (bought it late last year to protect server and all my network cabinet stuff) still reports 100% battery health and fully charged.

That's how all the previous logs have looked. Nothing common among them. We were gone all day yesterday and the server was mostly idle. The only other change I made recently is turning off netbios in smb since I saw something about it causing issues with ftp. I've reenabled netbios in smb on the latest reboot. I've also attempted stopping docker applications one at a time to see if the crash stops. Memtest has been fine but if it crashes again after changing the netbios setting back I'll put in a backup psu and see what happens.

Why wouldn't the logs include booting information? It booted at 2100 and crashed after 2300 and then booted again at 0000 the syslog-previous is the previous log from before a new bootup everything from bootup at 2100 until it no longer was recording information due to a crash at 2300.

The syslog-previous is before the crash. This is how all my logs look after it happens (it always happens when I'm not using the server it has never happened when content is being watched from plex or anything) From syslog-previous it crashed somewhere from 23:07 and I brought it back online at 00:29 the following day from syslog. Why are you saying syslog-previous is from before the reboot? Every syslog-previous I get ends around the time the server crashes and the times logged are all before the crash.

added to OP

No I have current syslog's but no diagnostic zips. I have syslog and syslog-previous which seems to be the log up till a crash. It hasn't made any diagnostic zips since 2022.

I have syslog's mirrored. Do I post the previous one? Hopefully it isn't the power supply but I did consider that. Since it happened directly after upgrading to 7 its hard not to assume something with that upgrade is what caused it.

Server has been running fine for years until about a week or so ago when I noticed the server array was offline after an "unclean shutdown" mind you I don't ever shutdown my server. The only change software wise is I finally updated to 7 after putting it off for a long time and I uninstalled proftp when moving to 7. I have no diagnostic logs being saved (last diagnostic zip is from 2022) but I did enable syslogging. The other issue I've noticed since upgrading to 7 is connecting via the tower.local url is much slower for some reason than just connecting with the url. It takes a long time to connect ever since going to 7 which seems weird. Is there anything in syslog I need to filter out for privacy if I post the logs online? Thank you. EDIT I also ran a full memtest and had zero errors after all passes. My server is also on a sinewave ups that has reported no outages syslog syslog-previous

I mean I launched and shutdown the server every time I edited the config and had no issues until walking away for a few hours and then coming back and before editing it at all I did start and stop it completely. Just now finished playing and shutdown the server and relaunched it to check and the settings stuck but I can't see any reason they would have reset. Are you saying when someone new joins and quits it's going to overwrite the file again? That would be stupid af.

Nevermind on having fixed it because for some reason my config file completely reset and now I have to edit it again. Why would the config file reset to default?

*EDIT* I fixed it by changing the password for the default user to the same as the server password. I keep getting invalid password when I try to connect to my server (I set the password in the config "password": "XXX",) and the log shows [online] Session accepted with peer ( id xxx ). [online] Added Peer #0. [online] Client 'xxx' authenticated by steam [session] Unable to find machine for peer 0. [session] Unable to find machine for peer 0. [session] Could not store acknowledge of packet id: 23. [online] Disconnecting peer #0 (SteamSessionConnectionMsg). [online] Removed Peer #0. I tried with Docker as the password too and it still didn't work.

*EDIT4* I got it working. Only problem I'm having is with cloudflare saying my record A IP is exposed. Is there a way around this? Without setting cname to dns only nextclould wont work. *EDIT3* I changed the scheme to https in nginx and now I'm able to access nextcloud locally. Outside of my network though I get too many redirect error in safari and firefox. I have not been able to figure it out. When nextcloud didn't have a host name it was accessible but once I did the edits to give it a hostname I was unable to connect to it directly or by clicking it in nginx. I really have no idea where the problem is. I don't know if it's related but I don't know what to put in the cloudflare cname content field. Nothing I watched/read ever addressed that and just showed them putting in information related to the video uploader. Here is what I can tell you. my proxy host is set to nextcloud.mysite.domain, destination is internalIP:444. nextcloud edited from "internalip" to nextcloud.mysite.domain. When I click webui in unraid the url address starts with the localip and then quickly flips to nextcloud.mysite.domain. Cloudflare has the cname dns added as name nextcloud and content mysite.dns <-- this is what I personally have no idea about. I tried setting it to mysite.domain but then it says it exposes the ip or something. I can turn on the proxy setting on cloudflare and that warning goes away but the settings in your guide show it set as dns only. Even set that way though I still get server not found. No matter what I do it just says server not found. I have the ports fowarded in my udmpro. I don't know if it matters but I do run a pihole. I haven't seen anything being blocked in it though. *EDIT* I didn't change anything and now it says "this page isn't redirecting properly". *EDIT2* Taking the proxy off on cloudflare so that it says my cname exposes ip of A has made it say 400 error plain http was sent to https port.

I fixed the webui issue but now my issue is that it seems to be completely broken. It claims all files are missing and rechecking doesn't work it tires to download them again instead and then they error. New downloads instantly mark as "errored". *EDIT* I fixed the issues myself.