itsmepetey

That solved my issue! Thank you very much for your help.

Everything has been working fine for me for well over a year. Last week though my binhex-delugevpn UI stopped loading. I tried multiple container restarts, unraid restarts, and tried removing the container and re-adding it. No luck. Both radarr and sonarr can add/pick up completed torrents just fine. Only the UI seems to be a problem. Based on the other replies above, some additional info: - Using wireguard to VPN into server as I am currently not able to physically access server. [This was working for the last 4 months so not a new variable to the system] - Haven't changed anything on web browser recently. Not using a proxy on web browser or anything supervisord.log

I realize I was in just the standard Deluge thread and there is a VPN specific one. I will post in the correct thread and include the logs. My apologizes

Thanks for the info! Appreciate it.

I have tried a bit of skimming of this thread as well as searching - but is anyone able to answer a quick question regarding wireguard functionality. Currently I have OpenVpn setup via docker container. This works great until you need to spin down the array. Will setting up wireguard, since it is a plugin and not a docker based solution, allow me to spin up and down the array while still maintaining vpn access?

Thanks! That did the trick and it no longer was giving me errors.

I am trying to follow this guide and have run into an issue with the matrix setup. I have read through and followed the instructions to add: pidfile=/data/turnserver.pid userdb=/data/turnserver.db But I am still getting these errors when I start back up the Matrix docker 2020-06-05 16:05:08,756 - synapse.app.homeserver - 369 - INFO - None - Setting up server 2020-06-05 16:05:08,756 - synapse.server - 272 - INFO - None - Setting up. 2020-06-05 16:05:08,757 - twisted - 192 - ERROR - - Traceback (most recent call last): 2020-06-05 16:05:08,757 - twisted - 192 - ERROR - - File "/usr/lib/python3.7/runpy.py", line 193, in _run_module_as_main 2020-06-05 16:05:08,757 - twisted - 192 - ERROR - - "__main__", mod_spec) 2020-06-05 16:05:08,757 - twisted - 192 - ERROR - - File "/usr/lib/python3.7/runpy.py", line 85, in _run_code 2020-06-05 16:05:08,757 - twisted - 192 - ERROR - - exec(code, run_globals) 2020-06-05 16:05:08,758 - twisted - 192 - ERROR - - File "/usr/local/lib/python3.7/dist-packages/synapse/app/homeserver.py", line 682, in <module> 2020-06-05 16:05:08,758 - twisted - 192 - ERROR - - main() 2020-06-05 16:05:08,758 - twisted - 192 - ERROR - - File "/usr/local/lib/python3.7/dist-packages/synapse/app/homeserver.py", line 677, in main 2020-06-05 16:05:08,758 - twisted - 192 - ERROR - - hs = setup(sys.argv[1:]) 2020-06-05 16:05:08,758 - twisted - 192 - ERROR - - File "/usr/local/lib/python3.7/dist-packages/synapse/app/homeserver.py", line 372, in setup 2020-06-05 16:05:08,759 - twisted - 192 - ERROR - - hs.setup() 2020-06-05 16:05:08,759 - twisted - 192 - ERROR - - File "/usr/local/lib/python3.7/dist-packages/synapse/server.py", line 274, in setup 2020-06-05 16:05:08,759 - twisted - 192 - ERROR - - self.datastores = DataStores(self.DATASTORE_CLASS, self) 2020-06-05 16:05:08,759 - twisted - 192 - ERROR - - File "/usr/local/lib/python3.7/dist-packages/synapse/storage/data_stores/__init__.py", line 49, in __init__ 2020-06-05 16:05:08,759 - twisted - 192 - ERROR - - with make_conn(database_config, engine) as db_conn: 2020-06-05 16:05:08,759 - twisted - 192 - ERROR - - File "/usr/local/lib/python3.7/dist-packages/synapse/storage/database.py", line 112, in make_conn 2020-06-05 16:05:08,760 - twisted - 192 - ERROR - - db_conn = engine.module.connect(**db_params) 2020-06-05 16:05:08,760 - twisted - 192 - ERROR - - sqlite3.OperationalError: unable to open database file Any other suggestions as to what I am missing?

I took your advice. I updated the BIOS and then ran a memtest over night. No errors showed up so I went ahead and gave the parity sync another go. That fixed it and it completed without errors. Thanks for taking a look!

Hi, this is my first time diving into setting up a server so I am hoping I am just missing something obvious. I have been trying for a week to get a parity drive set up but it keeps failing and setting itself as disabled. I have searched the forums and have tried a few things I have found but I can't seem to figure it out. Hoping someone with more experience could shed some light. Setup: 2 brand new Western Digital 8tb drives taken from Easystore externals Running unraid 6.8.3 Things I have tried: - Formatting drives - Stop array, de-select parity drive, start array, stop array, re-select parity drive. - Run full diagnostics on both drives - both pass with no errors. - Check cables/connections. One thing to note: The drives originally wouldn't spin up. After searching I found out that these drives in particular go into an error state if 3.3v is supplied via the power supply cable. I have cut and taped off that wire. They spin up fine now and I have had no issues with them going offline that I can tell. I have tried the parity check 3 times (each about 12 hours). I am kinda frustrated and exhausted. I feel like it shouldn't be this hard. I have attached the sys log but please let me know if there is any other info that would be helpful. Also, I have not put anything on the drives yet so there is no worry about data loss if that helps with suggesting something such as formatting again. I just wanted to get it setup before I use them just in case I screw it up. edinburgh-diagnostics-20200530-1731.zip