2S119/1 Sorry, you do not have permission for that!

[sg2013]

Hi,

My site is throwing this error up when I try to sign in, seems a fairly new issue and nothing has changed since I could login. I've done some searching and support advised to clear cache which I've tried, as well as other browsers. I can't login to the admin site to clear the forum cache.

Can someone advise what I need to do?

 

Thanks,

 

 

[Marc]

First thing I would advise here is upgrading. Upload a fresh set of files, and upgrade to the latest release, You appear at present to be over 40 releases behind

[sg2013]

That is what I want to do! I just renewed so I could, was going to sign in to the admin section and upgrade but can't...

[Marc]

You could not upgrade from the admin CP as the latest release requires PHP 8 and your current version will not support PHP 8. You need to upload a fresh set of files, and run the upgrader from /admin/upgrade

[sg2013]

thanks, I will try this.

[sg2013]

Update complete and same issue after clearing cache etc.

 

I can login as a user now, but admin area still the same

Edited December 21, 2022 by sg2013

[Jim M]

Could you please let us know what you're attempting to access in the ACP? Please also let us know your display name so we can review what is happening.

[sg2013]

I'm just trying to sign in at: /forum/admin/

I'm PM'd you my login name

 

thanks

[Marc]

You will need to update these details within your client area, rather than sending details to individuals via the PM system

[sg2013]

Maybe that should have been asked 😉

Right, I have updated those details to my own login.

 

thanks

 

[Marc]

1 hour ago, sg2013 said:

Maybe that should have been asked 😉

A little confused there. That is indeed what I just asked LOL. Im not sure anyone asked for any details at all above other than to know your display name so we could check permissions 😄

Never send credentials any other way than in the secure client area 🙂

 

I would suggest clearing your browser cache, and ensuring you are only visiting /admin/ (ensure you dont have anything after that stored in a bookmark for example). I am logged in as yourself with no issues at all.

[sg2013]

That comment was to Jim's post.

 

I've cleared cache many times, used browsers that I don't use (so no cache) and failed every time, until just now, it works. I even tried different computers. Very strange.

Thank you, I am in now 🙂

 

 

[Marc]

No problem. Glad you are in 🙂

[sg2013]

IT now happens logging in as a normal user, obvsiously cache cleared, using forum/login/, "Something went wrong. Please try again."

But I can login to admin with the same credentials.

 

[Marc]

Are you using any caching on the server at all?

Also, we would need to know who

 

[sg2013]

Have changed the password

Just now, Marc Stridgen said:

Are you using any caching on the server at all?

Also, we would need to know who

 

The host provides LiteSpeed, I have also flushed that cache many times

[Marc]

Please disable that cache entirely while we are taking a look at this. Especially as cached items seem to be having an impact

[sg2013]

I've never heard of it, it seems it only runs on plugins for apps like WP etc. so I don't think it's on the forum

But, I've added

RewriteEngine On
RewriteRule .* - [E=Cache-Control:no-cache]

to .htaccess and will try again later once it's disabled fully

 

Edited December 22, 2022 by sg2013

[Marc]

No problem. Please let us know how you get on

[sg2013]

well issue resolved, I think.

Basically it was the parameter for the site in conf_global was set to http, not https. It is strange that I could login to admin on FF, but not the forum, but on chrome I could log into both.

Never been an issue before, but I started getting warnings about it not being secure, so something has changed, be it browser, update etc.

Thanks for your help, think we're sorted!

[Marc]

If your server was forcing https and it was set http in your configuration, that would indeed cause you problems. I must admit, Im surprised you were ever able to log in. In any case, glad you got the issue sorted