Search the Community
Showing results for tags 'reverse proxy'.
Found 4 results
Issue: We've had a couple of instances where customers were attempting to add a password into a Password List, but when saving the password nothing happens. This can also happen when clicking on a Password Record. Resolution: Upon inspecting the developer tools in the browser, it was determined that when clicking the save button, or when trying to open a Password Record, and Error 413 was being thrown: This error means: “The server is refusing to process a request because the request payload is larger than the server is willing or able to process.” To fix this, the customer added a line to the Nginx configuration file that read “client_max_body_size #MB”, where # = max MB request size. Typically setting this value to 4mb should be suffice, and the default is 1mb. Regards, Support
A user has reported an issue with the browser based launcher, where after establishing either a RDP of SSH session, the tab that the session is in seems to close unexpectedly. This happens at around the 2 minute mark into the session. The customer came back to us for a fix for this, which I've quoted below. Thanks to our customer who provided this feedback, if you are reading this:) The issue with the remote session launcher closing after a few minutes of inactivity was reverse proxy related. We are using NGINX as a reverse proxy. Since your browser-based remote sessions use WSS, an upgrade instruction was needed to get the launcher working (proxy_set_header Upgrade $http_upgrade). After that, remote sessions worked, but they would close after a short period of inactivity. This timeout has been increased with the (proxy_read_timeout) instruction. These two config lines will be needed if users would like to use browser-based remote sessions with an NGINX reverse proxy successfully. Everything works great now. Regards, Support.
Hi, I'm a happy home user of Passwordstate (PWS), and so far the experience has been very nice. I've exposed my PWS to the internet through the use of an Apache reverse proxy, and that works great. Before I did that, I of course made sure I had 2FA enabled for my user, as only using username and password seemed far too dangerous. This has worked perfectly, but, I've been a bit annoyed by the fact that I needed to use 2FA even when I access my PWS from home. So, reading a bit about it lead me to the Administration -> System Settings -> allowed ip ranges -> Web Site Allowed IP Ranges setting, where I've added my internal network range, and set Authentication Option to Forms and Google Authenticator I've also made sure to specify my Apache reverse proxy IP in Administration -> System Settings -> proxy & syslog servers -> X-Forwarded-For Support. My user account is set to use Use the System Wide Authentication Settings under Web Authentication Option. The Apache reverse proxy is set up to use RemoteIPHeader X-Forwarded-For in the configuration for my PWS site. I can also see my real, remote client IP in the IIS logs after adding the X-Forwarded-For column to the logging options in IIS, so I know it gets through. Signing in to PWS from home works fine, with just username and password now. However, signing in from remote still only requires username and password. I'd like remote sign in to require 2FA. I'm sure I'm missing something, but I can't really see what. Any help would be greatly appreciated. Thank you!
Hi guys, I'm trying to get passwordstate to work externally from behind a nginx reverse proxy but am having some issues. Nginx is successfully passing the request and assigning the ssl certificate but I'm getting the following error. I've added pass.domain.com with port 80 and 443 to the iis bindings and as a hostname to password state but I'm still getting the same error. There doesn't seem to be much documentation about the error in my searching from google or the forums so any help would be greatly appreciated. Thanks, James