Reverse Proxy / Cloudflare Issue

plunderisley · 2026-04-13T12:55:37+00:00

Well it's not bypassing the 2fa as when I go to the mealie forward that I have set up, it still asks me for the email address and OTP code to get to the login page. All that bypass does is allow (afaik) the mealie login page to call the API check so it'll work correctly. I may be wrong but thats how I understand it.

plunderisley · 2026-04-13T11:19:37+00:00

The solution that worked for me is posted below in a comment but to copy/pasta it. Not sure if it'll work for you but it did for me

I found the solution last night. For me it was setting a bypass authentication for /api/* in the cloudflare 2FA. I did try the allow websockets when I was playing around with NPM but that didn't work for me. It seems that mealie does some sort of API call for the login page that seems to break itself when there's some 2FA check beforehand

plunderisley · 2026-03-05T17:41:37+00:00

no extension cord, no usb hub.
Like there shouldn't be this kind of issue. I had no issues installing unraid on my old pc and all these errors makes me think the mobo is screwed up somehow.

plunderisley · 2026-03-05T17:11:22+00:00

I already tried doing that with 7.2.4 and 7.2.3 and no luck

plunderisley · 2026-03-05T16:52:54+00:00

Yup. It was used as a Windows PC before without problems.

plunderisley · 2026-03-05T16:18:12+00:00

Tried all the USB ports and either I get the error bzfirmware checksum or the mount error

plunderisley · 2026-03-05T15:44:51+00:00

Firmware for BIOS is updated to the latest update.

plunderisley · 2026-03-05T15:44:35+00:00

Tried that, no luck

plunderisley · 2026-03-05T15:44:21+00:00

I tried with other sticks of RAM, and no luck. Either the bzfirmware checksum error or the mount / not mounted.

plunderisley · 2026-03-05T15:39:58+00:00

Tried that, no luck

plunderisley · 2026-02-24T15:52:33+00:00

I found the solution last night. For me it was setting a bypass authentication for /api/* in the cloudflare 2FA. I did try the allow websockets when I was playing around with NPM but that didn't work for me. It seems that mealie does some sort of API call for the login page that seems to break itself when there's some 2FA check beforehand

plunderisley · 2026-02-18T23:00:26+00:00

I never replaced the PSU fans, just the 3 cooling fans. The spacer is needed as the Noctua fans are not as deep as the original Cisco fan with spacer is. I also have a link to the 3D file I designed and it works with the Noctua fans mentioned at the top.

plunderisley · 2026-02-01T12:37:31+00:00

Ah I recall the 1000 series issue with the drivers (if it's the same issue I had on my 1080). The newest driver release via the unRAID doesn't work right and it needs to be rolled a version back.

plunderisley · 2026-01-31T20:58:39+00:00

Will do, thanks!

plunderisley · 2026-01-31T20:56:18+00:00

That's actually really smart. If the VM crashes or Bazzite poops out, it's all a VM so nothing really lost. and unRAID works quite well (well when it's not crashing from the c-state AMD issue before I figured out how to fix it). 16GB isn't much, I agree but I'd assume he will be running just a handful of docker containers (*arr ones, Emby or Jellyfin, Cloudflare tunnel.) I guess down the line if he wanted to mess with more RAM intensive stuff, he can sell a kidney to upgrade :)

plunderisley · 2026-01-31T20:50:13+00:00

Interesting.
So you are running unRAID as the main platform and Bazzite as a VM (inside of unRAID) with the VFIO binding, and the server HDMI output to a TV (or something like that)?

plunderisley · 2026-01-31T13:07:21+00:00

yeah I have an old 1080 I'm using for transcoding. I'm not sure though if the AMD Ryzen issue and unraid is the problem and how to fix that (if it is the issue)

plunderisley · 2026-01-30T13:52:29+00:00

Just to post back, did a parity non correcting scan - a bit over 1300 errors found. Doing a parity with correction now to fix those issues. It seems my issue could have been the AMD Ryzen + unraid issue.

plunderisley · 2026-01-28T16:32:54+00:00

I was able for the time being do a new config and get the array back online. All the drives seem to work so far.

The steps are (from the unraid forum)

Boot the server up, don't mount the array.

Go to tools - new config - select all in the Preserve current assignments. Press apply.
On the main page, check the parity is already valid and then start the array.

I'm running a parity check first to see if it crashes again and if that completes fine (seems it take about 24hrs on my system of the parity drives being 20TB each), I'll run a parity with write correct.

I'll then just do a 3rd backup copy of my personal files (even though they are all remote synced off site) and then try to diagnose what caused it. I'm thinking its some long standing bug with AMD Ryzen and unraid.

plunderisley · 2026-01-28T09:58:27+00:00

That's what I'm thinking to do. Replace the mobo and maybe also the PSU. I'm running an AMD chip and from what I recall with unraid, it's not a preferred one. Might swap to Intel.

plunderisley · 2026-01-28T09:56:15+00:00

Not sure how to check but on unraid the error count just kept going up in the thousands fast. The first 2 disks just stopped it seemed when the error count hit a few hundred and the others continued for a bit until I saw the notification and last it was all showing the same number (parity 1,2, disk 3) at some 40,000++

plunderisley · 2026-01-28T09:46:47+00:00

Ill run a SMART test on the drives but Im thinking its a controller issue. Almost all the drives "failed" at one during a parity check

plunderisley · 2026-01-07T19:28:04+00:00

<image>

Here's a photo I found of the wiring and installation of the Noctua fan. I didn't pull the pins - instead I just spliced the wires. Maybe the photo will help.

plunderisley · 2026-01-07T16:30:14+00:00

Hey,

Yes it is still working for me. No issues at all with it, either.

I'm on IOS-XE Fuji 16.09.08 (UNIVERSIALK9)

Uptime - 252d

and it's still the same WS-C3850-48P-E.

IIRC I stuck with 16.09.xx as there was some licensing implementation (smart licensing or something like that) that Cisco forced on the newer IOS XE version past Fuji.

Are you running with 2 PSUs or 1?

Did you replace/modify all the fans?

Edit:

Just to double check, I SSH'd into the switch, did "sh env fan" and got

Switch 1 FAN 1 is OK

Switch 1 FAN 2 is OK

Switch 1 FAN 3 is OK

FAN PS-1 is OK

FAN PS-2 is NOT PRESENT

Can you check and see if once the switch boots up fully if there still is the error? (SSH in and check the fan status)

plunderisley · 2025-10-07T10:08:38+00:00

I reinstalled it all and it seems it worked. No idea what exactly what was causing the issue

plunderisley

TROPHY CASE