Support

Site Restoration

#25417 "WARNING !!! Your database password contains special characters.

Posted in ‘Site restoration’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

PHP version
n/a
CMS Type
Other
CMS Version
n/a
Backup Tool Version
n/a
Kickstart version
n/a

Latest post by nicholas on Tuesday, 21 June 2016 03:53 CDT

user13134
On processing updated restoration site using Akeeba Angie (unpacked zip file) I got this WARNING !!! message.
What are the implications and is it safe/preferred to make these changes?
By this I mean: Will changing DB password as requested in any way affect other site functions or access

Kind Regards,
Nev Sagiba

"WARNING !!!

Your database password contains special characters. Many web servers reject or modify these passwords, causing the database restoration to fail with a database connection error.

We VERY STRONGLY recommend that you change your database password to a long (32 characters or longer) random string consisting of ONLY uppercase letters A-Z, lowercase letters a-z and numbers 0-9.

Do you want to ignore the warning and proceed with the database restoration at your own risk?"

user13134
I just found this: https://www.akeebabackup.com/documentation/troubleshooter/abidatabase.html

Will make an entirely new Database.

I'm concerned about the Tables changing causing issues (I think that was in the back of my mind)

I'll run with it and see what comes of it and if neccessary start ove.

I will appreciate your feedback.

Regards,

user13134
Curiously: Just found there are NO special characters in my DB name but complies with "random string consisting of ONLY uppercase letters A-Z, lowercase letters a-z and numbers 0-9"

Hence WHY the warning?

nicholas
Akeeba Staff
Manager
When you are typing in a database password that contains anything other than a to z, A to Z and 0 to 9 you get the warning. It's not a problem and you should be able to restore your site on 99% of the cases. The other 1% is when the server itself blocks any request with certain combinations of special characters and letters because of overly ambitious anti-hacker protection. We issue that warning to draw your attention to the fact that if your server does belong to that 1% and the restoration does fail it's not our fault and we can't do anything about it except ask you to either contact your host about it or use a database password that does not include the special characters / potentially problematic patterns.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user13134
Hi Nicholas,

Thanks for the prompt reply.

Is it OK I make a new Database?

Will this change the Table name.

Is this safe?

I recall reading a caution about altering table names.

Should I use the existing Table name?

Or is it OK if it changes?

Will appreciate any clarification..

Many thanks!

user13134
Should I use the old/existing Table name if it changes when I change the DB name?

user13134
I'm probably not making much sense but my mind is in hyperdrive.

eg

At https://www.akeebabackup.com/documentation/troubleshooter/abidatabase.html

This stood out:" As a rule of thumb: always create a database before restoring your site."

On this basis I'm wondering whether to or not since I'm loading to the same host, same folder.

The the worry about Tables changing came up. As I don't totally understand it I'm pausing to avoid creating a problem.

I'm very close to promised launch so I don't want to create issues that could affect subscribers otherwise I would dive in ands learn from mistakes if any.

Thanks!

nicholas
Akeeba Staff
Manager
You do not need to create a new database. Doing so is not bad, it's just NOT necessary.

Table names and the database name are not linked to each other. The table names will NOT change. The table name prefix will also NOT change unless you manually change it. Changing it is SAFE. If it wasn't we wouldn't let you do it.

As I said above, just go through the restoration. ONLY IF DATABASE RESTORATION FAILS should you even consider changing the password of the database user. Everything else you wrote are irrelevant and NOT, REPEAT: NOT, what I told you to do.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!