i’m using heroku for deploy a database (postgres) and connect to it.
I used it for 2 weeks but today it start rejecting my credential and i couldn’t login anymore, i checked if the credential are changed but nothing?
Can anyone help me? thanks a lot!
I had this issue, if you look in the Settings -> Config Vars you will see that the DATABASE_URL has changed. So you need to use the new value in Datagrip and things will work again.
They change the details periodically but it doesn't seem to update in the database settings page which is very annoying although it only happens on the free tier.
Related
anyone facing something similar? sadly I'm on a free plan so I can't open a ticket... does anyone know of a way to restart the service/machine of the DB? maybe that would just solve it...
ok so the issue in my case is that indeed heroku performed some sort of maintenance on the DB, and apparently it's connection params (host/url/user/password) had changed... and since it was embedded throughout all my interfaces (the app, my db tools, admin app I also have) - none were able to connect (they'd timeout).
while trying to figure out, I used the wonderful CLI tools of heroku pg:info and heroku pg:diagnose and even heroku pg:psql and tested to see that my data is still there... eventually I went to the online admin and that's where I saw the connections params had changed. BTW - I have this project for 2 years and this is the first time this had happened...
I was in the same situation. Heroku will email you that your database is scheduled for maintenance. After it's complete, connecting to the database fails because of this error:
error: no pg_hba.conf entry for host "IP_ADDRESS", user "DB_USER", database "DB_NAME", no encryption
This is telling us that incorrect credentials were given, meaning the database connection string has changed. I first checked the credentials on the website for the Heroku Postgres Add-on (data.heroku.com), but the connection string was still the same as before; it has not updated or changed at all, therefore this was misleading. Instead, the updated connection string is found inside of the DATABASE_URL config variable, located in the Settings tab of your app on the Heroku dashboard (dashboard.heroku.com), under Config Vars. To avoid manually correcting this problem again, get the connection string from the DATABASE_URL config variable directly, as opposed to hard coding it in your app.
Yes, Im in the same situation. Heroku are a bunch of amateurs. They did some maintenance on the DB, and after it was done, credentials don't work, even those listed in admin/dashboard section of web. Bunch of loosers... #heroku
My Hoster installed Typo3 9.5 for me with composer. I did the setup of typo3 but went on holidays a week afterwards and could not remind the password. So I changed the password in phpmyadmin but still can’t login. It says: Oops, an error occurred. I tried to find out the error and it told me that there must be a problem with the password hashing. I can't find the problem because the php version 7.3. has the correct hashing activated automatically in my opinion.
I can't use the front end login and no install tool can be activated with the ENABLE_INSTALL_TOOL command. So I can’t work and tried to find a solution for two days now. My hoster won’t help with that problem.
Is there anyone who maybe had the same problem? I had to admit that I’m not a developer with much experience... Thanks a lot if anybody could give me an advice!
Create an (empty) file named ENABLE_INSTALL_TOOL in typo3conf/ with permission that webserver at least can read it.
Then call domain.tld/typo3/install.
Try a password and save the returned hash in typo3conf/LocalConfiguration.php.
When you are logged in in the install tool, you can create a new admin user for TYPO3 backend.
If you have forgotten the Install tool password, you can reset it by modifying [your_site]/typo3conf/LocalConfiguration.php on the Typo3 server. Replace the $TYPO3_CONF_VARS['BE']['installToolPassword'] row with the following:
$TYPO3_CONF_VARS['BE']['installToolPassword'] = 'bacb98acf97e0b6112b1d1b650b84971';
This will give you the default password ("joh316") back again.
More information
Greetings
I'd like to backup a db today through localhost:8069/web/database/manager
, but the button return nothing while clicking the button.
Terminal show no error there.
Also invalid for duplicate, delete, create database,restore database and set Master password except link of existed db.
see pic as below:
the problem emerged since I deployed odoo12.
I can directly backup through pgAdmin4.
but I still want to know what happened.
My version of pgsql is 9.6 for odoo10 and odoo11.
It worked smoothly before I deployed odoo12
I found it's a stupid question.
the reason is that I connect to wrong db_host:
my conf set db_host as 127.0.0.1 but connect to localhost.
keep this topic for who make same mistake
I try to backup my university project database. I followed the instruction, everything seems to be inputed:
1:
2:
3:
But the only pop-out I get is this one in right-bottom corner of PGAdmin 4:
From the Official site, there should be another pop-up message, similiard to this one:
But I don't get this one, nor I get the other one that is displayed where any error occurs.
I tried to directly use pg_dump.exe, but it prompts me for a password. I tried all my passwords - user password, server password which I use to connect to my database in PGAdmin 4, other passwords, but none of them seem to work.
I tried to find any information about this, but all articles about pg_dump.exe are about how to automatize password input. What is the cause of this backup silent failure, and which password does pg_dump.exe need?
I'll add any details if needed, I was trying to figure it out for 4 hours now...
I've tried with pgAdmin4 1.4 and still my backup file was empty so I moved back to pgAdmin3 and it worked like a charm.
Although pgAdmin3 is not maintained anymore I suggest you use it until pgAdmin4 is up to it but right now it is way too slow.
Can you upgrade your pgAdmin4 with version 1.2 and try again?
https://www.pgadmin.org/
I think they have fixed the issue in new release.
Clearing the items in the path: C:\Users\yourUser\AppData\Roaming\pgAdmin seems to do the trick. Tested on PGadmin 4.29.
Be aware that all the sessions and saved servers will be gone.
I'm getting this error when I try to connect to my mongolab DB.
I saw some different topics talking about this issue, but solutions they gave was:
-Add mongoDB exception in my firewall. I done it without result
-Check if I was using the mongolab.com user and password instead of the user database. That's not the problem, even I created new users.
-Check if my version of mongoDB was older than the version used by mongolab (3.x). I also specified the auth system in the command to be sure.
I tried all those answers without success. I also checked the connection with the server, and it neither was the problem. I'm going crazy.
What could be the issue?
Thanks for your attention!
It was finally a network problem. I was lucky to discover it, cause I lost many hours.