• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue nginx + password protected directory = odd behavior

larryk

Regular Pleskian
hello,

situation:
I had old plesk and apache before upgrading to onyx and going to nginx.

a client goes to domain.com/admin/index.html (admin is password protected)

BEFORE upgrade, the client must enter user/pass to SEE the index.html page
AFTER upgrade, the client can 'see' the index.html and ONLY is prompted to enter user/pass AFTER they click a link on the index.html page

strange right? how is that happening?

It does not happen to me. client and I are both using chrome.
thoughts?

NOTE: I'm seeing nginx 401 error codes in the logs, EVEN THOUGH the client may or may NOT see the error page (unauthorized access) in the browser.

anyone got any ideas on how this might be occurring?

THanks!

PS. if anyone following my post, this is same client with 499 codes :(
i wonder if this is somehow related?

PSS. this client has proxy turned off. I'm thinking of testing, turning on (checking the box) proxy to see if these odd things go away?
 
Back
Top