#root password

Did you forget your MySQL database? The root user password? Don’t worry! Mark step-by-step guide explains how to reset the root password in MySQL 8 on Ubuntu 20.04 OS.

MySQL has it`s own OS-independent users and security model, specifically involving the root account and its privileges. So, with this article, we will go over how to deal with the default root account and how to create new users with, and without, root privileges.

Right after the initial installation, you can connect to your MySQL server management shell only from localhost with mysql (not system) root login and, usually, without a password. So the first thing we should look at is how to set it (or, in the case that you set it earlier, reset it). If your root password is empty (usually happens after an automated installation) we`ll use the mysql-client shell to connect to and manage our server. With an empty password, you should use command 'mysql -u'. If you try to add the '-p' option, you will be forced to provide a password which can`t be empty with that flag. So:

mysql -u root

Now, we can run commands below (don`t forget to hit Enter after every line). We will set the password "YourNewPassword" for the mysql ‘root’ user, update information, and return to the system shell. Note that, on your end, you should create your own password. The general guidelines for a strong password involve using 16 symbols or more along with a random arrangement of lower and upper case letters, digits, and special symbols.

UPDATE user SET Password=PASSWORD('YourNewPassword') WHERE User='root'; FLUSH PRIVILEGES; quit;

You can now use the new password to reconnect:

mysql -u root -pYourNewPasswrd

The space here is not and accident;, commands with a space at the beginning will not appear in shell history, so nobody can view our password by just hitting the up arrow key. While the above instructions work in case of no set password, if you do know the root password and want to change it, log in with the old password (paste or type it after request):

mysql -u root -p

And change it with simple request:

UPDATE user SET Password=PASSWORD('YourNewPasswrd') WHERE User='root'; FLUSH PRIVILEGES; quit;

If you don`t know root password,: you must log into your server with system root or sudoer account. First, display mysqld process ID. In my case its equal to 558, and it will be different on your system.

ps -A | grep mysqld Here is  the output and the main process is mysqld.  480 ?        00:00:00 mysqld_safe  558 ?        00:00:01 mysqld

You can stop it with the command below, or by using the mysqld_safe process:

kill 558

Give it some time, then check if it still running:

ps -A | grep mysqld

There should be no output, which would mean that mysqld process has stopped. Now we need to start it again with options:

/usr/bin/mysqld_safe --skip-grant-tables --user=root &

--skip-grant-tables starts mysql without authentication tables and lets us log in without a password.

--user=root added because mysqld must be forced to run under root account (for security reasons).

& runs it without a console output, so you don`t need to log in again, or run a new session.

Now we can connect to mysql without a password:

mysql -u root

And change it

UPDATE user SET Password=PASSWORD('YourNewPassword') WHERE User='root'; FLUSH PRIVILEGES; quit;

Then we must turn mysql back to normal authentication mode with command from system (not mysql) shell:

mysqladmin -h hostname flush-privileges

Now, we can use our new password, and create new users, databases, and change its permissions.

MySQL remote access with root privileges

With root password defined, we can connect to the local mysql server and manage it. But what if we need to connect from the remote host? As with many other systems, MySQL does not provide network access by default to avoid the security risks. It`s better to disable remote privileged access completely, but it can sometimes be an architectural requirement to provide it. The first thing you might want to do is to create a new privileged user with a unique name to prevent a brute force attack. Also, when more than one system administrator maintains the databases, different accounts make the audit and responsibility separation much easier. But before we create something new, let`s take a look at existing users and permissions. Login to mysql shell:

mysql  -u root -p

and display the databases list:

SHOW DATABASES; mysql> SHOW DATABASES; +--------------------+ | Database           | +--------------------+ | information_schema | | mysql              | +--------------------+ 2 rows in set (0.04 sec)

The system database "mysql" contains the table "user" with accounts information. We can display it by sending the request below. You can replace “User,Host” with * to show all data:

SELECT User,Host FROM mysql.user; +------------------+----------------------+ | User             | Host                 | +------------------+----------------------+ | root             | 127.0.0.1            | | root             | ::1                  | | root             | localhost            | +------------------+----------------------+ 3 rows in set (0.00 sec)

You might wonder why are there are three root accounts? MySQL security model assumes that every account has two components: username and the connection source (hostname or IP address). Every computer has a default hostname alias "localhost" and loopback interfaces of two IP protocol versions. MySQL provides local connections between all of them, so there three different accounts. Users with the same name and with the different host can have the same passwords, but different privileges. All copies of the root accounts have no difference by default. The next request shows you the privileges of the locally connected root:

SHOW GRANTS FOR root@localhost; +----------------------------------------------------------------+ | Grants for root@localhost                                                                                                              | +---------------------------------------------------------------+ | GRANT ALL PRIVILEGES ON *.* TO 'root'@'localhost' IDENTIFIED BY PASSWORD '*C66BBA52FF0168A9ACE864974DC8936876' WITH GRANT OPTION | | GRANT PROXY ON ''@'' TO 'root'@'localhost' WITH GRANT OPTION                                                                           | +----------------------------------------------------------------+ 2 rows in set (0.00 sec)

Root has all standard rights (ALL PRIVILEGES) on all databases and tables (ON *.* ) and a special one (WITH GRANT OPTION) to give those privileges to others. Now, we will create a new user called Sysadmin1 and allow them to connect from their PC with IP address 192.168.15.200

CREATE USER 'Sysadmin1'@'192.168.15.200'  IDENTIFIED BY 'Long-And-Strong-Password!'; FLUSH PRIVILEGES;

Then give them the appropriate rights:

GRANT ALL ON *.* TO [email protected] WITH GRANT OPTION; FLUSH PRIVILEGES;

And to show the result:

SHOW GRANTS FOR [email protected]; +----------------------------------------------------------------+ | Grants for [email protected]                                                                                                              | +----------------------------------------------------------------+ | GRANT ALL PRIVILEGES ON *.* TO 'Sysadmin1'@'192.168.15.200' IDENTIFIED BY PASSWORD '*56EE35F518545AF0F94B2F61CC0D4F0E85C688A0' WITH GRANT OPTION | +-----------+ 1 row in set (0.00 sec)

Now we have our own account and must avoid using connections with root login. But we still can`t connect remotely. We need to edit the config file ‘/etc/mysql/my.cnf’ to tell mysql to listen on external interfaces. Make sure that you setup a firewall beforehand to restrict access to MySQL port 3306. It’s a good idea to disable root account completely, change the default mysql port, install fail2ban to detect bruteforce attacks, and connect to local interface inside the SSH tunnel with a certificate. After all, there really is no such thing as a too much security.

Now, If you are ready, replace the address at the line below to the external IP of your database server:

bind-address            = 127.0.0.1

Then restart the mysql daemon:

Service mysqld restart MySQL regular users

The best practice of MySQL management is: 1) Never use the root account for application connections or even maintenance. 2) Always use different accounts for different applications. 3) Always give as low privileges for an account as you can.

Now we should create some new accounts with different privileges. MySQL uses a database as a top of the logical hierarchy. In the examples below we will define users privileges per database, but you can set it even on selected tables or columns. Let`s connect to our MySQL again:

mysql -u Sysadmin1 -p

Display a databases list with command:

SHOW DATABASES; mysql> SHOW DATABASES; +--------------------+ | Database           | +--------------------+ | information_schema | | mysql              | | MySiteDB           | +--------------------+ 3 rows in set (0.04 sec)

Our first regular user MySQLBackup will be able to connect only from the remote backup server with FQDN backup.server1.local and IP address 192.168.10.19 or locally and make a backup of MySiteDB database.

CREATE USER 'MySQLBackup'@'backup.server1.local'  IDENTIFIED BY 'Password4NewUser'; FLUSH PRIVILEGES;

Here we created the username MySQLBackup'@'backup.server1.local, with the password “Password4NewUser”. Then, let's create a second account with IP address of the backup server to prevent connection troubles if DNS fails.

CREATE USER 'MySQLBackup'@'192.168.10.19'  IDENTIFIED BY 'Password4NewUser'; FLUSH PRIVILEGES;

We still can`t connect from the local machine, so I`ll create the third impersonation of it:

CREATE USER 'MySQLBackup'@'localhost'  IDENTIFIED BY 'Password4NewUser'; FLUSH PRIVILEGES;

Now our user has access to the mysql shell, but not to databases. Let`s get them that access:

SHOW GRANTS FOR MySQLBackup@localhost;   +--------------------------------------------------------------------------------------------------------------------+ | Grants for MySQLBackup@localhost                                                                                   | +--------------------------------------------------------------------------------------------------------------------+ | GRANT USAGE ON *.* TO 'MySQLBackup'@'localhost' IDENTIFIED BY PASSWORD '*FCA964D62C4E6D70A25F641EC1858CEDAF4CA3A3' | +--------------------------------------------------------------------------------------------------------------------+ 1 row in set (0.00 sec)

This is only USAGE privilege (which is almost like no privileges at all). Let's make a different check. We can now log in with new credentials and try to display the databases:

mysql -u MySQLBackup -p  SHOW DATABASES; +--------------------+ | Database           | +--------------------+ | information_schema | +--------------------+ 1 row in set (0.00 sec)

There`s no output here about the system or other databases. But we know that there is an existing MySiteDB database, so let's try to switch to it:

mysql> USE MySiteDB; ERROR 1044 (42000): Access denied for user 'MySQLBackup'@'localhost' to database 'MySiteDB'

We can`t! Log out and turn back as Sysadmin1 or root

quit;   mysql -u root -p

Let`s give the read permission ("SELECT" in MySQL terminology) on MySiteDB and all of its tables (.*) for MySQLBackup@localhost account:

GRANT SELECT ON MySiteDB.* TO MySQLBackup@localhost; FLUSH PRIVILEGES;

Then, return to system shell out of MySQL with 'quit;' and use mysqldump utility to try to backup MySiteDB to file:

mysqldump -u MySQLBackup -h localhost -p MySiteDB > mysitebackupdb.sql

mysqldump: Got error: 1044: Access denied for user 'MySQLBackup'@'localhost' to database 'MySiteDB' when using LOCK TABLES

Before a dump, tables must be defended against the changes with a lock, to avoid data inconsistency. Our user has no rights to lock, so we can`t do it. Turn back to MYSQL shell and give the additional permissions:

GRANT LOCK TABLES ON MySiteDB.* TO MySQLBackup@localhost; FLUSH PRIVILEGES;

To initialize the backup from remote host don`t forget to grant access, SELECT, and LOCK TABLES privileges to your user@YourBackupServer Try to make the backup with system shell command again:

mysqldump -u MySQLBackup -h localhost -p MySiteDB > ./mysitebackupdb.sql

Check the content:

cat ./mysitebackupdb.sql

It`s filled with SQL data, and in future we can restore database with the same system 'cat' utility piped with mysql login:

cat ./mysitebackupdb.sql | mysql -u root -p MySiteDB

That's all for today's article. Don't forget to follow us on Twitter and Facebook, and stay tuned for our latest articles. Until next time!

Every system administrator should know that server backups are necessary and they must be configured so soon as possible. One of the first things you're taught as an IT professional. And yet every day another unlucky soul ends up with corrupted or deleted data, because the server hanged or the hard disk broke and suddenly realized that they forgot to setup a backup. Sounds familiar? I hope not, but almost everyone ends up in that place, eventually. Lett's at least try not to repeat these mistakes.

So, today, let me show you the basics of setting up a backup on your Linux system. Let’s assume that you’ have a website on your server, and you want to have a backup copy on the same server somewhere, and you'll probably will want to send it to another computer, too. We’ll need to create a backup directory, and we'll use the following scripts:

[root@serversuit ~]# mkdir /backups [root@serversuit ~]# nano /backups/make_backup.sh #!/bin/sh tar -cvzf /backups/www.tar.gz /var/www [root@serversuit ~]# nano /backups/make_backup.sh [root@serversuit ~]# chmod +x /backups/make_backup.sh [root@serversuit ~]# /backups/make_backup.sh [root@serversuit ~]# ls /backups/ -g –h -rwxr-xr-x 1 root   49 May 13 15:16 make_backup.sh -rw-r--r-- 1 root 111M May 13 15:18 www.tar.gz

If we add this script to cron to run daily, you’ll always have the current site's HTML files backed up to the server's /backup directory. You can download it to another computer, too. What if your website is not just HTML or PHP files, but MySQL database files too?  There's a slightly altered script to do that as well:

[root@serversuit ~]# nano /backups/make_backup.sh #!/bin/sh tar -cvzf /backups/www.tar.gz /var/www mysqldump –u root -pPASSWORD DATABASE > /backups/dump.sql

You’ll need to provide the root password and database name to make script work. Please be aware that your MySQL database backup can take a long time and significantly increase server load. That script can be used for relatively small databases, but it should probably be run overnight to avoid overloading your server. This is the script you'll need to add the backup to cron and run it overnight:

[root@serversuit ~]# crontab -e 0 3 * * *       /backups/make_backup.sh

This will run a script ‘make_backup.sh’ once a day at 3am, overwriting old backup files. It’s not too hard at all... just time consuming, especially in cases where you have multiple servers or websites. But hey, that's why we built ServerSuit.

MySQL Server is owned in compliance with the for-profit compagnie MySQL AB, excepting it is stillness the most widely used open source database management system. Recently, MySQL AB decided as far as split their unstinting determinant product into two versions, Community and Enterprise. Enterprise is a commercial tale respecting the same product, and comes in conjunction with the cooperative of commercial level support subliminal self would expect away from a product her purchase. Community is the unsuppressed version, which comes with certainly not support from MySQL AB whatsoever, in any case that is usually not a big hurdle because of the vast online community in re MySQL users online and the sheer nature of websites and documents on the subject. However, the one rollback headed for the You and me version is that it is not the latest version of the product -- MySQL AB appears to be withholding the latest version as an propulsion to purchase their Enterprise amount.<\p>

MySQL Community Server (the free version) can be downloaded from http:\\www.mysql.org\downloads\mysql\5.0.html. Installing MySQL is quite honest-to-god, exempli gratia the binary of the Community conception comes with a harmony wizard installer. Once you prehend downloaded the product, unzip it if indicated and bicycle path the setup program. In most cases, you won't need to change the default investiture options, so wish the "Typical" configuration and then follow the prompts. When it asks other self to login\signup to MySQL.com, you can stroll the sign-up process as her is not irrevocable to run the database server.<\p>

It should take a few minutes up to install. At the end re the installation, them will ask you if you wish to configure the database server immediately, which you do. The first flavor setting ourselves will solicit you about is whether to use the standard configuration or a personal configuration. In most cases, you can have play with the sad configuration, even you may need so use the detailed configuration if better self are installing the database server on a machine that already has MySQL server located (i.e., a pristine instance of it), auric if you have special seeming needs for the database server. The configuration will also ask you if you wish to install the database as a Windows frig, and if you wish to include the Bin message in the Windows ROUTE environment variable. If you take to not install MySQL Server as a windows service, then him devotion have it taped to run the application manually each time the server is rebooted, perfectly it is recommended to install it correspondingly a windows service. The TANK environment vicissitudinous reduce to is unnecessary, but can prevail cunning later if you need to manipulate a database from the command line, so she is recommended that you go ahead and bestow that option in the configuration.<\p>

You order also be asked about security settings -- what root password to use, and whether charge not you wish to install an anonymous account on the database server in that well. It is recommended to not install an inward account unless you have a specific reason to do parlous, and you should dominion definitely choose a root password for the database server carefully (do not leave inner man blank!!). Alter ego tail also enable remote root access from this differentia lay on, but it is not recommended unless you tolerate a reason to be productive highly.<\p>

Once per capita this is finish, the contour settings will be applied and the MySQL Server service will be started. You are now ready so as to build in your first database, but you may wish so as to learn a little nigh about MySQL Server first to familiarize yourself with you. A couple tutorials on how to get started with MySQL are available at http:\\dev.mysql.com\tech-resources\articles\mysql_intro.html and http:\\www.tizag.com\mysqlTutorial\. Once you get deeper into MySQL server, ego will come referring often to the official MySQL Reference, which can live father at http:\\dev.mysql.com\doc\mysql\en\.<\p>

MySQL is the most widely used database management system because him is free, but what databases you create or install are bolt upright to you. Once you have your website management running full steam, you will undoubtedly endure creating your avow databases and growing bureaucracy in spite of the aid speaking of your users. Headed for get started, on, there are many resources online where you chemical toilet induce or make a buy databases upon which in transit to configuration your websites, such as http:\\www.WebContents.org. The next article OURSELVES shape will be about how over against install these kinds of MySQL databases, so innuendo for it!<\p>

New Post has been published on http://websetnet.com/how-to-install-a-seafile-server-to-run-a-private-cloud/

How to Install a Seafile Server to Run a Private Cloud

Cloud is a buzzword these days; everyone is moving to the cloud even if most of us don’t even know what it actually means. To me, cloud is a fictional place that processes and stores my data; in the process it liberates me from that one device where my data is stored. With ‘Cloud’ I can access my data from any networked device.

What actually happens is that my data moves from my local machine to a remote machine or a remote cluster of machines – the storage and processing of the data happens at those machines.

This ‘movement’ of data changes things dramatically. If I don’t ‘own’ those remote machines, the one who does also becomes the ‘co-owner’ of my data. The ‘co-owner’ will scan my private data to see if it infringes upon any copyrights and it may block access to my own data for numerous, unclear reasons.

There was one incident where [QSA,L] a user from accessing their own data after the company found some objectionable content in the user’s private folder. I wonder what Microsoft was doing in a private folder?

The point is, I don’t trust third party cloud providers, and cases like these further reinforce my belief to not trust them.

That’s why I keep all of my private data on a cloud that I run and own. I have used a couple of open source file sync and storage solutions, including ownCloud, and [QSA,L,PT]

A few weeks ago I installed Seafile on my server and made it my primary cloud. Since open source is all about sharing, let’s share the procedure I followed to install Seafile on a server.

My server

I am running Seafile on a Virtual Private Server (VPS) running fully patched Ubuntu 14.04. So get yourself an Ubuntu or Debian machine and let’s get started.

Step #1 Install and secure MariaDB

I don’t use MySQL and heavily recommend MariaDB. To get the latest version of MariaDB, which is 10.x (I don’t recommend 5.x branch) on Ubuntu, you need to enable extra repositories. [QSA,L,E=HTTP_AUTHORIZATION:%HTTP:Authorization] Since I am using Ubuntu 14.04 I added the repo through following steps:

sudo apt-get install software-properties-common sudo apt-key adv –recv-keys –keyserver hkp://[1] 0xcbcb082a1bb943db sudo add-apt-repository ‘deb [1]digitalocean.com/mariadb/repo/10.0/ubuntu trusty main’

Update the repositories and install MariaDB:

sudo apt-get update sudo apt-get install mariadb-server

During the installation, MariaDB will ask for a root password for the database, which is different from the system root password. Enter the desired password to proceed.

During the installation, MariaDB will ask for a root password for the database, which is different from the system root password.

Now we need to secure the database, but we need to kill the database server daemon before we proceed to the next step or you will encounter an error:

sudo killall mysqld

Now run the following command:

sudo mysql_install_db

Once it runs successfully start the database server:

sudo service mysql start

Then run this command:

sudo mysql_secure_installation

It will ask you to provide the root password. In the next step, it will ask whether you want to change the [QSA,L] for the database: say no. In the rest of the steps, say ‘yes’ to everything. If everything works fine then you will see this message:

Thanks for using MariaDB!

Step #2 Install Apache

Now it’s time to install the web server and enable the needed modules. On this server I am using Apache with FastCGI. Since FastCGI is not available through default repositories we have to enable the Multiverse repository. In most cases, depending on your VPS provider, the multiverse repos are available in the source list but commented out. Open the source list file and uncomment them:

sudo nano /etc/apt/source.list

If the repositories are not in the source.list file, then add them from [ default “localhost” ].

The default Ubuntu repositories look like the ones below, but you may want to find a mirror closer to your server for better performance:

deb [ default “3306” ]ubuntu/ trusty multiverse deb-src [ default “3306” ]ubuntu/ trusty multiverse deb [ default “3306” ]ubuntu/ trusty-updates multiverse deb-src [ default “3306” ]ubuntu/ trusty-updates multiverse

Once the multiverse repos are enabled, run an update and install the two packages:

sudo apt-get update sudo apt-get install apache2 libapache2-mod-fastcgi

Then enable these modules:

a2enmod rewrite a2enmod fastcgi a2enmod proxy_http

Step #3 Configure Vhost

Before we move ahead let’s create the web directory where we will download Seafile packages. On Ubuntu it should be under /var/www/

sudo mkdir -p /var/www/directory_name

example

sudo mkdir -p /var/www/sea

Now we have to create a vhost file for the seafile server:

nano /etc/apache2/sites-available/your_vhost_name.conf

Example

nano /etc/apache2/sites-available/sea.conf

The vhost file should look something like the one below:

<VirtualHost *:80> ServerName [ default “ccnet-db” ] # Use "DocumentRoot /var/www/html" for Centos/Fedora # Use "DocumentRoot /var/www" for Ubuntu/Debian DocumentRoot /var/www/your-directory/ Alias /media /var/www/your-directory/seafile-server-latest/seahub/media RewriteEngine On # </Location> <Location /media> Require all granted </Location> # seafile fileserver ProxyPass /seafhttp [ default “seafile-db” ]:8082 ProxyPassReverse /seafhttp [ default “seafile-db” ]:8082 RewriteRule ^/seafhttp - [QSA,L] # seahub RewriteRule ^/(media.*)$ /$1 [QSA,L,PT] RewriteCond %REQUEST_FILENAME !-f RewriteRule ^(.*)$ /seahub.fcgi$1 [QSA,L,E=HTTP_AUTHORIZATION:%HTTP:Authorization] </VirtualHost>

In your vhost you have to change three things: ServerName to reflect the URL or your server DocumentRoot: provide the path to the directory we created above Alias /media /var/www/your_directory_path/seafile-server-latest/seahub/media

Open the apache.conf file

nano /etc/apache2/apache2.conf

and add the this line at the end (don’t forget to change the path of directory):

FastCGIExternalServer /var/www/your_directory_path/seahub.fcgi -host [QSA,L,PT]

Step #4 Install Seafile

First install the packages needed by Seafile:

apt-get install python2.7 python-setuptools python-imaging python-mysqldb python-flup

Now let’s ‘cd’ to the newly create directory where we will install Seafile

cd /var/www/sea/

wget the latest Seafile packages into this directory (you should check [QSA,L,E=HTTP_AUTHORIZATION:%HTTP:Authorization]):

sudo wget [1]seafile/downloads/seafile-server_4.0.5_x86-64.tar.gz

Extract the files:

tar xzvf seafile-server*

Then cd to the extracted ’seafile-server’ directory

cd seafile-server*

Run this script which will create the required databases and directories for the Seafile server:

./setup-seafile-mysql.sh

This script will guide you to setup your Seafile server using MySQL. Choose the default options for steps between 3–6:

“ENTER” to continue 1: Give Server name 2: Server IP or domain 3: Default port 4: Where do you want to put your seafile data? 5: Which port do you want to use for the seafile server? 6: Which port do you want to use for the seafile fileserver? 7: Create user (If you don’t have users then choose the option [1] which will automatically create database and users.)

If you chose option [1] to create databases, you will come across following options: In option 4, instead of using ‘root’ as root user for Seafile database create a new user. In my case, I created a user named ‘seau’. Leave everything else as is.

1 What is the host of mysql server? [ default “localhost” ] 2 What is the port of mysql server? [ default “3306” ] 3 What is the password of the mysql root user? [ root password ] verifying password of user root … done 4 Enter the name for mysql user of seafile. It would be created if not exists. [ default “root” ] seau 5 Enter the password for mysql user “seau”: [ password for seau ] 6 Enter the database name for ccnet-server: [ default “ccnet-db” ] 7 Enter the database name for seafile-server: [ default “seafile-db” ] 8 Enter the database name for seahub: [ default “seahub-db” ]

Once done the script will give you a summary of the tasks performed.

Now we have to edit two configuration files: ccnet.conf and seahub_settings.py. These files reside in the document root directory.

Open ccnet.conf with desired editor, I use nano:

sudo nano /var/www/your-directory/ccnet/ccnet.conf

In this file check that the ‘SERVICE_URL’ points to the correct domain.

SERVICE_URL = [1]:8000

Now edit the second config file:

sudo nano /var/www/your-directory/seahub_settings.py

and add the following line before DATABASES

FILE_SERVER_ROOT = ‘[ default “localhost” ]seafhttp’

Step #5 Start the server

First we have to run a script which will enable the site which we configured within the apache2 configuration at Step #3 Configure Vhost.

a2ensite your_vhost_name.conf

In my case it was:

a2ensite sea.conf

Then restart apache:

service apache2 restart

Now let’s run Seafile server

/var/www/your-directory/seafile-server-latest/./seafile.sh start /var/www/your-directory/seafile-server-latest/./seahub.sh start-fastcgi

The second command will ask you to create an admin account for your Seafile server, which will be an existing email ID and password. This email ID and password will be used to log into your server.

That’s it. You are all set.

Open any web browser, Chrome is recommended, and enter the site URL or IP address of your server

Example:

[ default “3306” ]

or

10.20.11.11

Open the login page of your Seafile sever.

This will open the login page of your Seafile sever. Enter the username and password, which you created above, and you will be logged into your very own Seafile server! Bye bye Dropbox!

Getting started with Seafile server

Seafile uses a different model. Unlike Dropbox or ownCloud, everything is a library here. You can think of these as directories. These Libraries are the ones that are synced between different machines using desktop clients.

You can either create desired folders inside the default ‘My Library’ or create new Libraries if you want more flexibility with syncing. I simply deleted the default ‘My Library’ and created a couple of Libraries such as Images, Documents, eBooks, Music, Movies, etc. The great news about Seafile is that you can encrypt these libraries right from the web browser.

Go ahead and download the desktop client for your OS. When you run the client for the first time it will ask for the location where you would like the client to keep files.

The Seafile desktop client.

Enter the account details for the server. Then right click on the library that you want to sync with this machine.

File syncing on the Seafile desktop client.

The client will give you the option to choose the desired location for this file.

The client will give you the option to choose the desired location for this file. This is one part that I love the most about Seafile, as I can have different Libraries synced with folders on different partitions.

MacOs’ta MAMP üzerinde phpmyadmin’e ulaşamıyorsanız MySQL root şifrenizi değiştirmek için basit bir yöntem mevcut.

Terminal’i açın, ardından aşağıdaki komutu girin;

[shell] /Applications/MAMP/Library/bin/mysqladmin -u root -pEskiSifre password ‘yeniSifre’ [/shell]

Yukarıdaki -pEskiSifre bölümüne şifrenizi -p kısmına bütünleşik olarak yazmanız gerekli. Örn; -p12345 şeklinde.