Jump to content

Search the Community

Showing results for tags 'reverse proxy'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Essentials
    • Announcements
  • Passwordstate 9.x
    • General Support
    • General Hints and Tips
    • Known Issues
    • Installing Passwordstate
    • Feature Requests
    • Feature Requests - Completed
    • 3rd Party Hardware/Software Knowledge Forum
  • Knowledge Base
    • General FAQs
    • Password Resets
    • Remote Session Launcher
    • App Server
    • Passwordstate API
    • Browser Extensions
    • Password Reset Portal
  • Passwordstate 8.x
    • General Support
    • Feature Requests - Completed

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Google Plus Account


Location


Interests


Biography


Location


Interests


Occupation

Found 2 results

  1. 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
  2. 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.
×
×
  • Create New...