The DB password was recently change for a website I'm working on (for reasons I won't get into). As such, Joomla is no longer able to connect to the DB, prompting the error message: Database connection error (2): Could not connect to MySQL.
Fortunately, I do know that I need to simply update the password in the configuration.php file to use the new password, but all of my attempts at making the change have failed. For security reasons I'm sure, I am completely unable to upload my modified configuration.php file. Normally I'd be happy to hear that the configuration file can't be modified, but in this one instance I need to modify it.
How would I go about modifying the file?
You options would be:
Upload new configuration.php via FTP file with new DB password value, however as you mentioned, you're unable to upload it.
Login to your hosting control panel and upload the configuration.php file via the built-in File Manager
Login to and change the password back to it's original value
Get in contact with your hosting provider and find out as to why you're unable to upload the config file.
One of the above options should work, however if all else fails, your last resort will be to contact the person who changed the DB password and ask them to change it back.
Being unable to upload / modify the configuration file, smells like a permissions issue. Maybe the file has permissions set to 444. Many FTP clients allow manipulation of the file permissions. You can set them to 644 for the config. file and then save it. If you can't do this through the FTP client, then try it within the cPanel.
Related
So, I changed my FTP password from my hosting panel.
And I've no idea what the old password was.
And now my website displays "Access denied." on every page.
It's a Joomla website.
Thank you for your help !
Edit: When I try to login on the admnistrator page, here is what I get :
Warning: include_once(/home/clients/6a0b43a5add26c536570d4cb7062e046/web/libraries/fof/config/provider.php): failed to open stream: Permission denied in /home/clients/6a0b43a5add26c536570d4cb7062e046/web/libraries/fof/autoloader/fof.php on line 87
Warning: include_once(): Failed opening '/home/clients/6a0b43a5add26c536570d4cb7062e046/web/libraries/fof/config/provider.php' for inclusion (include_path='.:/opt/php5.6/lib/php') in /home/clients/6a0b43a5add26c536570d4cb7062e046/web/libraries/fof/autoloader/fof.php on line 87
Fatal error: Class 'FOFConfigProvider' not found in /home/clients/6a0b43a5add26c536570d4cb7062e046/web/libraries/fof/model/model.php on line 570
Then I cant get back to the administrator page, it keeps saying that error message.
Stefan
It sounds like you may have unintentionally changed the credentials that Joomla uses to connect to its database.
You'll need to know the username and password that your hosting account uses to connect to the Joomla database. If you don't know what these are you'll be able to find the username in your cPanel and you should be able to reset the password.
Then using either an FTP client or your cPanel file manager,
- open the configuration.php file in the root of your site
- locate the lines that start with public $user and public $password
- as precaution first copy and save the vales on these two lines
- then change their values to what you noted above, eg
public $password = "my_database_password";
That should do it.
The name of your Joomla database is set in the same configuration file on the line public $db. I think it's unlikely that you could have unintentionally changed this, though you could double check if updating your username and password doesn't work.
Good luck!
The FTP section you see at the Joomla! admin is for handling FTP jobs between your website and the server and it can't manage the server's FTP account.
In any case, you can bring your site back by disabling FTP like what it was before. Since you have no access to the website, you can do it via FTP or cPanel. Go to root folder of the Joomla! site and open configuration.php file. Then change the value of public $ftp_enable = '1'; to public $ftp_enable = '0';. It'll disable it again and you'll be able to see the website again.
I transferred my magento installation on ubuntu with files and mysql db dump to my development machine on Windows 10 with XAMPP installed.
I can up the frontend, but I cannot login my admin backend.
I am sure the password and user name are exactly as my installation on ubuntu, why happened? It just stay on the login form and saying all the time invalid formkey, I viewed the source formkey value just generated there.
There mentioned issue with charset, tried no help.
There is no any error logged in var/report and XAMPP apache errorlog, access_log to /index.php/admin is 200, looks good.
will you have any idea? thanks in advance.
Possible causes include
Incorrect permissions on var/session, preventing session files from
being saved
Incorrect configuration of database/redis/other session storage,
preventing saving of session values
A module is instantiating sessions to early, preventing the correct
session names from being set
The cookie domain in System -> Configuration -> Web -> Session Cookie
Management doesn't match the actual site domain.
You're using the localhost as your server domain, and using a version
of webkit that has trouble/bugs setting cookies for localhost in some
situations.
Easier is just to use the IP-address 127.0.0.1 to access Magento.
Open magento database and run below query.
update `core_config_data` set `value`='/' where `path`='web/cookie/cookie_path';
update `core_config_data` set `value`='[magentohost]' where `path`='web/cookie/cookie_domain';
If you have setup multiple store with subdomains, add Cookie Domain: .magentohost.com
Add a dot “.” follwed by Magento URL.
source : CodePetals
I installed the Purity-III template for Joomla (3.3.0) on my local machine and I get error message from time to time like in the picture below. 'From time to time' because when I refresh the page with the error message the error is gone (Before installing the temmplate I never got those error messages).
Any idea why this is happening and how to prevent?
(ps: I checked that that the access rights for files and folders are set in the proper way)
It's quite possible that you do not have ownership of the file that is trying to be "touched". This is something that your server administration/hosting provider will have to sort out unless you're comfortable with SSH commands.
Also ensure that all folder are set to chmod 755 and files are 644. To ensure this is the case, you can install an Joomla extension called Admin Tools which allows you to perform a bulk permission change.
I moved website to new server, domain stay the same, files structure stay the same, but path to public_html has beed changed. Database has been also moved.
I tried to clean cache, but i dont think I made it. This is error i get:
Could not find action file at: /home/account_name/domains/domain.co.uk/public_html/manager/controllers/default/welcome.php
account_name is different now.
I havent access to the old server, so I cant login and clear cache. I tried to do it using php script I found, but it didnt help.
Moving to new server documentation - there is welcome.php error and how to fix it, but since I haven't access to website from old server, I can't do it.
Also I can't login and clear cache in admin panel, because this message in when i wan get access to it.
I also change in db, in modx_workspaces->path from {core_path} to home/account_name/domains/domain.co.uk/publis_html/core, but didn't help.
How can i clear cache or if it's not the case, what should I do to make it work?
Update
I have change location in settings:
config.core.php
connectors/config.core.php
core/config/config.inc.php
manager/config.core.php
In .htaccess I couldn't find path to website, I didn't change anything.
I remove all content from core/cache/, except one file (.gitignore), and if I go to domain.co.uk/manager/ it's blank page, no content at all. And still can't log in.
Clear the cache on the new server manually VIA FTP or from a shell.
Change that modx_workspaces thing back
did you change all your settings in core/config/config.inc.php ?? if not do so, that is where you will set most of your paths & database credentials.
you have a backup? good!
Now upgrade to the same version of modx, that should fix all your path issues. [make sure you are not logged into the manager while trying to upgrade]
When moving the site to the new server rather watch two things:
the right paths into this files
/config.core.php
/core/config/config.inc.php
/connectors/config.core.php
/manager/config.core.php
the folder /core/cache/ is empty. They can be cleaned simply by removing the contents via ftp.
and correct the value in the database back to {core_path}
I decided to give a try to Magento. I have used my hosting provider´s service Simple Scripts to install it in a subdomain. After succesfull install a have tried to go to home page but this error has occured:
SQLSTATE[00000] [1045] Access denied for user: 'testing_1303#10.10.29.3' (Using password: YES)
I have searched google but found nothing. I have checked my data in app/etc/local.xml file. host, user, password, dbname everything is OK. I also checked minimal requirements with magento script and a I have passed all requirements.
Do you have any sugestions?
One more clue: I have renamed local.xml file to force Magento to install again, but it does not start the instalation. My browser throw this error: Firefox has detected that the server is redirecting the request for this address in a way that will never complete.
SOLUTION:
And here is the solution with help of my hosting provider:
In the local.xml file put this as a host:
<host><![CDATA[127:0:0:1:/tmp/mysql50.sock]]></host>
This is almost definitely not an issue with Magento.
If you are sure your database credentials are correct then the problem probably lies in the fact that you are trying to connect to a non-local database server and the server does not allow remote connections.
SOLUTION: And here is the solution with help of my hosting provider: In the local.xml file put this as a host:
<host><![CDATA[127:0:0:1:/tmp/mysql50.sock]]></host>
Try emptying the var/ folder. Maybe it's a cache issue.