Jump to content

john_smith

Members
 View Profile  See their activity

  • Posts

    17

  • Joined

  • Last visited

 Content Type 

Posts posted by john_smith

    [Support] MattFaz Repo

    in Docker Containers

    Posted

    20 hours ago, MattFaz said:

    @maddog @john_smith @AirRicB
    You need to setup the Postgres database yourself, it will not create one for you.
    You then need to provide the details when setting up the FIrefly-iii container.

    You can use an app like pgadmin to perform this, you don't need to create any tables. Just create the database, user, and password (if not using an existing user and pass).

    image.png

     

    ok, trying to log into postgres now but it doesn't seem to be working? (page loads, but incorrect password or username)

     

    am i missing a link i need to be making first? i'm using the username and password that i used to set up the postgres15 container

    [Plugin] Tailscale

    in Plugin Support

    Posted

    On 12/30/2023 at 3:54 PM, EDACerton said:

    I can’t do much with this information… it’s too vague for me to help. 
     

    What are you trying to connect to? WebGUI? SMB? Docker containers?

     

    Can you post plugin diagnostics? (See the pinned post.)

    fair enough - it turns out my issue was actually just a general misunderstanding of how tailscale works. My setup was up and running correctly turns out, but i did not understand how to access the resource i wanted to access.

     

    thanks for the reply

    • Like 1

    [Support] MattFaz Repo

    in Docker Containers

    Posted

    I'm new to using these kind of containers and trying to get firefly iii (and later data importer) installed, but having an issue with the DB not existing. If this is anything like TeslaMate which also uses postgres, then i assume i might need to give the container permission to create the database, right?

     

    though i tried a similar command to the one i used for when i did that install to no avail. I'm also assuming it's not an issue to use the same postgres instance (host & port) and the associated DB username and password i had already used for my TeslaMate container.

     

    here's the error regardless in case my assumption is wrong: 

    Unfortunately, this error was not recoverable :(. Firefly III broke. The error is:

Could not poll the database: SQLSTATE[08006] [7] FATAL: database "fireflyiii" does not exist (Connection: pgsql, SQL: select "id", "name", "data" from "configuration" where "name" = is_demo_site and "configuration"."deleted_at" is null limit 1)

This error occured in file /var/www/html/app/Support/FireflyConfig.php on line 65 with code 0.

     

    [Plugin] Tailscale

    in Plugin Support

    Posted

    so i configured this plugin and confirmed green on host and client after setup, but i can't actually seem to be able to access any of my local resources remotely as i would expect to be able to do via the tailscale VPN. am i missing something in the settings?

    Securely auto-start 6.8+ Encrypted array using SFTP from your phone OR quick and dirty auto-start

    in General Support

    Posted · Edited by john_smith
    added detail/question

    couple of questions on the steps

    • why would you not use a password in the primitive ftpd settings? wouldn't this be more secure?
      • tbh i am not sure what the public key authentication option does, are we using the same keyfile from unraid as a file for authentication elsewhere? i thought we were literally putting the file in the phone and using SFTP to sync it each time
    • are the below steps still necessary if also doing the additional optional steps with p7zip?
    Quote

     

    Quick and dirty Side note, if you just want to build your array with encryption now since it is a royal pain to change later, you can simply add the below command directly to the go file. It is not secure but will get you going and you can get more advanced later. It is still better then nothing, simply yank the unraid USB and power cord from the computer and everything is secure.

     

    Personally I would recommend using an encrypted array if you think there is any chance you might wish you had it in the future, much much better to do it when first setting up unraid then trying to swap over later.

    echo -n 'password_here' > keyfile

    You will most likely need to change permissions to be able to copy it to your phone:

    chmod ugo+rwx keyfile

    Edit: This is technically an optional step but I would highly recommend it as it is far more secure and does not expose your actual array password in plain text.

     

     

    Best Way to Encrypt Exist Disks?

    in General Support

    Posted

    20 minutes ago, Phoenix Down said:

    What happens if you tried a different disk first?

    I could move everything to my new large drive and try that one first, then I would subsequently want to move the files back to the small old drive in order to try encrypting the large empty drive again. 

     

    Is there something that would change from doing that with regards to encrypting the large new disk?

    Best Way to Encrypt Exist Disks?

    in General Support

    Posted

    here are the logs:

    Spoiler

    Dec  1 17:33:19 HTPC kernel: mdcmd (52): nocheck pause
    Dec  1 17:33:21 HTPC emhttpd: creating volume: disk2 (xfs - encrypted)
    Dec  1 17:33:21 HTPC emhttpd: shcmd (137720): /sbin/wipefs -a /dev/sdb
    Dec  1 17:33:22 HTPC root: /dev/sdb: 8 bytes were erased at offset 0x00000200 (gpt): 45 46 49 20 50 41 52 54
    Dec  1 17:33:22 HTPC root: /dev/sdb: 8 bytes were erased at offset 0x1230bffffe00 (gpt): 45 46 49 20 50 41 52 54
    Dec  1 17:33:22 HTPC root: /dev/sdb: 2 bytes were erased at offset 0x000001fe (PMBR): 55 aa
    Dec  1 17:33:22 HTPC root: /dev/sdb: calling ioctl to re-read partition table: Success
    Dec  1 17:33:22 HTPC emhttpd: writing GPT on disk (sdb), with partition 1 byte offset 32KiB, erased: 0
    Dec  1 17:33:22 HTPC emhttpd: shcmd (137721): sgdisk -Z /dev/sdb
    Dec  1 17:33:23 HTPC root: Creating new GPT entries in memory.
    Dec  1 17:33:23 HTPC root: GPT data structures destroyed! You may now partition the disk using fdisk or
    Dec  1 17:33:23 HTPC root: other utilities.
    Dec  1 17:33:23 HTPC emhttpd: shcmd (137722): sgdisk -o -a 8 -n 1:32K:0 /dev/sdb
    Dec  1 17:33:24 HTPC root: Creating new GPT entries in memory.
    Dec  1 17:33:24 HTPC root: The operation has completed successfully.
    Dec  1 17:33:24 HTPC kernel: sdb: sdb1
    Dec  1 17:33:24 HTPC emhttpd: shcmd (137723): udevadm settle
    Dec  1 17:33:24 HTPC emhttpd: mounting /mnt/disk2
    Dec  1 17:33:24 HTPC emhttpd: shcmd (137724): mkdir -p /mnt/disk2
    Dec  1 17:33:24 HTPC emhttpd: /mnt/disk2 mount error: Volume not encrypted
    Dec  1 17:33:24 HTPC emhttpd: shcmd (137725): rmdir /mnt/disk2
    Dec  1 17:33:24 HTPC emhttpd: Starting services...
    Dec  1 17:33:24 HTPC emhttpd: shcmd (137729): /etc/rc.d/rc.samba restart
    Dec  1 17:33:24 HTPC wsdd2[23016]: 'Terminated' signal received.
    Dec  1 17:33:24 HTPC winbindd[23019]: [2023/12/01 19:33:24.464016,  0] ../../source3/winbindd/winbindd_dual.c:1950(winbindd_sig_term_handler)
    Dec  1 17:33:24 HTPC winbindd[23019]:   Got sig[15] terminate (is_parent=1)
    Dec  1 17:33:24 HTPC wsdd2[23016]: terminating.
    Dec  1 17:33:24 HTPC winbindd[23022]: [2023/12/01 19:33:24.464336,  0] ../../source3/winbindd/winbindd_dual.c:1950(winbindd_sig_term_handler)
    Dec  1 17:33:24 HTPC winbindd[23022]:   Got sig[15] terminate (is_parent=0)
    Dec  1 17:33:24 HTPC winbindd[24197]: [2023/12/01 19:33:24.466769,  0] ../../source3/winbindd/winbindd_dual.c:1950(winbindd_sig_term_handler)
    Dec  1 17:33:24 HTPC winbindd[24197]:   Got sig[15] terminate (is_parent=0)
    Dec  1 17:33:26 HTPC root: Starting Samba:  /usr/sbin/smbd -D
    Dec  1 17:33:26 HTPC smbd[25806]: [2023/12/01 19:33:26.673575,  0] ../../source3/smbd/server.c:1741(main)
    Dec  1 17:33:26 HTPC smbd[25806]:   smbd version 4.17.10 started.
    Dec  1 17:33:26 HTPC smbd[25806]:   Copyright Andrew Tridgell and the Samba Team 1992-2022
    Dec  1 17:33:26 HTPC root:                  /usr/sbin/wsdd2 -d -4
    Dec  1 17:33:26 HTPC root:                  /usr/sbin/winbindd -D
    Dec  1 17:33:26 HTPC wsdd2[25823]: starting.
    Dec  1 17:33:26 HTPC winbindd[25824]: [2023/12/01 19:33:26.791907,  0] ../../source3/winbindd/winbindd.c:1440(main)
    Dec  1 17:33:26 HTPC winbindd[25824]:   winbindd version 4.17.10 started.
    Dec  1 17:33:26 HTPC winbindd[25824]:   Copyright Andrew Tridgell and the Samba Team 1992-2022
    Dec  1 17:33:26 HTPC winbindd[25826]: [2023/12/01 19:33:26.796899,  0] ../../source3/winbindd/winbindd_cache.c:3117(initialize_winbindd_cache)
    Dec  1 17:33:26 HTPC winbindd[25826]:   initialize_winbindd_cache: clearing cache and re-creating with version number 2
    Dec  1 17:33:26 HTPC emhttpd: shcmd (137733): /etc/rc.d/rc.avahidaemon restart
    Dec  1 17:33:26 HTPC root: Stopping Avahi mDNS/DNS-SD Daemon: stopped
    Dec  1 17:33:26 HTPC avahi-daemon[23073]: Got SIGTERM, quitting.
    Dec  1 17:33:26 HTPC avahi-dnsconfd[23084]: read(): EOF

     

    Best Way to Encrypt Exist Disks?

    in General Support

    Posted

    10 hours ago, Phoenix Down said:

     

    See my reply above:

     

     

    Did you start the array back up after you changed the disk type to "XFS Encrypted"?

     

     

    thanks for the quick reply. i did start it back up after changing the disk type, that's when i was presented with the format option near the bottom of the page. from there:

    1. I check the checkbox, and and select OK on the popup
    2. I select Format, the page reloads
    3. "Started, formatting..." shows up for a few seconds
    4. The page reloads again,
    5. The disk shows up as unmounted and unencrypted, with the test to the right showing: "Unmountable: Volume not encrypted", remaining with the XFS file system

    Best Way to Encrypt Exist Disks?

    in General Support

    Posted

    posting here since it seems to be the most recent post on the topic - i also tried following the space invader one video, and have tried a handful of other things as well since i'm having trouble (including referencing the simpler steps on https://docs.unraid.net/unraid-os/manual/security/data-encryption/

     

    However, I'm still having trouble encrypting a new 20TB disk i'm trying to add. these are the steps i'm following:

    • Go to the Main tab.
    • Stop the array.
    • Select the drive.
    • In File system type change the file system to the encrypted type that you want.
    • Select Apply to commit the change.
    • Select Done to return to the Main tab.
    • The drive now shows as unmountable and the option to format unmountable drives is present.
    • I check the checkbox, and and select OK on the popup
    • I select Format, the page reloads
    • "Started, formatting..." shows up for a few seconds
    • The page reloads again, the disk remains unmounted and unencrypted, showing: "Unmountable: Volume not encrypted" and remains with the XFS file system

    am i missing something?

×
×
  • Create New...