kaiguy

Thanks, Sycotix, for setting up this template and providing your writeup. This was super helpful to get me up and running behind the LSIO Letsencrypt container. Just FYI, the section where you provide the maridadb command to add a user requires a semi colon at the end. It should be: CREATE USER 'authelia' IDENTIFIED by 'YOURPASSWORD'; After a bunch of issues likely related to my own misconfig, I took the configuration.yml down to its basics then added in the items I knew I'd need from the Authelia docs. That seemed to help get me going. DUO integration is working great, with totp as a backup. Since LSIO doesn't have much instruction on how to configure, it did take a while to figure out I needed to add this under the server block for its out-of-the-box Authelia support to work: server: path: authelia If others are going with the LSIO LE container, there's no need to utilize Authelia as its own subdomain reverse proxy.

I'm not seeing Authelia in CA... either by name or browsing under Security... was it pulled? Edit: I think it may be blacklisted in CA as seen here.

I have this motherboard and cpu combo, but was severely limited by case clearance. So I purchased a lower-profile Noctua that does an adequate job but still gets pretty darn hot at full load. If I could have chosen any cooler, I would have gone with the Noctua NH-D15.

2 weeks in for me on the L2.21A BIOS. No high temp warning yet (though I would bet money given everyone else getting the warning within the last few days I'm due for one). I'll be sure to comment here and let William know if/when it happens. Server has been fairly idle and its been pretty cool here in gneral lately, but that's the norm anyway so I doubt that's a factor.

I tried to make a switch from the non-GUI version to the GUI (pointed the config to the old appdata directory but started with a fresh container). It's running and working, but I can't access the GUI at all. Any suggestions? I manually added the port but nada.

Bummer, @Hoopster. I haven't ran into that yet, though I am a few days behind you since the BIOS update. I'm on the 1.80 BMC... Is there a 2.30 BMC, or are you thinking of the newer BIOS on their website that doesn't incorporate the QSV item?

No clue about the iOS app, but to install the preview, just change the repository in your container setting to "linuxserver/ombi:v4-preview" It's been working great for a while now.

Too soon to tell, but so far so good. I didn't get my first mobo temp warning for about 2 or 3 weeks after deployment.

Updated the BIOS to 2.21A this morning, then the BMC firmware to 1.80. BIOS did indeed revert the dual monitor setting, as well as my manual SmartFan settings. After BMC firmware was flashed, I had to go back into the hardware monitor in the BIOS to for the fans to kick back in. Rebooted back into unRAID, re-enabled the modprobe setting, and QS in Plex worked as expected. No issues as of yet to report.

I would volunteer as tribute to test this, but I'm currently running a preclear. Sorry guys.

Not a support need, per se, but curious if anyone has tried bypassing http auth on local network(s). I tried modifying the proxy-confs to accomplish this, but I haven't been able to get this to work. Not sure if I'm doing something wrong, or if it just doesn't work with reverse proxy for some reason. location / { satisfy any; # bypass http auth for local IPs allow 192.168.0.0/24; allow 172.18.0.0/16; deny all; # enable the next two lines for http auth auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; ...

Thanks, @Hoopster, for taking the plunge and finding out about the iGPU. I'm going to hold off on updating. Also appreciate your letting us know that all the settings reverted. I have static a DHCP address set on my router for the IPMI MAC, so luckily it would have still worked for me with the same IP. I'm going to hold off for the next revision, however.

William was nice enough to email me as well asking me to update and keep him informed. I'm really impressed with his support! Edit: I wonder what order we should update (BMC vs. BIOS). Did you get any indication that the additional features from the beta BIOS made its way into this one? I'd hate to lose QS.

While I'm sure one of you would have posted about it if you did, I figured I'd check in to see if anyone has heard anything from ASRock... If the two previous times it happened to me is any indication (about 20 days apart), I'm due for another high temp warning here in a couple of days...

Glad to hear it. Does it really matter, though, since the ASRock IPMI shows that high temp as well?

Thanks for making those reports. William didn't indicate any concern when I contacted him. Hopefully we'll get some action now!

Both times I've gotten the temp warning my server was idle, so I'm pretty sure load has nothing to do with it.

Considering just about all of us with this board here have experienced this, I'm surprised ASRock wasn't aware of this already.

Yeah, I figured the BIOS wasn't going to fix it since you've been on it since day one. If you have some time, can you maybe let ASRock know? He wanted me to update him if I get it again, and perhaps having more users reporting this MB temp issue would be helpful to get a solution...

@Hoopster That's a much more informative response than I got from Noctua when I asked about the CPU and cooler. I have seen temps in the 80s, but it never got above 85. That's with a thermal pad and not paste.

I flashed via html5 IPMI interface (firmware update, as Hoopster pointed out). It was pretty simple, though there were some times I thought it hung.

Update on the high MB temp. ASRock suggested I update to the latest BMC firmware. I was actually surprised I didn't already update it--for some reason I thought I was on the latest version. In any case, I'm now on P1.60. We shall see if this addresses this issue. @Hoopster and @Burizado, are you both on P1.60? If so, I doubt this is a fix.

Got another motherboard temperature warning tonight... my second. Server wasn't doing anything. I'm debating disabling the MB temp sensor in IPMI because I can't imagine that's an accurate reading. But I'm going to email ASRock tomorrow and ask about this being a known issue before I do that.

When you install a container, a user template is created under /boot/config/plugins/DockerMan/templates-user ... you can try deleting the "my-plex.xml" file before reinstalling. That could be what you're running in to?

If you read back into this topic, both Hoopster and I have experienced IPMI reporting ridiculously high mobo temps. The one time it happened to me I rebooted and it returned to normal, and I haven't encountered it since. My guess was it was a stuck sensor, but not sure. Looks like this is not uncommon with this mobo...