• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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