lococola

I just updated Privoxyvpn to the latest version, but now my Soulseek container that I'm running through Privoxy can't connect any longer. EDIT: Solved. There was some issue with certificates on the side of AirVPN. Fixed it by renewing the cert from the Airvpn client area, then generating a new ovpn file and placing that in PrivoxyVPN's config folder, replacing the old file. Everything now working again.

I'm still on 6.8.3. I would like to upgrade to 6.9.2. How can I do this? From Unraid I can only select 6.10.

You're right. Adding the set_real_ip lines to the advanced config fixed the issue for me. Strange that it somehow managed to work for several months without it. Still, working again now. Thanks for the help!

Like so: This is what I have in my access list: If I set the Proxy Host to not use this access list, so setting it to Publicly Accessible, then I can reach my vault just fine through the domain, and also login to it without issues. So the problem is somewhere in the access list, but I can't figure out how.

I have vaultwarden running through a reverse proxy that I set up with NGINX Proxy Manager. This used to work fine but suddenly since today I'm getting 403 errors with the reverse proxy. In NGINX I have an access list configured that allows only my external IP and my internal LAN, it denies everything else. This used to work fine. But now I am getting 403 errors when this access list is used. If I set the proxy host to Public Access, everything is fine. I don't know what could cause the access list to suddenly not work any more. I am using Cloudflare and I did set the custom config real_ip_header CF-Connecting-IP; in the advanced settings of the proxy host. HTTP/2 support is disabled. Any ideas what could be the issue? I updated NGinx to the latest version. Is the some log that I can check?

I found I couldn't login anymore, no idea why. So I reset my password according to this procedure from github. But now I lost my entire configuration! Everywhere I go it says "owner is null". Do I have to set it up again from scratch or can this be fixed somehow? edit: and now I can't login anymore... fantastic

n/m

Is it possible to enable the recycle bin just for a single share or folder? Right now it's enabled for every share by default, but I have a lot of shares and there appears to be a limit on the amount of exclusions you can add.

n/m

I also do not receive actual mails. However, after sending the invitation I was able to create an account for that e-mail address by simply going to the login page and clicking the Create Account button. I found that the process would actually work for the e-mail address that I sent an invite to. So just try it out

I set up NGinx Proxy Manager combined with Cloudflare and a domain for the Bitwarden docker. It all works, but I had to forward port 80 and 443 in my router. Now, it seems anyone can access the bitwarden login page from my docker from the internet. I did disable the admin page access using the tip from this thread. But the fact that you can just type my bitwarden.mydomain.com address and get to the login screen worries me. I really only need this to be accessible from within my LAN. Is it possible to somehow hide this page for any WAN access? How do you guys do it? Just accept that the login page is visible to the world? EDIT: Looks like I was able to make it a little bit more secure using NGinx proxy manager Access Lists. At first I couldn't get the ACL to work. I added the external IP of my router to the ACL, but I kept seeing 403 errors. And I did save the proxy host config each time again also. The thing that finally fixed it for me was adding the following code to the proxy host advanced config: real_ip_header CF-Connecting-IP; Now the login page is only visible from my own IP address, and gives a 403 error from any other IP. Makes me feel a little bit more secure

Thanks. I've read through that post and I learned some new things about the behavior of Windows regarding authentication and caching. But in my case, I don't want my main Windows user account to have access to the private share. What I want is to always have a login prompt appear when trying to access that particular share. Only with the correct username/password you can get in. This was working nicely (albeit with a workaround) before by approaching the share using the IP address instead of the hostname. But after the KB5003173 update that stopped working.

So, I have a hidden private share on my Unraid server that I am able to access on my Windows 10 machine by manually typing the ip address and path, and then entering the username/password that I setup for that share. Yesterday Windows update KB5003173 was installed on my Windows 10 machine. The Unraid share now cannot be accessed any more from that computer. Other public shares on the Unraid server are still accessible. But not the private share. I figured it might be an SMB 1.0 thing. In the Unraid settings I changed the SMB option "Enable Netbios" to No, which should disable SMB 1.0. But the private share is still not accessible. Then I reverted the KB5003173 update on my Windows 10 computer and after this the private share can again be accessed. Anyone else run into this? Is there a solution other than not installing the Windows security update?

Drive: WD80EZAZ-11TDBA0 Power on hours: 7385 (10m, 2d, 17h) Load Cycle Count: 9311 Unraid is set to never spin down the drive, and in the drive properties spin-down is set to default (so, never). Shouldn't the LCC be a factor 10 lower than what it currently is?

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.