Ben4

I was able to renew my certs using Zerossl instead of Letsencrypt. I was waiting for an update, but I need my Nextcloud site back up. Per Swag support site How to switch from Letsencrypt to Zerossl: https://docs.linuxserver.io/general/swag/#authorization-method "SWAG currently defaults to Let's Encrypt as the cert provider so as not to break existing installs, however users can override that behavior by setting the environment variable CERTPROVIDER=zerossl to retrieve a cert from ZeroSSL instead. The only gotcha is that ZeroSSL requires the EMAIL env var to be set so the certs can be tied to a ZeroSSL account for management over their web interface." Stop swag, then edit your Swag container and add the variable CERTPROVIDER ( i have attached screenshots). Then hit apply and start your container. Open the log viewer to make sure Swag has switched to Zerossl and has successfully renewed your certs. I also restarted my Nextcloud and Collobora containers, so restart any containers that use Swag.

In regards to the Slimsas, I'm not currently using it although I did buy the cable and tested it to make sure my hard drive would be recognized. However for some reason, when I switched it to sata and hit save and reset in the BIOS, it goes into a boot loop and I have to pull the CMOS battery to be able to boot back into the BIOS. So I just left it at pcie for now I have three 16TB hard drives, won't be needing a 5th for a while. For the Native Power State I did turn that back on recently I need to update my post to reflect that. Thanks

So an update just in case anyone runs into the same problem I had with this motherboard (micro ATX version). I did end up returning the board to Amazon. I re-ordered the same board hoping I would not have the same problems, well I did end up having the same issue. I did some more troubleshooting this time only turning off and on some BIOS features one at a time. I've come to the conclusion when I changed the setting: Onboard Device--->slimsas configuration------changed pcie to sata, the pc went into boot loop. For some reason it does not like it when I made that change. Hopefully a future BIOS update can resolve that problem. Everything has been stable sor far, I've been able to reboot the machine successful. I do have issues still with the BMC and using it to power off and on my server, I run into the same issues as before, so I'm hoping an future update to the BMC will resolve that issue as well. I've only been running the new board for a couple of days, but at least it's not in a boot loop anymore. For those curios about the BIOS changes: Loaded Optimize Default - which disable VMD AI- Asus Performance Enhancemnet--->Disable Turned on pch storage configuration-----> enabled hot plug for sata 1-4 Turned off Tools-Armoury crate---->Disable

From Asus website the memory that is supported. I usually buy from their list so I don't run into any issues. https://www.asus.com/motherboards-components/motherboards/workstation/pro-ws-w680m-ace-se/helpdesk_qvl_memory?model2Name=Pro-WS-W680M-ACE-SE

If I remember correctly from the manual that came with the board, FF is a reserved code for future use. The codes are in the back of the manual.

I had to return this board as it was unstable for me. Every time I rebooted unraid, the server would not boot back up and kept power cycling off and on. Then I would have to unplugg the power cable for about 30 seconds and plug it back in to boot. Also the IPMI BMC did not work for me correctly, I can log in and launch the viewer to control the PC, but the moment I used BMC to reboot the machine, it would freeze and loose connectivity and do them same thing I mentioned before. The BIOS and the ME were updated to latest version. Asus offered to RMA the board or return it to Amazon for a refund, which I choose the latter. I say this to ask if anyone has experienced the same issue? I'm wondering if I simply got a bad board and try again with a new one or if this particular board is bad all together and should I go with a different board? Thanks for the input.

I found how to roll back and everything is working now. Rolled back to previous version binhex/arch-sabnzbd:3.6.1-1-03

I'm having the same error as you. How do you roll back to the previous version?

Hello All, Sabnzbd webgui won't open. Radarr says it can't connect to client. Here is a part of the sab logs. Seems http server not running. Any ideas how to fix? The error first occurred November 12. 2022-11-24 06:34:15,667 DEBG 'start-script' stdout output: 2022-11-24 06:34:15,666::ERROR::[_cplogging:213] [24/Nov/2022:06:34:15] ENGINE Error in 'start' listener <bound method Server.start of <cherrypy._cpserver.Server object at 0x14afe1616f50>> Traceback (most recent call last): File "/usr/lib/sabnzbd/venv/lib/python3.10/site-packages/cheroot/ssl/builtin.py", line 106, in _loopback_for_cert thread.start() File "/usr/lib/python3.10/threading.py", line 935, in start _start_new_thread(self._bootstrap, ()) RuntimeError: can't start new thread During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/sabnzbd/venv/lib/python3.10/site-packages/cherrypy/process/wspbus.py", line 230, in publish output.append(listener(*args, **kwargs)) File "/usr/lib/sabnzbd/venv/lib/python3.10/site-packages/cherrypy/_cpserver.py", line 179, in start self.httpserver, self.bind_addr = self.httpserver_from_self() File "/usr/lib/sabnzbd/venv/lib/python3.10/site-packages/cherrypy/_cpserver.py", line 170, in httpserver_from_self httpserver = _cpwsgi_server.CPWSGIServer(self) File "/usr/lib/sabnzbd/venv/lib/python3.10/site-packages/cherrypy/_cpwsgi_server.py", line 99, in __init__ self.ssl_adapter = adapter_class( File "/usr/lib/sabnzbd/venv/lib/python3.10/site-packages/cheroot/ssl/builtin.py", line 232, in __init__ _parse_cert(certificate, private_key, self.certificate_chain), File "/usr/lib/sabnzbd/venv/lib/python3.10/site-packages/cheroot/ssl/builtin.py", line 128, in _parse_cert return _loopback_for_cert(certificate, private_key, certificate_chain) File "/usr/lib/sabnzbd/venv/lib/python3.10/site-packages/cheroot/ssl/builtin.py", line 114, in _loopback_for_cert thread.join() File "/usr/lib/python3.10/threading.py", line 1091, in join raise RuntimeError("cannot join thread before it is started") RuntimeError: cannot join thread before it is started 2022-11-24 06:34:15,667 DEBG 'start-script' stdout output: 2022-11-24 06:34:15,667::ERROR::[_cplogging:213] [24/Nov/2022:06:34:15] ENGINE Shutting down due to error in start listener: Traceback (most recent call last): File "/usr/lib/sabnzbd/venv/lib/python3.10/site-packages/cherrypy/process/wspbus.py", line 268, in start self.publish('start') File "/usr/lib/sabnzbd/venv/lib/python3.10/site-packages/cherrypy/process/wspbus.py", line 248, in publish raise exc cherrypy.process.wspbus.ChannelFailures: RuntimeError("can't start new thread") RuntimeError('cannot join thread before it is started') 2022-11-24 06:34:15,668 DEBG 'start-script' stdout output: 2022-11-24 06:34:15,667::INFO::[_cplogging:213] [24/Nov/2022:06:34:15] ENGINE Bus STOPPING 2022-11-24 06:34:15,668 DEBG 'start-script' stdout output: 2022-11-24 06:34:15,668::INFO::[_cplogging:213] [24/Nov/2022:06:34:15] ENGINE HTTP Server None already shut down 2022-11-24 06:34:15,669 DEBG 'start-script' stdout output: 2022-11-24 06:34:15,668::INFO::[_cplogging:213] [24/Nov/2022:06:34:15] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('0.0.0.0', 8080)) already shut down 2022-11-24 06:34:15,669 DEBG 'start-script' stdout output: 2022-11-24 06:34:15,669::INFO::[_cplogging:213] [24/Nov/2022:06:34:15] ENGINE Bus STOPPED 2022-11-24 06:34:15,669 DEBG 'start-script' stdout output: 2022-11-24 06:34:15,669::INFO::[_cplogging:213] [24/Nov/2022:06:34:15] ENGINE Bus EXITING 2022-11-24 06:34:15,670 DEBG 'start-script' stdout output: 2022-11-24 06:34:15,669::INFO::[_cplogging:213] [24/Nov/2022:06:34:15] ENGINE Bus EXITED 2022-11-24 06:34:15,676 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22414695317952 for <Subprocess at 22414695320880 with name start-script in state RUNNING> (stdout)> 2022-11-24 06:34:15,676 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22414695317904 for <Subprocess at 22414695320880 with name start-script in state RUNNING> (stderr)> 2022-11-24 06:34:15,676 INFO exited: start-script (exit status 70; not expected) 2022-11-24 06:34:15,676 DEBG received SIGCHLD indicating a child quit

@andreidelait Thank you. Once I added the .conf to my nextcloud config file my site came up. Much appreciated. Do you mind sharing the link with the documentation of this change.

Hello All, I a couple of days ago I updated the nextcloud docker and now the site is stuck at a Welcome to Our Server screen. I've been trying to troubleshoot myself, but have not found a solution. I did not change anything so I don't know what happened. There is nothing in the logs for nextcloud or swag that gives me a clue as to what the problem is. I updated nextcloud using the update command docker exec -it nextcloud updater.phar to the latest version 24.0.5 thinking that would fix it, but still nothing. I saw there was another docker update today and I ran that, but still the same Welcome to Our server message. Anyone know how to fix this?

Due to time constraints, I decide to format and restore the data. Thank you for your help.

I stopped the array and unassigned disk1 (chose no device, don't see unassigned), but unraid won't let me start the array, the option is grayed out. ***I forgot to mention in my original post that when the server first booted up, before i did the parity check i did a new config under tools in an effort to get unraid to recognize the disk. I read that somewhere on the unraid forum, so I don't know if this made my problem worst.

I'll give this a try. Thank you.

I've uploaded the diagnostics

Before I start, I made a backup of my server. I upgraded my raid controller on my dell server from a PERC 6/i to a H700. The old controller only read up to 2TB and I have 4TB drives. The new H700 controller shows my full drive capacity. Each disk on the controller is configured as individual vdisks (total of 5) with raid 0 (only way i know to get it to be JBOD) When unraided booted up it did recognized the drives ( 5 drives total, 1 parity 4 data). So assigned all of the drives like i did on the previous controller and unraid recommend a parity check which i did (reading on the forums, i think i probably should have waited). After the parity check completed i go the message next to each drive Unmountable: unsupported partition layout. Now i'm not sure what to do next. Am i able to get the drives mounted or should I just format the disk and restore my server from a backup. I've attached the syslog.