Move Elgg to differnt IP cron and upgrade not working
I moved my elgg installation to a different IP on the same server. The elgg data files remained in the same location and all that was need to get them to work was to change the owner.
Everything looks like it should except that now the cron jobs that were working perfectly have stopped and the upgrade from the dashboard has also stopped functioning.
Result from running cron job directly from SSH :
[ ~]# curl mydomain.com/cron/daily/
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL /cron/daily/ was not found on this server.</p>
<hr>
<address>Apache Server at mydomain.com Port 80</address>
</body></html>
Result from running upgrade in dashboard :
You must update your .htaccess file so that the path is injected into the GET parameter __elgg_uri (you can use install/config/htaccess.dist as a guide).
The location of the files did change but not in relation to the domain. Any suggestions appreciated.
Drew
- Matt Beckett@Beck24
Matt Beckett - 0 likes
- StampStudy@StampStudy
StampStudy - 0 likes
- StampStudy@StampStudy
StampStudy - 0 likes
- StampStudy@StampStudy
StampStudy - 0 likes
- Matt Beckett@Beck24
Matt Beckett - 0 likes
You must log in to post replies.Your rewrite rules are not working, sounds like you didn't move the .htaccess file with everything.
If you restore the .htaccess it will likely start working properly
Thanks Matt, I tried restoring the .htaccess from last nights backup but still no joy.
I see the following error in the log (removed identifying items)
I am new to this so reading up as much as I can. Thanks for your time.
Update :
I run Plesk 12 - I had my site working perfectly on a single IP. I add an additional IP and transferred my site across to the new IP webspace.
This stopped the update.php and cron jobs from running.
I created a fresh install of elgg on the new IP and the update and cron still refused to run. (They run if I type it in the web browser but not if I run the job through terminal). That eliminates my site but does mean something is up with the additional IP and webspace.
I then created a fresh install on the old IP under the old webspace and it works perfectly.
Both these plesk webspaces are on the same server. One is working as it should the other refuses to play ball.
I will keep tinkering.
SOLVED :
I added the new IP to the hosts file with the domain names and now all is working.
Drew
Fantastic, thanks for sharing the solution!