tshorts

From the Guide: https://docs.unraid.net/unraid-os/manual/changing-the-flash-device/ How do I know which drive is which? 3 have the same name, and the other 2 the same name. The have different sd-lettering, but not sure if they will change when I change USB, or what will information will be removed and what will stay. Or do the quote above not matter if I replace from backup zip file?

I suspect it's problems with the USB. I get some SQUASHFS errors in syslog, which searching seems to be USB. chkdsk shows no errors but I don't trust that, it's way to fast.

Thank you! Then I'll go forward with the project. Much obliged.

I use Nginx Proxy Manager to get web addresses to correct docker in the server. From internet videos.mycooldomain.com points to 10.1.1.1:555 that i run jellyfin on, ftp.mycooldomain.com points to 10.1.1.1:21 which i run my ftp docker on. Can I also use it for external server? I have a raspberry pi I want to run another server on, let's say IRC-server and it has 10.1.1.200. Can I do the same, like irc.mycooldomain.com and point the unraid nginx to 10.1.1.200:6667? So traffic goes from internet to unraid, nginx forward it to the other physical server?

No, I'm not. Running a quite (too) basic "unnamed" router ISP gave me. Which I haven't changed settings on or updated any firmware since issue started.

Had reverse proxy through cloudflare for over a year without any issues. Last week I've had 3 instances of problem with it, without any changes in cloudflare, or locally on the apps affected (have done some other stuff on the server though, installed dockers and such for LAN use only). 1.domain.com -> jellyfin (web-based) 2.domain.com -> webserver A few days ago I couldn't reach jellyfin from the outside, it worked fine locally. A reboot of the server fixed it (reboot of jellyfin docker, cloudflare docker, or nginx docker). Today I can't reach jellyfin, nor the webserver. I booted the server 2 hours ago, after 8 hours of being turned off. (All relevant dockers are set to autostart) I get cloudflare error: Browser Working, Cloudflare Working, 1.domain.com Host Error. Where can I begin to look for core fault reason? What logs etc. What should I look for?

I see my public (none-vpn) IP on the IRC server. But found the built in VPN Wireguard thing, so I'll look into that. Understand that's where VPN for outbound traffic is supposed to go.

Is it possible to use the VPN only for outgoing traffic? Like not having the web interface VPN:ed, but the other traffic. Eg, Torrent-program. No VPN for the interface, but VPN for all torrent traffic. Or TheLounge. Let's use my instance of irc-client TheLounge. Locally I use port 9000 for the WebUI, and a subdomain which is reversed-proxied to 9000 when used externally. So I don't want to VPN that part. 9000 is the only port mentioned in the docker settings and under Port Mappings column. TheLounge connects to an external IRC-server on port 6697, that server see my personal public IP. THIS is the part I'd like to VPN. Is that possible with similair method? Or is it a whole different thing?

Thank you, I'll use that as a last (well, second) resort.

Thanks, tried that now, my common passwords didn't work there either. So I guess I've outsmarted myself. If I remember correctly I generated a non-standard password to be extra safe with the admin account - and saved it encrypted somewhere. What I don't remember though, is where. I'll keep looking, I have about 18h to find it hehe.

Anyone know how I reset the password for the admin account? I'm loggin in, but need to know the old password to set new one. I haven't connected mail to it.

How do I add other than http or https? I'd like to add irc://

I really hoped it could be bad cable Disk -> Processor and not the other way around but I verified a torrent that ended up 99.9%, and reverified it and it failed again, so it's written error as you say. Cables, then memtest it is. I really hope it's one of those. But it's probably a bad motherboard if I know my luck with motherboards correctly. Thanks for the help!

Thanks. The cables yes, good idea. I'll replace out the SATA cables, if that doesn't help I'll remove one RAM at a time and see if it stops. Hope for the best. Weird that the files work fine, and the errors come totally random, can seed for a year and suddenly 99.9%, and same torrent can happen multiple times, wonder if transmission perhaps only try receiving a segment from HDD once, the requested segment gets corrupted in a bad cable and decides it's corrupted. While the Parity check will do multiple requests if a segment is seen as corrupted. I'll try Verifying a bunch of none-errored torrents.

You mean "Verify"? I did in the beginning, but not anymore, takes to long time. I did one now that was on "error" and not on stopped and it gets an "corrupted segment". Unraids Parity-Check have never found any errors though. Last one done a week ago. Thanks for the response. Narrowed it down a bit. I'm lost at what the cause can be though.. I don't use cache for torrents so can't be that disk. Do it go through RAM when it looks for a file, and a RAM might be bad maybe?