I'm working and out of no where i get this error. Didn't upload anything. I get Error establishing a database connection. The only thing i've done recently is install piwik analytics but i tested that thoroughly on the test server. I'm scared that i've corrupted the database. And i haven't got the most recent backup. I can't access any page on the website.. front end or backend. What is going on? Is the database overloaded?.. if so when does it reboot, all i want is the website to work as it doesn't belong to me.
i think you should have to refer this link.hope you may got your solution from there.
It could be that your database login credentials are wrong or have been changed.
It could be that your database server is unresponsive.
It could be that your database has been corrupted.
Try to define define('WP_ALLOW_REPAIR', true); inwp-config.php file.
then visit this link http://www.yoursite.com/wp-admin/maint/repair.php.
you see database repair option.
Related
I'm trying to restore a WordPress website for which I have the files backup, but I don't have a DB backup on hand.
I managed to get the site up partially by restoring the backup in cPanel - all the site's pages are working now, but because there is no DB in place (wp-config.php points to what 'used to be' my DB) accessing site.com/wp-admin renders this error:
Error establishing a database connection
This either means that the username and password information in your wp-config.php file is incorrect or we can't contact the database server at localhost. This could mean your host's database server is down.
Are you sure you have the correct username and password?
Are you sure that you have typed the correct hostname?
Are you sure that the database server is running?
If you're unsure what these terms mean you should probably contact your host. If you still need help you can always visit the WordPress Support Forums.
I know I made a huge mistake by not backing up my website DB.
Is there any way to be able to access wp-admin in this case? Can't I 'mock' the old DB with a new one? Anything to be able to access wp-admin.
Configure a core Wordpress with fresh installation point your current Wordpress files to the new database just got created
You should copy all the settings (from DB_NAME,DB_USER,DB_PASSWORD......AUTH_KEY,SECURE_AUTH_KEY..... till table_prefix) from your new installation wp-conf to old one
You would have lost almost all data stored in db like users etc however if your theme was more file based you should be able to se pages up
This is Triel and i think it should work to bes extent dont see any other way out of this scenario.
"Can't I 'mock' the old DB with a new one? Anything to be able to access wp-admin"
Simply Create a new mysql DB on your server and put its info in your wp-config.php file.
I am using msdeploy to push out website code to 4 different servers (test and production servers). Works fine on the first 3, but the 4th is giving me an ERROR_CERTIFICATE_VALIDATION_FAILED error. I am using the -allowUntrusted option.
"C:\Program Files\IIS\Microsoft Web Deploy V3\msdeploy.exe" -verb:sync -source:iisApp="E:\workspace\testDeploy\outproject\_PublishedWebsites\<webfolder>" -dest:iisApp="mycompany.com",ComputerName="https://<hostip>:8172/MsDeploy.axd",UserName="<userid>",Password="****",AuthType="Basic" -allowUntrusted -enableRule:AppOffline -skip:objectName=filePath,absolutePath="^.*<webfolder>\\web.*\.config$|^.*mycompany\.com\\web.*\.config"
Error Code: ERROR_CERTIFICATE_VALIDATION_FAILED
More Infenter code hereormation: Connected to the remote computer ("<hostip>") using the specified process ("Web Management Service"), but could not verify the server's certificate. If you trust the server, connect again and allow untrusted certificates. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_CERTIFICATE_VALIDATION_FAILED.
Error: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
Error: The remote certificate is invalid according to the validation procedure.
Any idea what I am missing?
Adding <AllowUntrustedCertificate>True</AllowUntrustedCertificate> to my pubxml file seemed to fix the problem initially.
Upon re-publishing days later though, I got the same error. I went into the Publish Settings, re-entered my password and the publish succeeded.
I'm now thinking my initial problem was solved by re-entering my password, not by adding <AllowUntrustedCertificate>True</AllowUntrustedCertificate>.
-allowUntrusted did not worked for me.
I used this:
/p:AllowUntrustedCertificate=True
Adding this solution as none of the others worked for me...
I had to add these lines to publish profile:
<UseMSDeployExe>True</UseMSDeployExe>
<AllowUntrustedCertificate>True</AllowUntrustedCertificate>
After adding those, publish still failed. Then I opened the publish profile settings, clicked validate connection, and saved. Only then did publish succeed.
I fixed this by going into the publish settings, then clicking "Validate Connection" at the bottom. Then this error goes away.
The problem was with the password for the user on the destination system.
I saw on another post that someone moved the -allowUntrusted flag before the -dest entry. I tried that and I started getting a ERROR_USER_UNAUTHORIZED message. Everything was correct with the password as it was entered, but it started with an * character and also had a single quote in it. I generated a new password for the user that didn't use those special characters and changed it on the remote system. After that, everything worked fine.
I was able to run the command as shown in the initial post without any error.
If you are getting a ERROR_CERTIFICATE_VALIDATION_FAILED or ERROR_USER_UNAUTHORIZED and everything is set up properly, try changing the password assigned to the user on the destination system. It would seem that some passwords just won't work.
Another Potential Solution - Deploying Web Jobs specifically
I know this is an old post, but I ran into this issue with VS 2019 when deploying my Azure Web Jobs. None of the above worked for me. What did end up working was re-authenticating using the tooling after updating the publishing profile. The way I resolved it was by right clicking the solution and selecting "Publish as Azure Webjob.." Even after creating a new publishing profile it still failed. I then added the following my publishing profile.
<_DestinationType>AzureWebSite</_DestinationType>
<UseMSDeployExe>True</UseMSDeployExe>
<AllowUntrustedCertificate>True</AllowUntrustedCertificate>
I tried publishing it again and it failed. Then I re-authenticated by clicking the edit password link shown below.
When you do, you'll see the following screen. Click on the "Attempt to retrieve credentials from Azure" link.
Don't forget to hit the save button at the bottom after retrieving the creds from Azure. Once you do, go back and try publishing again. It should work just fine.
NOTE: If you just pulled down/created your publishing profile for the first time, do not click the edit button under the name of the Publishing profile and validate the connection that way as shown below.
If you do, it may remove the username/password from the UI for the publishing tooling shown in my first image above. If it disappears, you need to start this process all over again by deleting your profile, creating a new one and finally following the steps above in order. I don't know why it does this, but just something I noticed.
I notice you used the IP address for the deployment server:
-dest:iisApp="mycompany.com",ComputerName="https://<hostip>:8172/MsDeploy.axd"
This caused the certificate validation error for me because the SSL certificate was issued for the domain name, not the IP address. Changing to domain name instead of IP address fixed it.
Just want to add my 50 cents and my solution so it may help someone else.
what i did yo solve this is to use remote desktop to connect to the host machine
and when asked to accept the machine certificate ( after input login and password ) i marked remember this at the bottom.
hope this help someone
Hi have a few DotNetNuke websites that intermittently show the under construction page for no apparent reason. I just load and resave the web.config file and it restarts correctly for a few weeks.
I am looking to find ways to identify the source of the problem, I guess it has somehing to do with the database connection or user, but I really don't know where to start troubleshooting and what tools to use to find the issue.
Any help appreciated.
If you go to http://www.mydomain.com/install/install.aspx when you're getting the Under Construction message that will likely tell you that the site can't connect to the database server.
So from there, you will want to check what is going on with your connection to your database. One thing you might try to start, is change the User Account that you are using to connect to the database server. Maybe create a new SQL user/password and connect with that one, instead of the existing account.
I had a website that had this problem, with a remote SQL server, and unfortunately, come to think of it, I didn't do anything to fix it, eventually it just stopped doing that...
I have just moved my site from developpement plateform to production.
I configure the setting files in the $db_url string. I have put the good ones because I use these credential in a shell to access th database, there is no problem.
But when I try to access my site I get the following message:
Site off-line
The site is currently not available due to technical problems. Please try again later. Thank you for your understanding.
If you are the maintainer of this site, please check your database settings in the settings.php file and ensure that your hosting provider's database server is running. For more help, see the handbook, or contact your hosting provider.
you will see this message if drupal can't connect to its database....check the filed settings.php again...and make sure that the database, username and password are correct and no problem with connecting to the database
I had created a folder in my site, and uploaded drupal in it. But when I access it, the following error is coming
Internal Server Error
The server encountered an internal error or misconfiguration and was unable
to complete your request.
Please contact the server administrator, webmaster#xxxxxx.xx and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
There are literally thousands of things that can be wrong
Do you have access to the webserver logs? Check /log/apache/error.log for errors.
Have you already configured drupal correctly? Normally, when you surf to the drupal root directory, you get presented with an installer message.
Does your server support PHP?
I'd recommend any of the following:
Checking that you meet the Drupal requirements
Re-uploading the whole Drupal folder
Testing the Drupal folder (is this a custom installation, or just straight from the drupal website?) on local LAMPP webserver.
Assuming you're trying to run Drupal for the first time (ie run the installer), have you followed the pre-install setup?
Here's Drupal's "Quick install guide for beginners": http://drupal.org/documentation/install/beginners
Since you've already uploaded the code and you have your domain set up, you can probably skip down to the big labelled "Create the configuration file and grant permissions".
The first thing in this section is to create your settings.php file. Drupal won't work without this. You also need to set its file permissions to that Drupal's installer can update it.
My guess is that this is why you're getting the error. Follow the instructions on the page I linked you to above and you should be okay.
You'll also need to have a database ready for use by Drupal. The Drupal installer will populate the DB tables, but you need to at least have the empty DB ready for it to use.
Hope that helps.