How to configure FTP in Centos 7.2 + VestaCP?

Question

Java

Good afternoon.
I made a web server based on windows server 2012 r2 + Hyper-V (on which Centos 7.2 + VestaCP runs on a virtual machine). My server connects to the network through a router. White static ip is used.
Using port forwarding on the router, I made the sites (running on the Centos 7.2 + VestaCP virtual machine) accessible from the outside.
How do I set up or replace FTP (so that it works on port 21)? because I can connect to FTP only on port 22, and for example, to add plugins to the same Worpress, I need connection data and port 21.
When trying to connect on port 21, it says:
Status: Connection established, waiting for an invitation ...
Status: Insecure server, does not support FTP over TLS.
Status: Logged in
Status: Getting directory listing...
And nothing else happens.

Answer 1

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder":
if slf4j is not needed, then this error does not affect the operation of the application itself.
Eksepshn crashes for a different reason. Show the hibernate config.

Caused by: org.hibernate.MappingException: Unable to load class [ entity.Article] declared in Hibernate configuration <mapping/> entry
Caused by: java.lang.ClassNotFoundException: entity.Article

Judging by the stackcase in the hibernate config in the mapping section, the entity.Article class is declared, which is not (at least you didn’t attach it)
by SLF4J error:
everything is clear here in principle.
look, delete from pom.xml

<dependency>
        <groupId> org.apache.cassandra</groupId>
        <artifactId>cassandra-all</artifactId>
        <version>0.8.1</version>

        <exclusions>
            <exclusion>
                <groupId>org.slf4j</groupId>
                <artifactId>slf4j-log4j12</artifactId>
            </exclusion>
            <exclusion>
                <groupId>log4j</groupId>
                <artifactId>log4j</artifactId>
            </exclusion>
        </exclusions>

    </dependency>

As I understand it, you pasted this code by copying it from the slf4j website, if so, then it is not needed here.
hibernate-core library - uses slf4j in order to be able to cut any logger (log4j, logback and others) and then hibernate would write his messages to it.
The fact that this message pops up is not an error in principle. Just for this example, the logger is not installed. If it was installed then everything would be fine.
However, the slf4j site says that adding a dependency to pom.xml will be enough to avoid this error.

<dependency>
        <groupId>org.slf4j</groupId>
        <artifactId>slf4j-nop</artifactId>
        <version>1.7.13</version>
    </dependency>

If this does not help, then you just need to include logback or log4j and configure it. How to do this is easy to find on the net.

Answer 2

disable ftp tls in connection settings