Installing database when create a clone of website in local server - database

G'day, I am trying to make a clone of the WordPress website into my local server. I installed the Duplicator plugin and generated a archive file of the website and the installer.php. Then after ran the installer.php from http://localhost:8888/untitledfolder/installer.php.
In the step 2 (Install Database) there is an error which is a connection failure. I already created a database named 'livewebsite' beforehand. It's likewise the below image.
Any help would be really appreciated though I am new to WordPress trying to learn from the scratch. No down votes for the question please. Thank you! :)

I got the issue. That was my username and password. Username & password should be default data which is root and 123 for my settings. Thank you!

You should change MySQL port (the right input with localhost) from 8888 to 3306. That's the real port of MySQL server.
After change and retry, you can see the Host: Fail will become Host: Success with green flag I think. If Database still have a red fail flag, please edit your database username and password. It's not your WordPress account.

Related

MediaWiki installation issue - port problems

I am trying to install MediaWiki version 1.31 localy and I have run into some issues that I cant get past by. Mainly when I input datatabe connection (I am trying to connect to PostgreSQL database) information it returns this error.
Thing is the port I am trying to connect is 5433 not 5432, also the names "template1" and "postgres" are not included in my input trough the dialogue screen - I dont know where they came from. "test1" is the name of the database I am trying to connect to.
Any help or advice how to get trough this error would be greatly appreciated. Thank you.
That the port you specify is not used while setting up the database schema in the first place is a long-standing known bug. One workaround is to run your database on the default port until you have wiki set up, then change it back to the port you want.
In order to create a new database, you need to connect to an existing database in the same cluster. 'template1' and 'postgres' are pre-existing databases (usually created at the time the cluster was created) commonly used to connect to in order to create a new database. These names are "well-known", you don't need to specify them.

Publicly Visible Database Password on Github an issue?

I'm running an express server and I am very new to databases. If I have a public repo on Github of my express server and have this line of code publicly visible in one of the files:
const pool = new Pool({
user: "postgres",
host: "localhost",
database: "postgres",
password: "dummypassword",
post: 5432
});
Can people somehow connect to my PSQL database using my 'dummypassword' and mess up people's accounts that are stored in that database? I am planning to deploy it to DigitalOcean and I am wondering if this could be an issue somehow later down the road.
Thanks :)
If dummypassword is your true database password, then yes, this is absolutely a problem. You would literally be giving hackers instructions on exactly how to connect to your database! Don't do this.
Look into using dotenv on npm. This will allow you to create a .env file that can hold this precious information on a server outside of version control i.e. Github.
https://www.npmjs.com/package/dotenv
To expound on this, I would always err on the side of caution when dealing with database credentials. Say someone did get access to this information but that wasn't the actual database password, but the rest of the credentials were. The intruder now knows what kind of database you are running, where it's located, what port, and the username. All they need is the password in order to gain access to your entire production database and all of your users information.
I'm assuming you are saying; can someone connect to my production database ONCE you have changed the password for your production database?
If so then there is nothing in your example that isn't default so the answer is no.
If you're saying that "dummypassword" will be in production then yes that would NOT be a good idea, but I'm guessing you're not saying that.

Setup SQL Server JDBC Connection Pool and Resource on Tomcat 7

Firstly let me start off by saying I've been Googling for quite some time now and I can't find a straight forward answer to this. Either my Google-Fu is terrible or there really isn't a clear and simple way of doing this. Even on the official site I get pages and pages of jargon.
I'm used to Glassfish and am quite spoiled when it comes to connection pool setup especially with the Glassfish admin console. What I'm looking for is just a simple step by step, e.g. 'Go to this file, add this xml tag', paste your JDBC driver in that folder, done'. But I can't find something like that.
What I have is
The Server IP Address the Database is on
The database name
The username
Password
and JDBC Driver .jar file
It would greatly be appreciated if someone can clear things up for me a bit. Thanks!
Here is the document for setup tomcat connection pool using DBCP

How To See User Database On PGAdminIII with Heroku?

I set up PGAdmin III with my Heroku database.
I was wondering how I can see my Users database. I am still building my website so I wanted to test how they are being registered in the database.
However, all I see is tons of databases with strange "d10abc111ldlapsaman"-like names. How do I access my User database?
If PGAdmin III is not the right tool for this - what tool should I get to see my users of my still - in -development Heroku application?
You may have figured out your issue by now, but what you want to do is go to https://postgres.heroku.com. Look at your default connection settings for your database. Now, do the following in pgAdmin III using these settings:
File -> Add Server
Name: anything you want
Host: ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com
Port: 5432
Maintenance DB: yourdbname (in your example it would be d10abc111ldlapsaman)
Username: uiuskwljksjdkje (change to yours)
Password: sdjfj3##f333edfs (change to yours)
The other settings can stay at what they initially were.
You should no be connected to the server. Expand it and scroll through the long list until you find your database name (the one that you put as Maintenance DB).
You're done!
Updating the answer for someone who still needs it, like me:
Go to your heroku account and find your database credentials (you should open your app, then postgres on add-ons and finally settings):
screenshot
In pgadmin you should right-click on 'servers'-> create -> server and enter your credentials:
General/Name: the name that pgadmin will show (only for you)
Connection/Host name: Host in credentials
Connection/Port: Port in credentials (probably 5432)
Connection/Maintenance database: Database in credentials
Connection/Username: User in credentials
Connection/Password: Password in credentials (tip: check the box to save it)
SSL/SSL mode: Require
Advanced/DB restriction: your database (same as maintenance db) -> this will filter only your db of the many others that will spam if you don't do that.

processmaker : connect to database

according to the title, i want to connect the process maker to the database.
i use MySql as an engine, the server is localhost, and the port is 3306. after submit the configuration, then the processmaker doing 4 steps to test the connection. i already passed the first 2 step, but the 3 and 4 step are failed.
the processmaker say :
MySql connection refused!
i follow the instruction from http://wiki.processmaker.com/index.php/Database_Connections
but it still doesn't work.
thanks for your answer
Did you verify that your information is the correct one???
Check your mysql Username and password, and try using 127.0.0.1 as server
When you installed ProcessMaker, which database did you use as a default one?, I've asked you this beacuse ProcessMaker comes with Apache and Mysql by default so maybe this step is unuseful to do.
Regards,
processmaker
make sure you are using correct version of mysql supported by processmaker.

Resources