"Access Denied" and Permissions errors
Permalink 1 user found helpful
Hello All,
I've recently pushed a C5 site from a development server to a live server. On the development server I and my client had no problems editing pages, adding content, etc. However, since moving to the live server, we are constantly running into "Access Denied" errors when trying to delete blocks, and the attached error when trying to edit blocks. I think these errors are related to the fact that logins don't stick. I get kicked out when I receive the attached error. I get kicked out when I try to access any of the submenu options under the gear (Versions, Design, etc). I can access the dashboard pages. I notice that they use "index.php" even though my site is set to use pretty URLs. (I am using the root admin login.)
I've checked the permissions on files and folders and they are correctly 644 and 755, respectively. The files and folders are also correctly owned by the server. I moved the database back to the development site so I could make changes, and had no problem. Made changes, reuploaded the database to the production site -- changes were reflected, of course, but still all the errors.
Any suggestions?
I've recently pushed a C5 site from a development server to a live server. On the development server I and my client had no problems editing pages, adding content, etc. However, since moving to the live server, we are constantly running into "Access Denied" errors when trying to delete blocks, and the attached error when trying to edit blocks. I think these errors are related to the fact that logins don't stick. I get kicked out when I receive the attached error. I get kicked out when I try to access any of the submenu options under the gear (Versions, Design, etc). I can access the dashboard pages. I notice that they use "index.php" even though my site is set to use pretty URLs. (I am using the root admin login.)
I've checked the permissions on files and folders and they are correctly 644 and 755, respectively. The files and folders are also correctly owned by the server. I moved the database back to the development site so I could make changes, and had no problem. Made changes, reuploaded the database to the production site -- changes were reflected, of course, but still all the errors.
Any suggestions?
Does your live site use some sort of caching like Varnish? I've seen similar issues when that is the case.
There is no caching, server-side or otherwise. I did have Concrete5's built in caching turned on, but I've turned it off in hopes to resolve these issues -- no luck so far.
Hi digitalrainstorm,
Are you or your client connecting to the site using a VPN, mobile internet connection, or some other type of connection that would change your IP during your concrete5 editing session?
Are you or your client connecting to the site using a VPN, mobile internet connection, or some other type of connection that would change your IP during your concrete5 editing session?
My clients do use a VPN. I and my colleagues, however, do not, and we're having all the same problems. When the site was in the development environment, my clients used the VPN with no problem.
The development environment was on the web host A Small Orange, and the production environment is on Media Temple. Anyone have any experience with Concrete5 on Media Temple? Could this be the issue?
The development environment was on the web host A Small Orange, and the production environment is on Media Temple. Anyone have any experience with Concrete5 on Media Temple? Could this be the issue?
It could be that your server is using the new 'Litespeed Cache' and if so you will probably not find an on/off switch for it in the servers control panel.
To disable the Litespeed Cache on a server add this line to the top of your htaccess file
To disable the Litespeed Cache on a server add this line to the top of your htaccess file
RewriteEngine On RewriteRule (.*) - [E=Cache-Control:no-cache]
There is no caching at all, so sayeth Media Temple support.
I just changed the PHP version from 5.6.21 to 7.0.6 and was able to actually make some changes. We'll see if it sticks.
I just changed the PHP version from 5.6.21 to 7.0.6 and was able to actually make some changes. We'll see if it sticks.
