Jump to content

lococola

Members
  • Content Count

    16
  • Joined

  • Last visited

Community Reputation

0 Neutral

About lococola

  • Rank
    Member

Recent Profile Visitors

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

  1. I appreciate your help. But it's getting really confusing. I think a reverse proxy is not the solution for me if I don't want to open any ports in my router. So I will start from scratch again and see if I can get Bitwarden to work with some form of self signed certificate. I saw mention of Caddy, perhaps that works better for me. Thanks again though.
  2. Interesting. How would I go about setting that up?
  3. It's confusing. I mean, Is port 443 needed for Letsencrypt, or for Bitwarden? I verify Letsencrypt over DNS and I don't have to have any ports open in my router for that. If it is Bitwarden that needs to go online over port 443, then what for? What is surprising to me is that once you have set up Bitwarden over the reverse proxy, anyone can access the login page if they know the url. Sure, they have to crack the password and then circumvent the 2FA, so it's safe enough. But still, I really don't like the thought of having my password manager available through the internet like that. I'm frankly surprised nobody else seems to have an issue with this. I will check out if I can get Bitwarden to work with a self signed cert. Since the app does not need to be accessed over WAN it should be secure enough. *If* it works...
  4. So I installed Bitwarden RS on my Unraid server. I only want to access it from within the LAN. I also do not want to open any ports in my router. Unfortunately it appears this is not possible. It turns out I can't create a user account if Bitwarden is not on HTTPS. Fine. So I go through the whole work of setting up a reverse proxy, getting duckdns, and buying a domain (only a few bucks anyway). I spent all day setting it up and getting it all connected. Also I had to get Letsencrypt to verify over DNS since my ISP is blocking port 80 (took me half a day before I figured out this was a thing). In the end, it all works. I can access Bitwarden through my domain, I can create an account etc. However, it only works with port 443 forwarded in my router to Unraid's port 1443. If I disable port forwarding in the router, Bitwarden is not accessible. Now, to me it seems kind of ridiculous that I have to go over the WAN in order to access a locally hosted server. I mean, I am running local, and Bitwarden is local. There must be some more efficient way to connect than via the internet... I am guessing I am probably missing some obvious setting or feature? Is there anyone who can shed some light on this? A reverse proxy may be nice to have for future apps, but in this situation all I wanna do is access Bitwarden locally (and securely). I have extensively searched this forum (and the rest of the internet) but information on this particular thing is scarce. It appears everybody really likes to access Bitwarden from the other side of the world for some reason...
  5. Well, I got it running with the proper GUID and GPID now. Unfortunately I still have the issue of Soulseek not writing the client data, so whenever I restart the docker I lose all my settings. I have set the option to 1 minute, but to no avail. Could it be a permissions issue? This is how I set up my paths in the Docker settings: Which user:group should I set the /mnt/cache/appdata/soulseek/ folder and subfolders to? root:root, or nobody:users? I tried both but it won't save the client data...
  6. I want to run this on my Unraid server. Do I need to run this through a VPN? Or a reverse proxy? Or both?
  7. I feel like a total nitwit, but I can't get this to work. I installed MariaDB with default settings. Then I installed Wordpress with default settings. Then when I open the WP webgui, I get "Error establishing a database connection". What do I need to do to get this working? I know how to install Wordpress itself, I'm just not seeing the initial WP setup screen. Never mind, fixed it. I needed to set the path to the MariaDB with the right port in the WP docker settings. Working now!
  8. Very cool plugin! Been playing around with it. One question. When you hover a menu item there appears this little colored underline. How can you change the color of this underline? I tried to find out the object using Chrome Inspector, but I haven't been succesfull. Very strange!
  9. I want to use a script to run a rsync command, but I also want to run this from a screen, so I can check the progress at any time with screen -r. I have several backup scripts for each share that I want to backup. I'm having some issue getting screen to work. This is how the script looks now: #!/bin/bash export SCREENDIR=/root/.screen screen -dmS rsyncdms echo "Job '[job name]' started" rsync [with parameters etc] /usr/local/emhttp/webGui/scripts/notify -s "Job '[job name]' finished at $(date '+%Y-%m-%d %H:%M')" So it needs to do 3 things (echo, rsync and notify). When I run the script from the User Scripts page with the Run Script button, it works perfectly. But when I run it in the background and then try to view the status with 'screen -r' in a terminal, I just get a blank terminal with a prompt. I read it's because you need to put something immediately behind the 'screen -dmS rsyncdms' command, but then it still doesn't work. How can I get these 3 things to be executed in order, all within its own screen session? I saw another post where someone made a new user script and within it called the .sh file, but I want to integrate the screen function within the backup script itself, if possible.
  10. Yep, that was it. I ran rsync with -v and then I could see it didn't even attempt my custom named key, only the rsa_id ones. Naming the key accordingly fixed it.
  11. I've been trying to get this work but no matter what I do, every time I ssh it keeps asking for a password. Here is what I do, perhaps I'm missing something. I have an Unraid server (192.168.1.159) and a Synology DS411j (192.168.1.9). On the Unraid server, I run ssh-keygen -t rsa and give it the name "unraidkey". When it asks for a passphrase I just hit enter. It generates a private and public key file. They are in the following location on the Unraid server. ~/root/.ssh. On the Synology I created the user "fsync", made it a member of the administrators group. I also enabled the Homes service. SSH was already enabled. And I uncommented the required lines from the SSHD config file and restarted SSH. Now I copy the public key from the Unraid server to the Synology with the command: ssh-copy-id -i unraidkey fsync@192.168.1.9 Back to the Synology. I made sure the chmod permissions are set as described: chmod 700 on .ssh/ and 644 on .ssh/authorized_keys. According to the description I should be able to connect to the Synology from the Unraid without password. But when I SSH from the Unraid terminal to fsync@192.168.1.9 it keeps asking for a password. What could I be doing wrong?
  12. The easy of use combined with the many options and detailed system information make you feel like the master of your domain that you are. As for improving things I would like to see even more options for showing and hiding information on every section of the Unraid pages.
  13. Haha wow, I was so mixed up in my head with all the access rights and settings that this never occurred to me... Yeah that makes total sense. But now I at least know how to take care of this. Thanks for making sense
  14. I'm trying to configure a combination of shares and users that I think may not be possible, but I would like to double-check it here anyway. This is how I would like it to be: Share 1-5: Guests have Read-Only access; User1 account has Read/Write access; User2 account has No access. Share 6: Guests have No access; User1 account has No access; User2 account has Read/Write access. I can set it up almost 100% like above, except... I can't set the access rights for User2 on Share 1-5 to "No access". The option is simply not there, it has Read-Only access by default. I guess that is because I set up the shares with the options Export: Yes and Security: Secure? If I set the security to Private then I can set User2 to "No access", but then Guest users also have no access. Is there any workaround for this? Basically all I want to accomplish is to have 1 specific share that is only accessible for 1 specific user, but to also lock that user to that share. So it should not be able to even see the other shares.