Thread

I’ve got a client reporting that they’re getting this:

-The following errors were encountered
“You are not authorized to perform this action”

but only from certain networks, e.g. one of the laptop users at the place of work gets the above message when she tries to login from the office. She takes the same laptop home and tries on her home connection and gets in fine.

Another external consultant uses a wireless USB modem when she’s on the road and gets the error and when they go home and uses the same laptop on their home network, it logs in fine.

😖

And it seems that another client has the same trouble editing all of his EE sites when tethering his laptop to his mobile.

What method of authentication are you using? Try not to use session_ids. There are some other options that you can try, too, like not requiring IP addresses and the like.

Changing to cookies only works for the client tethering from his laptop, but I’ve tried setting to cookies only and setting Require IP Address and User Agent for Login to ‘no’ and still getting the same problem for the client mentioned in the opening post.

Are they behind a firewall?

Apparently not.

Is there anyone in their office able to login?

No.

Try adding this to your config.php

$config['cookie_domain'] = ".example.com";
$config['cookie_path'] = "";
$config['cookie_prefix'] = "";
$config['admin_session_type'] = "c";
$config['user_session_type'] = "c";
$config['require_ip_for_login'] = "n";
$config['require_ip_for_posting'] = "n"; 
$config['secure_forms'] = "n";

Be sure to change example.com to your domain.

Yep did that but still getting the problem. A bit more info:

The site also has a login to a restricted area from the front end which is also causing some troubles logging in.

- When logging in at their office as a superadmin, could log into the CMS but not the restricted area (unless i was already logged in via the CMS).
- Could not log in via editor login to either restricted area or CMS.
- Changed editor login to a superadmin and could log into the CMS but not the restricted area.
- Could then see the restricted area once logged into the CMS.

This only happens in their office. Logging into either CMS or restricted area with either editor or superadmin login works fine at my end and at the end of the client that I did the site for (i.e. the actual users of the site are clients of another agency that I did the work for).

Actually, something that’s just occurred to me: should that be $config[] or $conf[]?

Good catch, for EE1 it’s $conf[], $config[] being EE2 syntax.