Creating Your First Web Account in ISPConfig Server Configuration (page 2)

botond published 2018/07/28, Sat - 02:38 time

2. page content

 

The description on the first page we've done most of the task, but there are still a few things to do.

 

 

Create a Shell user

Shell In most cases, the user is not needed to run an average website, but since the site mainly deals with command line solutions and background tasks, the forthcoming tutorials will be based on this, so we will need it later.

There is another very big advantage if we have a shell user: It becomes one with the user SFTP connection, so we do not need to create separate FTP accounts, but can also move files between our computer and the storage via this encrypted SFTP connection. The only small drawback is that not all clients support SFTP. For example, Total Commander cannot connect by default either, but different dlls must be copied into the TC directory in order for it to work. However, a FileZilla can easily access these SFTP accounts without further ado.

To create a shell user, go to ISPConfig Sites main menu Shell-User submenu where it is Add new Shell-User button to start filling out the form:

Shell User tab

Create a Web Account in ISPConfig - Create a Shell User

  • Website: Select the web page for which you want to create a shell user.
  • Username: Here the client prefixes the name with the username, so I enter the name "_testpage" here, which becomes "linuxportal_testpage". Here, a customer can have several websites and any number of customers, so it is necessary to prefix the names here as well.
  • Password: It's a good idea to choose a password that is easy to remember and type in, because it makes it easier for you to enter the terminal. I save the password of my choice in the standard /root/access.txt file.
  • Chroot Shell: If you want to chroot the user, here you can select the JailKit system. But if you are the server itself and you do not need to share the system with others, you do not need chroot. So I'm not turning it on here.
  • Quote: Leaving this on -1, no need for storage limit in the shell user's home directory.
  • SSH-RSA Public Key: Here you can place a public key for your shell user account in case you want to be able to log in without a password. I've made one about this before description, executed from the command line only.
    Leave it blank now.
  • active: Pipe.

Options tab

Go to the Options tab of the form where you can check or modify your user's most important parameters:

Creating a Web Account in ISPConfig - Shell User Options

There's nothing to do here, just run through the fields to see what they mean.

  • Web Username: This will be your real Linux username. What we gave in the previous page is just an entry alias. In fact, in the system, this "web1" user and "client1" group will own the file structure of the web account. This method allows you to create multiple shell aliases for a web account, for example, if multiple people are working on the same account. Furthermore, the PHP-FPM is also launched on behalf of this user PHP processes when someone loads the web page that resides in that browser into their browser.
  • Web Group: This is the Linux group.
  • Shell: This is the path to our shell user's shell shell, the usual / bin / bash. If you want to use another shell, you should enter its path here.
  • Base Dir: This is the "base" directory of the account, also known as document root (document root, docroot) library. ISPConfig has compiled everything you need to run this account into this directory, and the web root itself opens from this directory (./web), which is accessible from the outside.

Save the form. With this, our shell user is ready. The user account is encrypted SSH we can enter through a connection.

 

Create an FTP Account (Optional)

For the shell user, we negotiated that the user would automatically "get" an SFTP connection (not to be confused with FTPS!), Which is a nice way to upload and download files from storage. However, there are times when you just need to create a traditional FTP account. For example, if you want to allow others to upload files to our site, or just want an FTP connection that is limited to a single subdirectory, etc. In such cases, it is advisable to create one (or more) traditional FTP accounts, even for each authorized user.

However, it is good to know that a plain FTP connection does not use encryption, so if we need to upload / download something very confidential, unauthorized people can access our data by eavesdropping on the channel (the section between our computer and our web host). Therefore, we need to consider which solution we choose.

To create an FTP account, log in to Sites main menu FTP Accounts submenu, where you can start filling out the form with the usual green create button:

FTP User tab

Creating a Web Account in ISPConfig - FTP User

  • Website: Standard Website Selection Box ...
  • Username: Again, the names are prefixed, so I have a "linuxportal test page"
  • Password: I saved the generated password to the standard /root/access.txt file
  • Harddisk-Quota: No limit, -1
  • active: Pipa

Options tab

Creating a Web Account in ISPConfig - FTP User Options

  • User identifier (UID): For the Linux user, leave it filled in.
  • Group identifier (GID): For the Linux group, leave it filled
  • Directory: This is the root directory of the FTP account. Cannot access FTP at this directory level.
    The default is here / Var / www / clients / client1 / web1 there was a library, which is the document directory for the repository. I put the web root behind it, so it was / Var / www / clients / client1 / web1 / web. I find it safer that with a plain FTP account you can only access the root of the web, such as uploading web page content, and managing the document library one level up via SFTP. Of course tastes and slaps, everyone adjusts it as needed.

Other fields are left at the factory default. These apply to storage limits and FTP speeds. We do not set a limit anywhere. Finally, save the form.

So we now have an FTP account pointing to the web root. This allows us to easily upload a complete website to the hosting.

 

 

DNS settings

DNS settings are only needed for a live server, so now we'll cover this topic.

Entering ISPConfig DNS we have several options in our main menu:

Creating a Web Account in ISPConfig - DNS Settings

Here you can create the DNS zone wizard, manually create it, or you can even import the zone file from other systems.

If you click on the "Add new DNS Zone with Wizard" button, the first form of the wizard will appear, with which you can start the DNS setup process. I have previously made the For a detailed description of DNS setup, where I set up the DNS zone for this website. So if you want to set up your server for live use, this description will provide a lot of information for anyone.

 

Create email accounts

Email accounts are also only needed for live use, but we’ll look at how to create an email account.

Let's step in Email main menu where it is Email Domain part receives us. Click the Add New Domain button and the following form will appear:

Creating a Web Account in ISPConfig - Creating an Email Domain

To create email addresses, you first need to add an Email domain, and then we can link different email accounts for this. Fill out the form accordingly:

  • Server: Standard server selection field
  • Client: Set up the Client to whom the email domain you want to create belongs.
  • Domain: Here, enter the exact same domain name that you set when creating the webhost, for me, "test page.local"
  • spamfilter: Here you can choose from a variety of predefined SPAM filtering strategies. I'm leaving this off for now.
  • active: Pipa

Save the form.

 

You may be wondering what this step was when we once created a domain and a full account. Well, the point is quite logical: ISPConfig handles email-related domains and hosting-related domains separately. This is because the control panel can only perform email functions without any storage space. So, for example, if you have a domain name that you only want to use for receiving emails, then you don't have to create a full webhost, but just an email domain with the aliases. Then, on the registrar side, you need to set up an MX record redirect to the server and the mail server is ready.

 

After creating the email domain, you can now add email addresses to it Email Mailbox by clicking on the green button labeled "Add new Mailbox" in the submenu:

Mailbox tab

Creating a Web Account in ISPConfig - Creating an Email Address - Mailbox Tab

Here we are creating an admin email account for our test page, which will be dealt with later in the tutorials.

As you can see ISPConfig has a fairly rich feature set, let's go through the fields:

  • Name: Mailbox name, it appears at the sender, etc. (it's not neccessary)
  • Email: Pre-magpie email address member. Here I set the name "admin". Also, in the post-worm section, the drop-down box already sets up the email domain you previously added. Or, if you have multiple domains, you can choose which one you want to create the account for.
  • Password: I also store this in the access.txt file that I set up here.
  • Quote: Hosting-letter limit. Leave on 0 (no limit)
  • Send copy to: Here you can specify auto-copy addresses to which all outgoing mail will be sent.
  • Send outgoing BCC to: Here, too, you can enter the outgoing Bcc addresses.
  • spamfilter: Option to set SPAM filter.
  • Enable receiving: Allow mail to be received. Pipe.
  • Disable SMTP: Disable outgoing mail. Leave it blank.
  • Enable greylisting: Enable gray listing
  • Disable IMAP: IMAP Disabling
  • Disable POP3: Disable POP3

Autoresponder tab

Creating a Web Account in ISPConfig - Creating an Email Address - Autoresponder Tab

Here you can set up automatic answers. There's nothing to do now, just run through:

  • Email subject: Subject of reply letter
  • Text: letter text
  • Enable the autoresponder: Enable reply message
  • Start on: Auto-reply from this time 
  • End by: Auto-reply until now

Mail Filter tab

Creating a Web Account in ISPConfig - Creating an Email Address - Mail Filter Tab

Here you can configure spam emails to be immediately trashed. Also, during the setup, another list will appear, where you can add filter rules per item. Clicking the green "Add new Filter" button will bring up another form to define the filter rule:

Creating a Web Account in ISPConfig - Creating an Email Address - Creating a New Filter

  • Name: Name of filter rule
  • Source: Here you can choose where to look at the pattern (Subject, From, To)
    Here is another dropdown where we can select the pattern fit:
    • contains: Includes sample
    • also: Exactly the same as the pattern
    • Begins with: It starts with the pattern
    • Ends with: It ends with a pattern
    Then you have to enter the pattern below in the next field.
  • Action: Here you can choose what to do with the filter when you find it: Move mail to the folder specified in the box below, or delete it.
  • active: Make sure the filter is in use.

We are not setting a filter here now, we have just reviewed it, so click on cancel and then go to the next tab.

Custom Rules tab

Creating a Web Account in ISPConfig - Creating an Email Address - Custom Rules tab

Here we are greeted by a single field where we can write our unique mail filter recipes. Refer to the documentation for the mail server (Dovecot or Courier) running on the server for recipe syntax.

Backup tab

Creating a Web Account in ISPConfig - Creating an Email Address - Backup Tab

  • Backup interval: Here you can choose from what drop-down intervals your emails should be saved (no backup, daily, weekly, monthly)
  • Number of backup copies: Here you can set the number of copies to back up.

It makes the compressed save files available in this list, from where we can then download, and so on.

There's nothing else to do right now, so just save the form eventually. After saving, you will be returned to the mailbox list of the Mailbox, where you can see the email addresses you have created.

 

 

Testing your hosting

When all is done, all you have to do is test your storage to see if everything is done well. The easiest way to do this is to enter the IP address of our server in the address bar of your browser:  http://192.168.1.120. And the ISPConfig welcome panel comes in.

 

Of course, this only works if there is no other web page on the server that comes in alphabetical order. By default, if you enter the IP address of the server in your browser, the Apache server running on the server will look for the first virtualhost in the list, / Etc / apache2 / sites-enabled in the library that it loads nicely. So, if this is our first web account, it will load on an exclusive basis by entering the IP address.

 

However, there is a much more elegant solution to this, which is to run the right web page in our browser. This is the use of the hosts file. If you want to access the appropriate web page from the server on a Linux machine, it is etc / hosts file, and on a Windows machine, open c: \ Windows \ System32 \ drivers \ etc \ hosts file must be edited. The format is the same for both, so use either system, put the following two lines at the end of the hosts file:

192.168.1.120   tesztoldal.local
192.168.1.120   www.tesztoldal.local

Of course, if you access our server with a different IP address, you must enter it.

Then we type in our browser that http://tesztoldal.local vagy http://www.tesztoldal.local, the webpage on the storage will load in the same way. In this case, in the newly created storage space, the ISPConfig welcome panel:

Creating a Web Account in ISPConfig - Testing Your Storage - ISPConfig Welcome Screen

 

 

Conclusion

So we've done the basics of creating a new web account, but in addition, ISPConfig includes a number of other settings that you can use to fine-tune different corners of your account. However, these settings usually have to be made while running the given website, because they depend on the type of website.

Our web hosting is now ready to run any PHP-based dynamic web site that can be uploaded via FTP or installed from a terminal.

 

What's next?

Once you’ve set up your hosting and set everything up, the next step is to redirect your domain name to your server. To do this, we will also need a secondary name server, without which name server-based redirection will not work. The essence of name server-based redirection is that we have to specify at least 2 name servers in the domain management interface (where we registered the domain name). After this, ISPConfig on our server will handle the entire DNS zone. So we will also have correspondence, etc. If we run our own server, we usually don’t have a secondary name server because we only have one server. Therefore, in this case, we have to solve this ourselves so that the domain can be redirected. About the implementation of this one another specification get information. 

Then the in the next section, we will install a fresh Drupal on the storage CMS system, which will be the subject of later related tutorials.

Also, if you already have a working website, I recommend Matomo (Piwik) web analytics system installation is.

 

 

Navigation

This description consists of several pages: