Jump to content

Ruthalas

Members
  • Content Count

    85
  • Joined

  • Last visited

Community Reputation

3 Neutral

About Ruthalas

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Current situation: When a docker has an update that can be applied, it can be somewhat difficult to track down it's home repository and read through what changes have been made. Ex: Click docker icon, determine whether 'more info' or 'project page' links to a repo rather than a descriptive website, if a dockerhub page is linked search it to find a link to the github repo, navigate to releases, etc. Suggested change: Add a 'View Changes' button next to 'Apply Update' that links to the base repository the docker installation pulls from, specifically to the change history section if present on the site. This could be supported by having another field to fill when creating templates that is specifically for the change history portion of whatever site the base repo is pointing to, or by guessing based on the domain (ex: you can append '/releases' to the github link). In theory, I'd like to make this check for every update I make to important dockers, so having a direct link to the releases or change history for these projects would be very convenient.
  2. I second that request (for restore functionality). No hurry, but that would be a valuable addition.
  3. It looks like my friend found a solution. u/Toastman89 suggested the following solution on Reddit:
  4. Good afternoon folks, I have been trying to assist a friend in setting up a windows VM, but they've run in to an issue that I haven't seen before. As far as I can tell, the issue is that, regardless of which virtio driver package they select (and download) in the VM Manager pane, when they get to the "load driver" step in a Windows (7/10) setup, the mounted drive has the 0.1.1 virtio driver package. (This package doesn't work, I assume because it is old and outdated.) I've had him restart the server, toggle the VM Manager off and on, and select alternate (newish) virtio driver packages. But in each case, when he gets to the "load driver" step, the 0.1.1 version is mounted. Can anyone provide guidance on how to resolve this? If you need diagnostic logs, please let me know and I'll try to get them from him. Edit: Pictures and Video of his configuration prior to issue resolution, for posterity.
  5. Hey yggdranil. I am trying to get this spun up, and I think I have entered all the fields correctly, but the docker container fails to start. If you could provide any guidance, I'd be grateful. The unRAID log shows the following when I start the container: Sep 7 17:27:22 MY-HOSTNAME kernel: docker0: port 10(veth413a681) entered blocking state Sep 7 17:27:22 MY-HOSTNAME kernel: docker0: port 10(veth413a681) entered disabled state Sep 7 17:27:22 MY-HOSTNAME kernel: device veth413a681 entered promiscuous mode Sep 7 17:27:22 MY-HOSTNAME kernel: IPv6: ADDRCONF(NETDEV_UP): veth413a681: link is not ready Sep 7 17:27:22 MY-HOSTNAME kernel: docker0: port 10(veth413a681) entered blocking state Sep 7 17:27:22 MY-HOSTNAME kernel: docker0: port 10(veth413a681) entered forwarding state Sep 7 17:27:22 MY-HOSTNAME kernel: docker0: port 10(veth413a681) entered disabled state Sep 7 17:27:25 MY-HOSTNAME kernel: eth0: renamed from veth4b32693 Sep 7 17:27:25 MY-HOSTNAME kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth413a681: link becomes ready Sep 7 17:27:25 MY-HOSTNAME kernel: docker0: port 10(veth413a681) entered blocking state Sep 7 17:27:25 MY-HOSTNAME kernel: docker0: port 10(veth413a681) entered forwarding state Sep 7 17:27:26 MY-HOSTNAME avahi-daemon[5004]: Joining mDNS multicast group on interface veth413a681.IPv6 with address fe80::xxxx:xxxx:xxxx:dd12. Sep 7 17:27:26 MY-HOSTNAME avahi-daemon[5004]: New relevant interface veth413a681.IPv6 for mDNS. Sep 7 17:27:26 MY-HOSTNAME avahi-daemon[5004]: Registering new address record for fe80::xxxx:xxxx:xxxx:dd12 on veth413a681.*. Sep 7 17:27:27 MY-HOSTNAME kernel: veth4b32693: renamed from eth0 Sep 7 17:27:27 MY-HOSTNAME kernel: docker0: port 10(veth413a681) entered disabled state Sep 7 17:27:27 MY-HOSTNAME avahi-daemon[5004]: Interface veth413a681.IPv6 no longer relevant for mDNS. Sep 7 17:27:27 MY-HOSTNAME avahi-daemon[5004]: Leaving mDNS multicast group on interface veth413a681.IPv6 with address fe80::xxxx:xxxx:xxxx:dd12. Sep 7 17:27:27 MY-HOSTNAME kernel: docker0: port 10(veth413a681) entered disabled state Sep 7 17:27:27 MY-HOSTNAME kernel: device veth413a681 left promiscuous mode Sep 7 17:27:27 MY-HOSTNAME kernel: docker0: port 10(veth413a681) entered disabled state Sep 7 17:27:27 MY-HOSTNAME avahi-daemon[5004]: Withdrawing address record for fe80::xxxx:xxxx:xxxx:dd12 on veth413a681.
  6. Ah! Ok. Thank you, that makes sense. I will give that a shot. Edit: Setting up a user allowed the added channels to persist. Thank you!
  7. @CHBMB "Specifies default network information that will be used as placeholder values in the Connect window." If I have read this correctly, it would allow one server to be set as the autofill, but if I frequent 2-3 servers, I'd still have to manually type all the connection information for the second and third server each time I opened the webpage. Is that the best I can do?
  8. Thanks for the reply @CHBMB. Looking through the config file I see options to configure users, and an option to set the default content for the network configuration wizard, but not a way to set up a list of servers to connect to when the client is accessed. Is there another portion of the documentation that addresses this, or did I miss a section in the config file?
  9. I know that this is not supposed to act as a bouncer, but is there a way to save server configurations between sessions? Each time I connect to the web interface I have to re-add any servers I want to use. The client I am trying to move away from (Hexchat) preserves server configurations between uses. Do I have something configured incorrectly?
  10. Generating the key on another machine worked. My conf file is stock aside from the addition of the <IfModule mod_sftp.c></> section you describe in the post I quoted above (and alternate port numbers). I hope that is helpful! (If you have a moment to provide guidance on converting the keys for use with FileZilla, I'd appreciate that as well. That's my next step.)
  11. Good afternoon Slrg, I am trying to get sftp up and running on my unRAID box. I have followed the above steps, but still get the following when I attempt to start ProFTPd: /usr/local/SlrG-Common/usr/local/sbin/proftpd -c /etc/proftpd.conf 2019-02-18 22:43:37,864 Example-Server proftpd[26662]: mod_ctrls/0.9.5: error: unable to bind to local socket: Address already in use 2019-02-18 22:43:37,866 Example-Server proftpd[26662]: warning: config file '/etc/proftpd.conf' is world-writable Wrong passphrase for this key. Please try again. Wrong passphrase for this key. Please try again. Wrong passphrase for this key. Please try again. 2019-02-18 22:43:37,954 Example-Server proftpd[26662] 127.0.0.1: mod_sftp/1.0.0: error reading passphrase for SFTPHostKey '/etc/ssh/sftp_rsa_key': (unknown) 2019-02-18 22:43:37,954 Example-Server proftpd[26662] 127.0.0.1: mod_sftp/1.0.0: unable to use key in SFTPHostKey '/etc/ssh/sftp_rsa_key', exiting From a previous post of yours, it seems the bind error is expected (and netstat shows nothing using my ports), as is the world-editable warning. When creating the key I was careful to enter anything when prompted by ssh-keygen (I hit enter without typing anything). Can you provide some guidance? (I am using unRAID 6.6.6- the plugin works fine when not configured for sftp.)
  12. Ok! Question for you. I spun up the database, made monicahq database, and spun up the docker. When I launch the web interface I get the following error: Whoops! Something went wrong. The stream or file "/var/www/monica/storage/logs/laravel-2018-11-08.log" could not be opened: failed to open stream: Permission denied Back to homepage My docker config looks like this: And the Access Mode for the container path remap is "Read/Write". (I tried RW/Slave as well.) (I figured manually creating the folder might be skewing the permissions, so I tried letting the unRAID docker setup create the directory, then placing the env file in, but that didn't change anything.) Any guidance?
  13. @tjb_altf4 Thank you for your help! I will try to get this set up soon, and report back if I have any questions.
  14. Oh! Nice work! I'd love to hear about how you configured your mariahdb.
  15. Thanks for the response. The portion I am struggling with is how to implement the .env file portion of the quickstart guide: Quickstart Download a copy of MonicaHQ's example configuration file: $ curl https://raw.githubusercontent.com/monicahq/monica/master/.env.example > .env Edit it: Set APP_KEY to a random 32-character string. For example, if you have the pwgen utility installed, you could copy and paste the output of pwgen -s 32 1. Edit the MAIL_* settings to point to your own mailserver. Set DB_* settings to point to your database configuration. If you don't want to set a db prefix, be careful to set DB_PREFIX= and not DB_PREFIX='' as docker will not expand this as an empty string. Run this image: $ docker run --env-file .env -p 80:80 monicahq/monicahq I can fetch the file and prepare it, but I'm not sure how to incporate the .env file into the creation of the docker in unRAID. Where would I place the .env file such that the (as yet not created) docker can access it? How do I replicate that final 'docker run' command in my unRAID docker interface?