403 problems after transfer
Permalink
I have a site I've transferred, and after transferring there are problems. Yes I've edited the site.php and the .htaccess.
The site actually works, sort of - with no css. It will pull in files like pictures no problem, but the css won't load. If I View Source and click the link to the css, I get a 403 forbidden error.
If I try to go to the dashboard, I do get the full login page, oddly enough with css and all. However I get 403 forbidden when I log in, so I can't get to the dashboard.
I chmod'd the Files directory to 777, no change.
The odd part is I've transferred C5 sites from the old host to this one before with no problems, using the same method.
Anyway, are there other directories that maybe need to be 777'd? Never had to before, but maybe the web host made changes recently.
The site actually works, sort of - with no css. It will pull in files like pictures no problem, but the css won't load. If I View Source and click the link to the css, I get a 403 forbidden error.
If I try to go to the dashboard, I do get the full login page, oddly enough with css and all. However I get 403 forbidden when I log in, so I can't get to the dashboard.
I chmod'd the Files directory to 777, no change.
The odd part is I've transferred C5 sites from the old host to this one before with no problems, using the same method.
Anyway, are there other directories that maybe need to be 777'd? Never had to before, but maybe the web host made changes recently.
This was the situation:
- live site on server1 with domain.com pointing to it (eg mydomain.com)
- new c5 site on server2, available at temporary URL ( eg server2.com/~myaccount )
- new site was not working properly, throwing 403 errors and not loading files with "index.php" in the URL
To show the new site *before* pointing the domain to server2:
- set up a subdomain on server 2 (eg dev.mydomain.com) in your server control panel (eg cPanel)
- on server1 (or wherever mydomain.com's DNS is hosted) set up an A record for the subdomain you just set up on server2 (eg dev.mydomain.com) to point to the IP address of server2
- make sure to update your Concrete5 site/config.php file on server2 with the appropriate details
- now you can test your dev site on a new server
Of course you'll need to change mydomain.com and server2.com, etc to match your actual domain and server addresses!
Hope that helps someone!
- live site on server1 with domain.com pointing to it (eg mydomain.com)
- new c5 site on server2, available at temporary URL ( eg server2.com/~myaccount )
- new site was not working properly, throwing 403 errors and not loading files with "index.php" in the URL
To show the new site *before* pointing the domain to server2:
- set up a subdomain on server 2 (eg dev.mydomain.com) in your server control panel (eg cPanel)
- on server1 (or wherever mydomain.com's DNS is hosted) set up an A record for the subdomain you just set up on server2 (eg dev.mydomain.com) to point to the IP address of server2
- make sure to update your Concrete5 site/config.php file on server2 with the appropriate details
- now you can test your dev site on a new server
Of course you'll need to change mydomain.com and server2.com, etc to match your actual domain and server addresses!
Hope that helps someone!
I'm getting 403 forbidden on css files on a new install.
This is a new host for me (MDD... sound familiar? :-)
The host is trying to say I shouldn't use a "temporary URL" (eg server.host.com/~myaccount/ )... which I've done many times before.