BrunoVic

Hello, I attempted to upgrade my FoundryVTT to 14 and now I am getting this error message. node:internal/modules/cjs/loader:1459 throw err; ^ Error: Cannot find module '/foundry/fvtt/resources/app/main.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1456:15) at defaultResolveImpl (node:internal/modules/cjs/loader:1066:19) at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1071:22) at Module._load (node:internal/modules/cjs/loader:1242:25) at wrapModuleLoad (node:internal/modules/cjs/loader:255:19) at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:154:5) at node:internal/main/run_main_module:33:47 { code: 'MODULE_NOT_FOUND', requireStack: [] } Node.js v24.14.1 Since then I have uninstalled and reinstalled the container and copied the linux install to the /foundry/fvtt mapped directory and verified that it was there with ls but for whatever reason the container will not see the files. root@Storage:/mnt/user/appdata/FoundryVTT# docker exec -it FoundryVTT bash Storage:/# ls -la /foundry/fvtt/resources/app/ total 168 drwxrwxrw- 1 root root 224 May 29 04:00 . drwxrwxrw- 1 root root 34 May 29 03:58 .. drwxrwxrw- 1 root root 292 May 29 03:58 client drwxrwxrw- 1 root root 254 May 29 03:58 common drwxrwxrw- 1 root root 208 May 29 03:58 dist -rwxrwxrw- 1 root root 7552 May 22 22:19 license.html -rwxrwxrwx 1 root root 271 May 22 22:19 main.js -rwxrwxrw- 1 root root 1212 May 22 22:19 main.mjs drwxrwxrw- 1 root root 7434 May 29 03:58 node_modules -rwxrwxrw- 1 root root 143772 May 22 22:19 package-lock.json -rwxrwxrw- 1 root root 2841 May 22 22:19 package.json drwxrwxrw- 1 root root 138 May 22 22:19 public drwxrwxrw- 1 root root 244 May 29 04:00 templates -rwxrwxrw- 1 root root 777 May 22 22:19 tsconfig.json Storage:/# root@Storage:/mnt/user/appdata/FoundryVTT# d4d94513a02e:/# cat /foundry/fvtt/resources/app/main.js #!/usr/bin/env node /** * Bootstrap the Node.js loader to support ESM imports * Required until https://github.com/electron/electron/issues/21457#issuecomment-815770296 is resolved * @returns {Promise<void>} */ (async function() { await import("./main.mjs"); })();

Yeah this is all confusing. I follow all these instructions and now I keep getting this and my nextcloud doesn't work. root@unraid:~# docker exec -it nextcloud occ maintenance:mode --off An unhandled exception has been thrown: Doctrine\DBAL\Exception: Failed to connect to the database: An exception occurred in the driver: SQLSTATE[HY000] [2006] MySQL server has gone away in /config/www/nextcloud/lib/private/DB/Connection.php:139 Stack trace: #0 /config/www/nextcloud/3rdparty/doctrine/dbal/src/Connection.php(1519): OC\DB\Connection->connect() #1 /config/www/nextcloud/3rdparty/doctrine/dbal/src/Connection.php(1041): Doctrine\DBAL\Connection->getWrappedConnection() #2 /config/www/nextcloud/lib/private/DB/Connection.php(261): Doctrine\DBAL\Connection->executeQuery() #3 /config/www/nextcloud/3rdparty/doctrine/dbal/src/Query/QueryBuilder.php(345): OC\DB\Connection->executeQuery() #4 /config/www/nextcloud/lib/private/DB/QueryBuilder/QueryBuilder.php(281): Doctrine\DBAL\Query\QueryBuilder->execute() #5 /config/www/nextcloud/lib/private/AppConfig.php(419): OC\DB\QueryBuilder\QueryBuilder->execute() #6 /config/www/nextcloud/lib/private/AppConfig.php(184): OC\AppConfig->loadConfigValues() #7 /config/www/nextcloud/lib/private/AppConfig.php(375): OC\AppConfig->getApps() #8 /config/www/nextcloud/lib/private/legacy/OC_App.php(967): OC\AppConfig->getValues() #9 /config/www/nextcloud/lib/private/Server.php(725): OC_App::getAppVersions() #10 /config/www/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php(163): OC\Server->OC\{closure}() #11 /config/www/nextcloud/3rdparty/pimple/pimple/src/Pimple/Container.php(122): OC\AppFramework\Utility\SimpleContainer->OC\AppFramework\Utility\{closure}() #12 /config/www/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php(130): Pimple\Container->offsetGet() #13 /config/www/nextcloud/lib/private/ServerContainer.php(136): OC\AppFramework\Utility\SimpleContainer->query() #14 /config/www/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php(57): OC\ServerContainer->query() #15 /config/www/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php(185): OC\AppFramework\Utility\SimpleContainer->get() #16 /config/www/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php(163): OC\AppFramework\Utility\SimpleContainer->OC\AppFramework\Utility\{closure}() #17 /config/www/nextcloud/3rdparty/pimple/pimple/src/Pimple/Container.php(118): OC\AppFramework\Utility\SimpleContainer->OC\AppFramework\Utility\{closure}() #18 /config/www/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php(130): Pimple\Container->offsetGet() #19 /config/www/nextcloud/lib/private/ServerContainer.php(136): OC\AppFramework\Utility\SimpleContainer->query() #20 /config/www/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php(57): OC\ServerContainer->query() #21 /config/www/nextcloud/lib/private/Server.php(1121): OC\AppFramework\Utility\SimpleContainer->get() #22 /config/www/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php(163): OC\Server->OC\{closure}() #23 /config/www/nextcloud/3rdparty/pimple/pimple/src/Pimple/Container.php(122): OC\AppFramework\Utility\SimpleContainer->OC\AppFramework\Utility\{closure}() #24 /config/www/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php(130): Pimple\Container->offsetGet() #25 /config/www/nextcloud/lib/private/ServerContainer.php(136): OC\AppFramework\Utility\SimpleContainer->query() #26 /config/www/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php(57): OC\ServerContainer->query() #27 /config/www/nextcloud/lib/private/Server.php(2072): OC\AppFramework\Utility\SimpleContainer->get() #28 /config/www/nextcloud/lib/private/Files/View.php(117): OC\Server->getLockingProvider() #29 /config/www/nextcloud/lib/private/Server.php(462): OC\Files\View->__construct() #30 /config/www/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php(163): OC\Server->OC\{closure}() #31 /config/www/nextcloud/3rdparty/pimple/pimple/src/Pimple/Container.php(122): OC\AppFramework\Utility\SimpleContainer->OC\AppFramework\Utility\{closure}() #32 /config/www/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php(130): Pimple\Container->offsetGet() #33 /config/www/nextcloud/lib/private/ServerContainer.php(136): OC\AppFramework\Utility\SimpleContainer->query() #34 /config/www/nextcloud/lib/private/AppFramework/Utility/SimpleContainer.php(57): OC\ServerContainer->query() #35 /config/www/nextcloud/lib/private/Server.php(1474): OC\AppFramework\Utility\SimpleContainer->get() #36 /config/www/nextcloud/lib/base.php(617): OC\Server->boot() #37 /config/www/nextcloud/lib/base.php(1145): OC::init() #38 /config/www/nextcloud/console.php(48): require_once('...') #39 /config/www/nextcloud/occ(11): require_once('...') #40 {main}root@unraid:~#

I also came here with the same problem. I install it for the first time and everything works fine. Then I restart the container and next thing I know it nothing is working. The container just stops and this is what I get in the logs. Authenticate | 2023-06-03 21:15:12 | [debug] Saving cookies to: cookiejar.json Authenticate | 2023-06-03 21:15:12 | [info] Requesting CSRF tokens from https://foundryvtt.com Authenticate | 2023-06-03 21:15:12 | [debug] Fetching: https://foundryvtt.com Authenticate | 2023-06-03 21:15:13 | [info] Logging in as: omit Authenticate | 2023-06-03 21:15:13 | [debug] Fetching: https://foundryvtt.com/auth/login/ Authenticate | 2023-06-03 21:15:13 | [debug] Community URL: /community/omit Authenticate | 2023-06-03 21:15:13 | [info] Successfully logged in as: omit Entrypoint | 2023-06-03 21:15:10 | [warn] The container may not function properly with this version mismatch. Entrypoint | 2023-06-03 21:15:10 | [info] Foundry Virtual Tabletop 11.300 is installed. Entrypoint | 2023-06-03 21:15:10 | [info] Requested version () from FOUNDRY_VERSION differs. Entrypoint | 2023-06-03 21:15:10 | [info] Uninstalling version 11.300. Entrypoint | 2023-06-03 21:15:11 | [info] Using FOUNDRY_RELEASE_URL to download release. Entrypoint | 2023-06-03 21:15:11 | [info] Using FOUNDRY_USERNAME and FOUNDRY_PASSWORD to authenticate. Entrypoint | 2023-06-03 21:15:13 | [info] Using CONTAINER_CACHE: /data/container_cache Entrypoint | 2023-06-03 21:15:13 | [info] Downloading Foundry Virtual Tabletop release. % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 52.218.168.243:443... * Connected to foundryvtt.s3.amazonaws.com (52.218.168.243) port 443 (#0) * ALPN: offers h2,http/1.1 } [5 bytes data] * TLSv1.3 (OUT), TLS handshake, Client hello (1): } [512 bytes data] * CAfile: /etc/ssl/certs/ca-certificates.crt * CApath: none { [5 bytes data] * TLSv1.3 (IN), TLS handshake, Server hello (2): { [110 bytes data] * TLSv1.2 (IN), TLS handshake, Certificate (11): { [4970 bytes data] * TLSv1.2 (IN), TLS handshake, Server key exchange (12): { [333 bytes data] * TLSv1.2 (IN), TLS handshake, Server finished (14): { [4 bytes data] * TLSv1.2 (OUT), TLS handshake, Client key exchange (16): } [70 bytes data] * TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1): } [1 bytes data] * TLSv1.2 (OUT), TLS handshake, Finished (20): } [16 bytes data] 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* TLSv1.2 (IN), TLS handshake, Finished (20): { [16 bytes data] * SSL connection using TLSv1.2 / omit * ALPN: server accepted http/1.1 * Server certificate: * subject: CN=*.s3.amazonaws.com * start date: Mar 21 00:00:00 2023 GMT * expire date: Dec 19 23:59:59 2023 GMT * subjectAltName: host "foundryvtt.s3.amazonaws.com" matched cert's "*.s3.amazonaws.com" * issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M01 * SSL certificate verify ok. * using HTTP/1.1 } [5 bytes data] > GET /releases/11.300/FoundryVTT-11.300.zip?AWSAccessKeyId=omit&Signature=omit&Expires=omit HTTP/1.1 > Host: foundryvtt.s3.amazonaws.com > User-Agent: curl/8.1.1 (felddy/foundryvtt:11.299.0) > Accept: */* > If-Modified-Since: Sun, 04 Jun 2023 01:12:17 GMT > { [5 bytes data] < HTTP/1.1 403 Forbidden < x-amz-request-id: omit < x-amz-id-2: omit < Content-Type: application/xml < Transfer-Encoding: chunked < Date: Sun, 04 Jun 2023 01:15:14 GMT < Server: AmazonS3 * The requested URL returned error: 403 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 * Closing connection 0 { [5 bytes data] * TLSv1.2 (OUT), TLS alert, close notify (256): } [2 bytes data] curl: (22) The requested URL returned error: 403

I needed it on the array because something was maxing out my cache drive and those where the only things using the cache drive at the time. Seeing how the docker containers are in the appdata folder and one of my docker containers went crazy writing 5.1TB of logs this would explains why when appdata was on the cache drive it was maxing out.

I've identified the problem. So once I stopped using my cache drive all together my array just maxed out 5.1TB. After doing more research I narrowed it down to a docker container (unifi) that stored 5.1TB of logs. That's what cause the cache drive to max out and since it was smaller than the array it maxed out quicker than the array itself.

Correction a directory called journal is 5.1TB big.

Yes I see those in the data folder under unifi. Can I just delete those files? How can I back things up?

Ok my raid is completely maxed out. This docker container is taking up 5.1 TB of space and I don't know how to get rid of it. Because my drives are maxed out this docker container won't load anymore and I get a 404 error so I cannot make any changes like “override inform host” as someone suggested above. How do I free up space in this docker container?

What in the world? Why is the unifi-controller eating up 5.1TB of space?

root@unraid:/mnt/user/appdata# du -hs ./unifi-controller/ 5.1T ./unifi-controller/

Something tells me this is the culprit! How in the world is my appdata maxing out at 5 TB? root@unraid:/mnt/user# du -hs ./appdata/ 5.1T ./appdata/

My hard drives keep maxing out for no reason and it is turning my NAS into a brick. Once it maxes out I cannot access shares to delete anything and free up space. I've even disabled docker containers and after freeing up space it still maxes out. I have no idea what's going on. unraid-diagnostics-20220831-1955.zip

Ok I'll look into an SSD option. Thank you.

That worked but what caused this in the first place? How can I avoid this?

Well ok then I disabled docker and now the cache driver is clearing up. Why am I running into this problem in the first place though? If I re-enable docker will the cache drive fill up again? How can I avoid this?

I didn't disable docker before the mover. I should do that?

So I am sitting here watching the mover work. For a moment I see it spike up to 100MB free space and then go back down. It keeps going back and forth between 100MB and 6MB. I see both the read and write counters moving at the same time. This is bizarre. unraid-diagnostics-20220825-1412.zip

I have set ALL the shares to yes which should move things off the cache drive and onto the array when the movers is invoked. However that doesn't seem to be the case for me and I don't know why it won't clear the cache drive. What can I provide that can help you help me?

On the array in the iso share.

Hello I am having strange issues where my Vaultwarden just won't authenticate any of my users. It either says "someone has requested your hint password" or "2fa doesn't exist" for accounts that have 2fa. The only thing that fixes this is a restart. But then it reverts back the way it was and won't let people log in again over time. These were the log outputs I gathered. [2022-08-25 09:51:15.420][request][INFO] POST /identity/connect/token [2022-08-25 09:51:15.507][vaultwarden::api::identity][ERROR] Username or password is incorrect. Try again. IP: [OMIT]. Username: [OMIT]. [2022-08-25 09:51:15.507][response][INFO] (login) POST /identity/connect/token => 400 Bad Request [2022-08-25 09:53:08.515][request][INFO] POST /api/accounts/prelogin [2022-08-25 09:53:08.515][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK [2022-08-25 09:53:08.707][request][INFO] POST /identity/connect/token [2022-08-25 09:53:08.791][vaultwarden::api::identity][ERROR] Username or password is incorrect. Try again. IP: [OMIT]. Username: [OMIT]. [2022-08-25 09:53:08.792][response][INFO] (login) POST /identity/connect/token => 400 Bad Request [2022-08-25 09:53:17.200][request][INFO] POST /api/accounts/prelogin [2022-08-25 09:53:17.200][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK [2022-08-25 09:53:17.260][request][INFO] POST /identity/connect/token [2022-08-25 09:53:17.344][vaultwarden::api::identity][ERROR] Username or password is incorrect. Try again. IP: [OMIT]. Username: [OMIT]. [2022-08-25 09:53:17.344][response][INFO] (login) POST /identity/connect/token => 400 Bad Request [2022-08-25 09:53:40.155][request][INFO] POST /api/accounts/prelogin [2022-08-25 09:53:40.156][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK [2022-08-25 09:53:40.248][request][INFO] POST /identity/connect/token [2022-08-25 09:53:40.248][vaultwarden::api::identity][ERROR] Username or password is incorrect. Try again. IP: [OMIT]. Username: [OMIT]. [2022-08-25 09:53:40.248][response][INFO] (login) POST /identity/connect/token => 400 Bad Request [2022-08-25 09:53:49.165][request][INFO] POST /api/accounts/prelogin [2022-08-25 09:53:49.165][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK [2022-08-25 09:53:49.267][request][INFO] POST /identity/connect/token [2022-08-25 09:53:49.267][vaultwarden::api::identity][ERROR] Username or password is incorrect. Try again. IP: [OMIT]. Username: [OMIT]. [2022-08-25 09:53:49.267][response][INFO] (login) POST /identity/connect/token => 400 Bad Request [2022-08-25 09:54:05.211][request][INFO] POST /api/accounts/prelogin [2022-08-25 09:54:05.212][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK [2022-08-25 09:54:05.297][request][INFO] POST /identity/connect/token [2022-08-25 09:54:05.297][vaultwarden::api::identity][ERROR] Username or password is incorrect. Try again. IP: [OMIT]. Username: [OMIT]. [2022-08-25 09:54:05.297][response][INFO] (login) POST /identity/connect/token => 400 Bad Request [2022-08-25 09:57:28.009][request][INFO] POST /api/accounts/prelogin [2022-08-25 09:57:28.009][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK [2022-08-25 09:57:28.104][request][INFO] POST /identity/connect/token [2022-08-25 09:57:28.191][vaultwarden::api::identity][ERROR] Username or password is incorrect. Try again. IP: [OMIT]. Username: [OMIT]. [2022-08-25 09:57:28.191][response][INFO] (login) POST /identity/connect/token => 400 Bad Request [2022-08-25 09:57:39.609][request][INFO] POST /api/accounts/prelogin [2022-08-25 09:57:39.610][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK [2022-08-25 09:57:39.674][request][INFO] POST /identity/connect/token [2022-08-25 09:57:39.758][vaultwarden::api::identity][ERROR] Username or password is incorrect. Try again. IP: [OMIT]. Username: [OMIT]. [2022-08-25 09:57:39.758][response][INFO] (login) POST /identity/connect/token => 400 Bad Request [2022-08-25 10:01:36.931][request][INFO] POST /api/accounts/password-hint [2022-08-25 10:01:37.926][response][INFO] (password_hint) POST /api/accounts/password-hint => 200 OK [2022-08-25 10:03:46.726][request][INFO] POST /api/accounts/prelogin [2022-08-25 10:03:46.726][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK [2022-08-25 10:03:46.807][request][INFO] POST /identity/connect/token [2022-08-25 10:03:46.807][vaultwarden::api::identity][ERROR] Username or password is incorrect. Try again. IP: [OMIT]. Username: [OMIT]. [2022-08-25 10:03:46.807][response][INFO] (login) POST /identity/connect/token => 400 Bad Request [2022-08-25 11:32:22.147][request][INFO] POST /api/accounts/prelogin [2022-08-25 11:32:22.148][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK [2022-08-25 11:32:22.403][request][INFO] POST /identity/connect/token [2022-08-25 11:32:22.528][error][ERROR] Error adding twofactor_incomplete record. [CAUSE] DatabaseError( __Unknown, "database or disk is full", ) [2022-08-25 11:32:22.528][response][INFO] (login) POST /identity/connect/token => 400 Bad Request [2022-08-25 11:32:41.035][vaultwarden][INFO] Exiting vaultwarden! [2022-08-25 11:32:41.035][rocket::server][WARN] Received SIGTERM. Shutdown already in progress. [2022-08-25 11:32:41.035][vaultwarden][INFO] Vaultwarden process exited! /--------------------------------------------------------------------\ | Starting Vaultwarden | | Version 1.25.2 | |--------------------------------------------------------------------| | This is an *unofficial* Bitwarden implementation, DO NOT use the | | official channels to report bugs/features, regardless of client. | | Send usage/configuration questions or feature requests to: | | https://vaultwarden.discourse.group/ | | Report suspected bugs/issues in the software itself at: | | https://github.com/dani-garcia/vaultwarden/issues/new | \--------------------------------------------------------------------/ [INFO] No .env file found. [WARNING] The following environment variables are being overriden by the config file, [WARNING] please use the admin panel to make changes to them: [WARNING] SIGNUPS_ALLOWED, INVITATIONS_ALLOWED, ADMIN_TOKEN [2022-08-25 11:32:43.556][start][INFO] Rocket has launched from http://0.0.0.0:80 [2022-08-25 11:32:57.436][request][INFO] POST /api/accounts/prelogin [2022-08-25 11:32:57.437][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK [2022-08-25 11:32:57.821][request][INFO] POST /identity/connect/token [2022-08-25 11:32:57.915][error][ERROR] 2FA token not provided [2022-08-25 11:32:57.915][response][INFO] (login) POST /identity/connect/token => 400 Bad Request [2022-08-25 11:33:04.602][request][INFO] POST /identity/connect/token [2022-08-25 11:33:04.694][vaultwarden::api::identity][INFO] User [OMIT] logged in successfully. IP: [OMIT] [2022-08-25 11:33:04.694][response][INFO] (login) POST /identity/connect/token => 200 OK [2022-08-25 11:33:05.036][request][INFO] POST /identity/connect/token [2022-08-25 11:33:05.041][response][INFO] (login) POST /identity/connect/token => 200 OK [2022-08-25 11:33:05.238][request][INFO] GET /api/sync [2022-08-25 11:33:05.467][response][INFO] (sync) GET /api/sync?<data..> => 200 OK [2022-08-25 11:33:05.537][_][WARN] Response was `None`. [2022-08-25 11:33:05.537][_][WARN] No 404 catcher registered. Using Rocket default. [2022-08-25 11:35:32.605][request][INFO] GET /admin [2022-08-25 11:35:32.605][_][WARN] Request guard `AdminToken` is forwarding. [2022-08-25 11:35:32.605][response][INFO] (admin_login) GET /admin/ [2] => 200 OK [2022-08-25 11:35:40.099][request][INFO] POST /admin [2022-08-25 11:35:40.102][response][INFO] (post_admin_login) POST /admin/ => 303 See Other [2022-08-25 11:35:40.258][request][INFO] GET /admin [2022-08-25 11:35:40.263][response][INFO] (admin_page) GET /admin/ => 200 OK [2022-08-25 11:36:26.696][_][WARN] Response was `None`. [2022-08-25 11:36:26.696][_][WARN] No 404 catcher registered. Using Rocket default.

I noticed that after creating a VM and launching it I could hear my HDD working overtime when my VM booted up. Is this normal or did I set something wrong. I looked under the main tab too and that write number is moving very fast which explains what I am hearing. The moment I turn off the VM the write number stops increasing so I know that it is the VM doing that. What in the world is it writing if all it is doing is reading the hard drive? I'm kind of afraid that this will significantly shorten the life of my HDDs.

Ok I think I figured out why I couldn't remove those static routes. User error I forgot to turn off docker. So once docker is off I cleaned up the routing table the way I liked it turned docker back on and everything is working as I would like it. I did notice however once the network daemon restarts it will rebuild the routing table with those static routes that I do not want. Is there a way to stop that from happening?

Yes different subnets do access the gui. But that's because I am allowing it for now through the firewall. I plan on forcing all gui traffic to go to the server vlan ip address which is the 30.5 ip. The reason I have the other VLANs has more to do with what I am trying to do with my unifi docker container trying to implement multi vlan wifi networks. That a whole completely different topic on it's own. But for the purposes of management and smb all I want is for ALL networks to access 30.5 and nothing else.

Okay so THIS is my ultimate goal...

Oh and the interVLAN routing is done on the pfSense not the UNRAID. I don't expect the UNRAID to do any routing other than static routes to their respective networks. The interVLAN is working flawlessly. The problem is that UNRAID can't make up it's mind as to which destination it wants to send the traffic to. From the looks of it what I ultimately want done is I want to re-enable VLAN20 but I DON'T want a static route put in the routing table for VLAN20. I need ALL default routes to go to the 30.0/24 interface. Unfortunately I cannot delete those static routes for some reason.