Error: Invalid login

[OrjanSwe]

Hi,

When upgrading to 3.8.3 there is a message "ERROR: Invalid login. This happens when I use the "Write files directly".

Have also tried manually via FTP and get Error with blank screen.

Any ideas?

Br, Örjan

[Webdongle]

...
When upgrading to 3.8.3 there is a message "ERROR: Invalid login. This happens when I use the "Write files directly".
...

What version are you updating from ?
Do you have password set for the /administrator folder (or some other security feature)
If the error came after the files wrote to the server you may need to recover by restoring your backup

...
Have also tried manually via FTP and get Error with blank screen.
...

You have almost certainly broke your site ... recover by restoring your backup



Also please viewtopic.php?f=621&t=582860

[johnnybgoodwin]

This is an error that has happened with previous updates to Joomla! - easy to find on the web. I am also having the same problem upgrading from 3.8.2 to 3.8.3 - An error is returned, "Invalid Login"
The site is not broken, it works okay. I changed the php version from 5.6 to 7 - doesn't make any difference. Error still happens. Upgrade does not.

[sozzled]

When upgrading to 3.8.3 there is a message "ERROR: Invalid login".

Usually indicates the presence of enabling the FTP Layer in the Global Configuration settings. If you have enabled the FTP layer, suggest you disable it (or, at the very least, ask yourself the question why you enabled this setting in the first place).

Recheck the FTP user credentials for this website.

[johnnybgoodwin]

Fixed this now:
I discovered a problem with the hosting account and a possible site hack which has caused the site to exceed storage quota. Now that the site is not over quota the update works.


[ "Usually indicates the presence of enabling the FTP Layer in the Global Configuration settings."
- I don't use ftp on any Joomla! site - seems like it's been trouble since it was introduced!

Thanks for the response.]

[evansnp]

Any updates on this?

[johnnybgoodwin]

In my case it was only because the hosting account was over quota. Reducing the space used up in the hosting account allowed the update to work fine.
(The overage was caused by an ever increasing error log file - deleted the error log, about 2 gig, and gained plenty of space for the process).