Password protected folder doesn't show login box in Google Chrome

[Ian Grant]

Hi, all.

As a matter of course, we use Plesk to password-protect working sites until they're ready for launch. And that works fine in most instances: in IE and FF, for example, you get the usual dialog box asking for a username and password, with an error message if you enter the wrong details.

But if you visit one of these sites in Google Chrome, you just get the 401.1 "You are not authorized to view this page" error message, without any dialog box to enter your credentials. Which means that you can't see the site at all.

Is there some way of getting around that? While we can just ask clients to use a different browser, it'd be nice if they didn't have to do that.

Any help will be gratefully received.

Many thanks,

ian.

 

[IgorG]

According http://www.parallels.com/products/plesk82/reqs/ Google Chrome is not supported browser for Plesk 8.2.0

 

[Ian Grant]

Thanks for your reply; your help is much appreciated.

I can understand that the Plesk interface itself doesn't support Google Chrome...but that doesn't mean that sites created and configured with Plesk 8.2 won't work on unsupported browsers, does it? If it does, that's a massive issue: there's clearly no way of guaranteeing which browsers are visiting your sites and no viable way of imposing those restrictions (even if you wanted to).

To clarify, the problem isn't that I can't password protect the site folder, but that visiting the address yields only a 401 error rather than a login box in Chrome.

Many thanks.

 

[IgorG]

Ian,

You cannot create sites by Plesk. Plesk is a solution for a hosting, but not for creation of sites. SiteBuilder is used for this purpose. Do you mean that you can't use Chrome for sites which were created by SiteBuilder?

 

[Ian Grant]

Thanks for your reply, Igor, and apologies if I'm not explaining the problem very clearly.

There is absolutely no problem with the site itself. The problem is only with password-protecting that site using the facilities within Plesk. If I do that, anyone who visits the site using Google Chrome sees a 401 error message without any login option; in other words, they can't access the site at all because they can't get past the password protection.

If that is because Plesk 8.2 doesn't support Google Chrome, then I suppose that's something we'll have to live with. But obviously, we have no control over which browser is used to access our sites...and we have no way of telling those users to try another browser. In other words, if a hosting system means that sites don't work in certain browsers, that's a bit of a flaw in the system!

 

[IgorG]

Ian,

Ok, I see. I think that really, problem related to fact that password-protection functionality for sites is provided by Plesk engine. And if Chrome is not supported by this Plesk version we can wait that it will not work correctly too.

 

[Ian Grant]

Thanks for your help, Igor. Even if we can't fix it, we do at least have a better idea of what the problem is. Much appreciated.