action/login 404 error
This is a new problem with the update from 1.6.1 to 1.6.3. When I attempt to log in from the main page, the server returns a 404 error: "The server can not find the requested page: mysite.com/action/login.php (port 443)"
The login.php file is definitely intact in the actions folder. What gives?
I do have vazco_topbar installed, which has its own login box -- still working. I'm reluctant to disable it to check for conflicts, because that might leave me with no way to log into the site!
Elgg Technical Support
Get support from other Elgg users
- iionly@iionly
iionly - 0 likes
- Cash@costelloc
Cash - 0 likes
- julie levin russo@openid_377574
julie levin russo - 0 likes
- Cash@costelloc
Cash - 0 likes
- julie levin russo@openid_377574
julie levin russo - 0 likes
- natedlee@miershpedankl
natedlee - 0 likes
- natedlee@miershpedankl
natedlee - 0 likes
- fathomboy@owner
fathomboy - 0 likes
- iionly@iionly
iionly - 0 likes
You must log in to post replies.I don't know if there were any changes in .htaccess between 1.6.1 and 1.6.3. Have you checked if you have to replace .htaccess?
That would indicate an issue with the .htaccess or a server configuration problem (mod rewrite not turned on or htaccess not being processed)
When I updated I used 1.6.3 .htaccess but checked carefully to make sure I copied over important settings. I don't see any inadvertent changes in modrewrite that would cause this. Wouldn't a rewrite problem affect more pages in the site and not just login?
Yes it would.
Have you changed the SSL (https) setup of your server recently? The login is going against a https page. You could try turning off https login for the site.
Yes! I'm not sure if 1.6.3 changed https, it got turned on accidentally in the update, or something changed coincidentally on the back end -- but with https login unchecked it works fine.
Thanks so much, you're a huge help.
I have encountered the same problem, but I can no longer login to the site. What file do I need to fix on the server-side to re-enable login? I am on the latest version.
Found the answer under Adminstrator FAQs.
This error has recurred AGAIN in the latest update help please...
@fathomboy: which version have you updated from? Have you replaced the content of .htaccess with the content of htaccess_dist (while keeping any changes you might have made yourself)?