craigr

What's crazy is PIA doesn't seem to allow any cipher to be defined due to their own errors.

Thanks for trying 🙂 2024-07-28 03:05:45,045 DEBG 'start-script' stdout output: 2024-07-28 03:05:45 Note: --cipher is not set. OpenVPN versions before 2.5 defaulted to BF-CBC as fallback when cipher negotiation failed in this case. If you need this fallback please add '--data-ciphers-fallback BF-CBC' to your configuration and/or add BF-CBC to --data-ciphers. It just kinda cracks me up that it's the same "deprecation" message "Computer says noooo... cough"

I'm running an Intel Xeon E-2288G CPU + Supermicro X11SCZ-F at the moment. I am strongly considering "upgrading" to an AMD EPYC 7642 or EPYC 7413 with Supermicro H12SSL-I. I lose integrated graphics, but I gain a huge amount of PCI lanes and CPU power. I also have higher potential power consumption. I'm looking at these two listings right now: AMD EPYC 7413+ Supermicro H12SSL-I +8x32g 3200 DDR4 REG ECC=256G combination US $1,814. https://www.ebay.com/itm/387125658055? Supermicro H12SSL-i Motherboard With AMD EPYC 7413 CPU，8x32GB 3200MHz RECC RAM US $1,679. https://www.ebay.com/itm/126573440505? AMD EPYC 7642+ Supermicro H12SSL-i +8x32g 2133P DDR4 REG ECC=256G combination US $1,470. https://www.ebay.com/itm/175430840223? I'm leaning towards the 7413 just because it's newer, but frankly the 7642 is much better value. Twice the cores, $350 less, and just a bit less efficient per core. I'm also considering staying where I am now. My server does everything I need still, but I don't think I can push it much harder and still be happy with the performance. Also, I would love more PCI lanes and a second SSD slot on board. I don't think I'd even install the full 256GB of memory as 128GB is fine right now, but I like having it on hand for future expansion. What would you do? Why? Thanks!

Also binhex, I have been meaning to ask, is your Q&A number 21 and 22 up to date? I can't get rid of the cypher error for example. 2024-07-23 23:49:40,899 DEBG 'start-script' stdout output: 2024-07-23 23:49:40 DEPRECATED OPTION: --cipher set to 'aes-256-gcm' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations. 2024-07-23 23:49:40 WARNING: file 'credentials.conf' is group or others accessible

Thank you binhex. I don't know why it never bothered me to the point of noticing before. It's fine there. If you have time to answer, has every version you have released done this? It seems to not always occur looking back through a couple years of logs.

I looked but didn't see anything wrong. Sorry.

So, looking back at old logs this has happened in the past from time to time. What causes it? 2023-09-26 07:02:23,818 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '32615' 2023-09-26 07:17:23,967 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '32615' 2023-09-26 07:32:24,107 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '32615' 2023-09-26 07:47:24,238 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '32615' 2023-09-26 08:02:24,379 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '32615' 2023-09-26 08:17:24,541 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '32615' 2023-09-26 08:32:24,704 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '32615' 2023-09-26 08:47:24,883 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '32615'

I'm thinking this might be a PIA thing for the server I am using? It's sporadic now all of my trackers shows all or most of the torrents I am seeding. Or is this how it's supposed to work, assign and bind the port every ten minutes? info] lu.privacy.network [info] za.privacy.network [info] aus-melbourne.privacy.network [info] ae.privacy.network [info] morocco.privacy.network 2024-07-23 20:16:15,234 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '25033' 2024-07-23 20:16:55,860 DEBG 'watchdog-script' stdout output: [info] Deluge incoming port 23881 and VPN incoming port 25033 different, marking for reconfigure 2024-07-23 20:16:57,479 DEBG 'watchdog-script' stdout output: Setting "listen_interface" to: '10.28.112.194' Configuration value successfully updated. 2024-07-23 20:16:57,479 DEBG 'watchdog-script' stderr output: <Deferred at 0x14f952eeaab0 current result: None> 2024-07-23 20:16:58,991 DEBG 'watchdog-script' stdout output: Setting "random_port" to: False Configuration value successfully updated. 2024-07-23 20:16:58,991 DEBG 'watchdog-script' stderr output: <Deferred at 0x150e7d8ca300 current result: None> 2024-07-23 20:17:00,527 DEBG 'watchdog-script' stdout output: Setting "listen_ports" to: (25033, 25033) Configuration value successfully updated. 2024-07-23 20:17:00,527 DEBG 'watchdog-script' stderr output: <Deferred at 0x1516ec3923c0 current result: None> 2024-07-23 20:17:02,929 DEBG 'watchdog-script' stderr output: <Deferred at 0x14693646ae40 current result: None> 2024-07-23 20:17:02,973 DEBG 'watchdog-script' stdout output: [info] No torrents with state 'Error' found 2024-07-23 20:26:15,399 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '25033' 2024-07-23 20:36:15,626 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '25033' 2024-07-23 20:46:15,819 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '25033' 2024-07-23 20:56:15,992 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '25033' 2024-07-23 21:06:16,401 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '25033' 2024-07-23 21:16:16,555 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '25033' 2024-07-23 21:26:16,706 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '25033' 2024-07-23 21:36:16,857 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '25033' 2024-07-23 21:46:17,008 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '25033' 2024-07-23 21:56:17,196 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '25033' 2024-07-23 22:06:17,394 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '25033' 2024-07-23 22:16:17,549 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '25033'

Spoke too soon. This is with zero changes: 2024-07-23 10:37:24,532 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI started 2024-07-23 10:46:59,289 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '23881' 2024-07-23 10:56:59,444 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '23881' Every ten minutes. I've got to fix this so I don't get H&R's.

Hey binhex, I woke up to deluge down. A restart fixed it, but looking at the log... "[info] Successfully assigned and bound incoming port '29732'" every ten minutes, but when I shut down (many times): 2024-07-23 10:36:34,682 INFO waiting for start-script, watchdog-script to die 2024-07-23 10:36:35,183 DEBG 'watchdog-script' stdout output: [info] Child process with pid id '781' still running, waiting... 2024-07-23 10:36:35,684 DEBG 'watchdog-script' stdout output: [info] Child process with pid id '781' still running, waiting... 2024-07-23 10:36:36,186 DEBG 'watchdog-script' stdout output: [info] Child process with pid id '781' still running, waiting... 2024-07-23 10:36:36,687 DEBG 'watchdog-script' stdout output: [info] Child process with pid id '781' still running, waiting... 2024-07-23 10:36:37,188 DEBG 'watchdog-script' stdout output: [info] Child process with pid id '781' still running, waiting... 2024-07-23 09:27:58,158 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '29732' 2024-07-23 09:37:58,306 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '29732' 2024-07-23 09:47:58,461 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '29732' 2024-07-23 09:57:58,623 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '29732' 2024-07-23 10:07:58,796 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '29732' 2024-07-23 10:17:58,965 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '29732' 2024-07-23 10:27:59,142 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '29732' 2024-07-23 10:36:28,664 INFO reaped unknown pid 56 (terminated by SIGTERM) 2024-07-23 10:36:28,664 WARN received SIGTERM indicating exit request 2024-07-23 10:36:28,664 DEBG killing watchdog-script (pid 392) with signal SIGTERM 2024-07-23 10:36:28,664 INFO waiting for start-script, watchdog-script to die 2024-07-23 10:36:28,665 DEBG 'watchdog-script' stdout output: [info] Waiting for child processes to exit... 2024-07-23 10:36:28,665 DEBG received SIGCHLD indicating a child quit 2024-07-23 10:36:29,167 DEBG 'watchdog-script' stdout output: [info] Child process with pid id '781 837' still running, waiting... 2024-07-23 10:36:29,669 DEBG 'watchdog-script' stdout output: [info] Child process with pid id '781' still running, waiting... 2024-07-23 10:36:30,170 DEBG 'watchdog-script' stdout output: [info] Child process with pid id '781' still running, waiting... 2024-07-23 10:36:30,671 DEBG 'watchdog-script' stdout output: [info] Child process with pid id '781' still running, waiting... 2024-07-23 10:36:31,173 DEBG 'watchdog-script' stdout output: [info] Child process with pid id '781' still running, waiting... 2024-07-23 10:36:31,674 DEBG 'watchdog-script' stdout output: [info] Child process with pid id '781' still running, waiting... 2024-07-23 10:36:31,674 INFO waiting for start-script, watchdog-script to die 2024-07-23 10:36:32,175 DEBG 'watchdog-script' stdout output: [info] Child process with pid id '781' still running, waiting... 2024-07-23 10:36:32,677 DEBG 'watchdog-script' stdout output: [info] Child process with pid id '781' still running, waiting... 2024-07-23 10:36:33,178 DEBG 'watchdog-script' stdout output: [info] Child process with pid id '781' still running, waiting... 2024-07-23 10:36:33,679 DEBG 'watchdog-script' stdout output: [info] Child process with pid id '781' still running, waiting... 2024-07-23 10:36:34,181 DEBG 'watchdog-script' stdout output: [info] Child process with pid id '781' still running, waiting... 2024-07-23 10:36:34,682 DEBG 'watchdog-script' stdout output: [info] Child process with pid id '781' still running, waiting... 2024-07-23 10:36:34,682 INFO waiting for start-script, watchdog-script to die 2024-07-23 10:36:35,183 DEBG 'watchdog-script' stdout output: [info] Child process with pid id '781' still running, waiting... 2024-07-23 10:36:35,684 DEBG 'watchdog-script' stdout output: [info] Child process with pid id '781' still running, waiting... 2024-07-23 10:36:36,186 DEBG 'watchdog-script' stdout output: [info] Child process with pid id '781' still running, waiting... 2024-07-23 10:36:36,687 DEBG 'watchdog-script' stdout output: [info] Child process with pid id '781' still running, waiting... 2024-07-23 10:36:37,188 DEBG 'watchdog-script' stdout output: [info] Child process with pid id '781' still running, waiting... 2024-07-23 10:36:37,689 DEBG 'watchdog-script' stdout output: [info] Child process with pid id '781' still running, waiting... 2024-07-23 10:36:37,690 INFO waiting for start-script, watchdog-script to die 2024-07-23 10:36:38,191 DEBG 'watchdog-script' stdout output: [info] Child process with pid id '781' still running, waiting...

Update from 6.12.10 to 6.12.11. No issues whatsoever. Really really really want to run unRAID 7 Beta, but will hold off. Dockers and VM's working fine after update. Even was able to reboot after upgrade without powering down. For many version, a power cycle has been required on my system, but not this time. Thanks!

I finally upgraded the last five 8TB hard drives to 14TB hard drives. 220TB storage space with dual parity. I'm looking forward to much faster parity checks because slowing down for three different hard drive sizes was rough, and the 8TB drives were much slower than the 14TB drives. Got the five WHITE 14TB drives used from a miner with three years on them for $75 each. Cheap enough because when I can get 20TB drives for $150 or less (couple years?), I plan to remove five drives from the array and swap the rest all out to the same capacity.

No fear here. Just extra happy that the startup time is faster. Thanks again!

binhex I just updated today again to your newest. I have never started deluge and had it come online so quickly. It only took a few moments to get the web GUI and thinclient up. Did you speed things up somehow? Thanks!

Here are my fan mods on the ICX-7450 so that it now is nearly silent instead of sounding like a jet taking off out of my equipment room https://forums.servethehome.com/index.php?threads/new-icx7450-or-6610-fan-mod-setup-metal-case-lid.44604/

I have been looking for a Brocade ICX7450-32ZP switch for the right price seemingly FOREVER) like at least 4-5 years) and I finally scored one! That gave me 8x 2.5GB PoE ports! They are now powering three Ruckus R750 WiFi AP's using PoE on their 2.5GB inputs. Sweet AP's I must say! 5500 square foot house and back yard patio over the dethatched garage with very strong signal strength everywhere and in the city with tons of interference. Ruckus/Brocade deal incredibly will with loads of interference. I hear the R650's are nearly as good; highly recommended!

EDIT: Deluge must be stopped to edit the file! You can also brows your appdata folder, go to binhex-delugevpn, and manually edit the core.conf file with a plain text editor if you prefer GUI to CLI.

Here is my FLOATING rule. Could you not just put the IP of your client in regardless of vlan? Not sure, just woke and am very foggy.

I can probably figure out sense when my brain is less foggy. Right now I'm going to sleep.

I’m sorry, but I use my Brocade switch to manage my vlans. My only vlan that sees OPNsrnse is ve1. I don’t know how to specify this in OPN or PF.

I can hardly think, but it looks like I have it working: 2024-07-03 12:49:51,081 DEBG 'watchdog-script' stdout output: Setting "listen_ports" to: (41229, 41229) Configuration value successfully updated. 2024-07-03 12:49:51,081 DEBG 'watchdog-script' stderr output: <Deferred at 0x14b632742120 current result: None> 2024-07-03 12:49:53,475 DEBG 'watchdog-script' stderr output: <Deferred at 0x1508d64ce570 current result: None> 2024-07-03 12:49:53,519 DEBG 'watchdog-script' stdout output: [info] No torrents with state 'Error' found 2024-07-03 12:49:53,520 DEBG 'watchdog-script' stdout output: [info] Starting Deluge Web UI... 2024-07-03 12:49:53,520 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI started 2024-07-03 12:58:53,270 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '41229'

Thanks. I get it, it'll be fine, I just have to make some adjustments. The drugs are kicking in so yeah, I'm good 🤪.

Correction, I just checked and have no clients connected. I’ll have to fix it when I get home. Crap. Your upgrade appears to be working as you intend.

When I left for the hospital I tried to connect with my DNS at 192.168.1.1 and it failed the first time. I restarted deluge docker and it worked second attempt and deluge was running with clients connected when I left. I’ll get you the files you request as soon as I am able. I’m in my first surgery as we speak but will be incapacitated for second surgery. I’ll try to get you info tomorrow but I have a full day. OK, I did not think I had a DNS rule to allow deluge Docker to use alternate DNS. Your change makes sense than and explains why the Docker worked using external DNS until this update (I guess because it was really using my local DNS). Also explains why it’s Q&A 35 and the newest (or at least last) on your list

My question is then why does my local unbound DNS server work? 192.168.1.1. According to the Q&A it should not. I do block other DNS servers with OPNsense, but until today your Docker worked fine. I’ll have to look back, but I must have a rule to allow your docker to use another DNS server since it’s always worked. Deluge connected Monday morning because it was automatically shutdown for backup at 4:00 on the 2nd of July. I was out of town. I don’t let the deluge Docker auto update. I manually updated it last night and went to bed. Then realized this morning I was not connected and in that DNS loop.