emsixteen

Is there any way for me to schedule one of the stacks I have in Compose Manager to restart every X days or so?

Where are the files for and which run the kiwix itself, the web server n' that? Where is that running from? It feels wrong to me to keep the zim files in the appdata folder, 100GB+ files shouldn't be in there imo and I believe there should be a separation of concerns. I do have it working as-is and appreciate that it was very easy to get set-up, but my questions are still there.

Hey! I think this is the correct topic for the kiwix-serve, right? I'm confused – Where are the files for kiwix actually at? I see one path in the container when setting it up, 'Appdata', which sits in '/mnt/user/appdata/kiwix-serve/'. There's also the Download variable, which has the URL for a vim file. I thought that the appdata folder would contain all the files that kiwix needed to run the webserver, etc., but when I start the container the only thing in there is the zim file which has been downloaded. I had actually added another path to the container, where I had intended to keep the zim files, separate from the appdata folder.

.. I just want to know which approach I should use which will get me this functionality, or if I should wait for Unraid changes. 😅

Bringing the stack down doesn't fix the issue – The loading icon's still there, and I can't interact with the buttons along the bottom of the Docker Containers section, or the buttons in the Commands column added in the Compose section. I just found what the issue what the issue was though, right after writing that. I'd removed one of the applications from the stack, recyclarr, and it was still in the Docker Containers list saying Rebuilding. Can be seen briefly in my video. Removing that from there fixed the issue. 🙂 --- I have another little question actually. When I use update stack everything seems to update, but in the list they all still say "Apply update" - I'm guessing this is normal?

This really seemed the part, until I tried logging in without my key to check – I'm still prompted for my password and can log in with it. It seems to just be straight up ignoring the settings in sshd_config, but I've no idea what's going on really. Here's my terminal output, including the contents of sshd_config: me@my-machine ~ % ssh [email protected] -p 2122 ([email protected]) Password: Last login: Wed Jan 15 10:43:19 2025 from 321.321.321.321 Linux 6.1.103-Unraid. root@Cube:~# cat /boot/config/ssh/sshd_config # $OpenBSD: sshd_config,v 1.104 2021/07/02 05:11:21 dtucker Exp $ # This is the sshd server system-wide configuration file. See # sshd_config(5) for more information. # This sshd was compiled with PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin # The strategy used for options in the default sshd_config shipped with # OpenSSH is to specify options with their default value where # possible, but leave them commented. Uncommented options override the # default value. #Port 22 AddressFamily inet ListenAddress 192.168.10.123 # br0 ListenAddress 10.0.0.1 # br1 #HostKey /etc/ssh/ssh_host_rsa_key #HostKey /etc/ssh/ssh_host_ecdsa_key #HostKey /etc/ssh/ssh_host_ed25519_key # Ciphers and keying #RekeyLimit default none # Logging #SyslogFacility AUTH #LogLevel INFO # limetech - lets be verbose LogLevel VERBOSE # Authentication: # limetech - we need to allow root AllowUsers root PermitRootLogin yes #LoginGraceTime 2m PermitRootLogin prohibit-password #StrictModes yes #MaxAuthTries 6 #MaxSessions 10 PubkeyAuthentication yes # The default is to check both .ssh/authorized_keys and .ssh/authorized_keys2 # but this is overridden so installations will only check .ssh/authorized_keys AuthorizedKeysFile .ssh/authorized_keys #AuthorizedPrincipalsFile none #AuthorizedKeysCommand none #AuthorizedKeysCommandUser nobody # For this to work you will also need host keys in /etc/ssh/ssh_known_hosts #HostbasedAuthentication no # Change to yes if you don't trust ~/.ssh/known_hosts for # HostbasedAuthentication #IgnoreUserKnownHosts no # Don't read the user's ~/.rhosts and ~/.shosts files #IgnoreRhosts yes # To disable tunneled clear text passwords, change to no here! PasswordAuthentication no PermitEmptyPasswords no # Change to no to disable s/key passwords #KbdInteractiveAuthentication yes # Kerberos options #KerberosAuthentication no #KerberosOrLocalPasswd yes #KerberosTicketCleanup yes #KerberosGetAFSToken no # GSSAPI options #GSSAPIAuthentication no #GSSAPICleanupCredentials yes # Set this to 'yes' to enable PAM authentication, account processing, # and session processing. If this is enabled, PAM authentication will # be allowed through the KbdInteractiveAuthentication and # PasswordAuthentication. Depending on your PAM configuration, # PAM authentication via KbdInteractiveAuthentication may bypass # the setting of "PermitRootLogin without-password". # If you just want the PAM account and session checks to run without # PAM authentication, then enable this but set PasswordAuthentication # and KbdInteractiveAuthentication to 'no'. UsePAM yes #AllowAgentForwarding yes #AllowTcpForwarding yes # limeteh - disallow forwarding but see below AllowTcpForwarding no #GatewayPorts no #X11Forwarding no #X11DisplayOffset 10 #X11UseLocalhost yes #PermitTTY yes #PrintMotd yes #PrintLastLog yes #TCPKeepAlive yes #PermitUserEnvironment no #Compression delayed #ClientAliveInterval 0 #ClientAliveCountMax 3 #UseDNS no #PidFile /var/run/sshd.pid #MaxStartups 10:30:100 #PermitTunnel no #ChrootDirectory none #VersionAddendum none # no default banner path #Banner none # override default of no subsystems Subsystem sftp /usr/libexec/sftp-server # Example of overriding settings on a per-user basis #Match User anoncvs # X11Forwarding no # AllowTcpForwarding no # PermitTTY no # ForceCommand cvs server # limetech - permit only root SSH tunneling Match Group root AllowTcpForwarding yes root@Cube:~#

Here's a screen recording showing. Loading icon and can't interact on the Docker tab, then can access settings through the tool's own settings page. Screen Recording 2025-01-13 at 10.04.16.mov

I have a stack on which I clicked 'Update stack' a few weeks ago, and I accidentally closed the windowed that popped up in the middle of it doing those updates. After that I couldn't interact with the buttons for the stack at all, at least from the Docker Containers page, and there was a permanent Unraid loading icon in the center of the screen. I tried disabling Docker on Unraid and re-enabling, which worked for me to interact with those buttons one time, but after that the loading icon was back. Tried removing this compose manager tool, and reinstalling, but even still there's the loading icon when on that page. I figured out that I can access the buttons from the tool's own settings page, but surely there must be something I can clear/reset somewhere to fix this? 🙂 On Unraid 6.12.12, and Docker Compose Manager version 2024.09.13.