Jose Cabrera Zuniga's questions

To understand mariadb replication I created the next docker containers:

docker run -e TZ=America/Denver --name mariadb1 --network=camino_nw \
  -e MARIADB_SERVER_ID=1 -e MARIADB_LOG_BIN=mysql-bin -e MARIADB_LOG_BASENAME=mariadb1 \
  -e MARIADB_BINLOG_FORMAT=mixed -p 127.0.0.1:53301:3306 \
  -v /home/jcz/Documents/dockerMariadbData1:/var/lib/mysql:z \
  -e MARIADB_ROOT_PASSWORD=S3cretPw -d mariadb:latest

docker run -e TZ=America/Denver --name mariadb2 --network=camino_nw \
  -e MARIADB_SERVER_ID=2 -e MARIADB_LOG_BIN=mysql-bin -e MARIADB_LOG_BASENAME=mariadb2 \
  -e MARIADB_BINLOG_FORMAT=mixed -p 127.0.0.1:53302:3306 \
  -v /home/jcz/Documents/dockerMariadbData2:/var/lib/mysql:z \
  -e MARIADB_ROOT_PASSWORD=S3cretPw -d mariadb:latest

docker run -e TZ=America/Denver --name mariadb3 --network=camino_nw \
  -e MARIADB_SERVER_ID=3 -e MARIADB_LOG_BIN=mysql-bin -e MARIADB_LOG_BASENAME=mariadb3 \
  -e MARIADB_BINLOG_FORMAT=mixed -p 127.0.0.1:53303:3306 \
  -v /home/jcz/Documents/dockerMariadbData3:/var/lib/mysql:z \
  -e MARIADB_ROOT_PASSWORD=S3cretPw -d mariadb:latest

The master is mariadb1 and for this one I executed:

CREATE USER 'replication_user'@'%' IDENTIFIED BY 'S3cretPw';
GRANT REPLICATION SLAVE ON *.* TO 'replication_user'@'%';

For each of the slaves mariadb2 and mariadb3 I run:

CHANGE MASTER TO MASTER_HOST='mariadb1',  MASTER_USER='replication_user',  MASTER_PASSWORD='S3cretPw',  MASTER_PORT=3306, MASTER_CONNECT_RETRY=10;

CHANGE MASTER TO MASTER_USE_GTID = slave_pos;

I also started the slaves with START SLAVE;

After running the

SHOW SLAVE STATUS \G 

I got the next error:

         Last_IO_Error: Fatal error: The slave I/O thread stops because master and slave have equal MariaDB server ids; these ids must be different for replication to work (or the --replicate-same-server-id option must be used on slave but this does not always make sense; please check the manual before using it).

How can this happen if I used

MARIADB_SERVER_ID=1
MARIADB_SERVER_ID=2
MARIADB_SERVER_ID=3

for each of my containers?

I am trying to follow:

https://mariadb.com/kb/en/setting-up-replication/

I have a Centos 7 QEMU-KVM virtual machine located at a Centos 7 physical server. Both are in a network that uses vlan ids. Also the Network Admin Guy told me to assign the VLanId 33 to the Virtual machine. Because of this, the virtual machine can not have internet access unless I assign this VM the proper VLanId. At the host I also installed QEMU-KVM using:

sudo yum install qemu-kvm qemu-img virt-manager libvirt libvirt-python libvirt-client virt-install virt-viewer bridge-utils

I also added my account to the libvirt group to be able to run the virt-manager using ssh with:

usermod --append --groups libvirt `whoami`

From:

https://serverfault.com/questions/868093/vms-on-a-kvm-host-with-tagged-vlans

I saw: "tagging VMs isn't inside the VM itself, it's by creating tagged interfaces on the host, creating bridges on top of those tagged interfaces (so you have something like a tagged v-switch) and plugging the VMs into those tagged bridges"

So, I have some questions:

a) What I need to have installed in the Centos 7 physical host to create tagged interfaces within the host itself?

b) How do I create bridges on top of those tagged interfaces?

c) How do I plug the QEMU-KVM Virtual Machine into those tagged bridges?

d) Is there any software/hardware I could use to experiment with the solutions to a)-c)? I do not want to put in risk the production Centos 7 host to test the needed configuration.

Thx

I have a server named as servername.mydomain.com. I can do ssh to this server using a port number X using:

ssh  [email protected] -p X

From this server I can run:

psql -h localhost -d myDatabase -U myusername -p DBPORT

Instead of having to login using ssh I want to be able to use psql as:

psql -h servername.mydomain.com:X -d myDatabase -U myusername -p DBPORT

Is this possible? I tried this but I am getting the message: could not translate hostname ...

To install impala in a Docker container (that use Ubuntu 16.04) I followed:

https://cwiki.apache.org/confluence/display/IMPALA/Building+Impala

(Section: Building Impala (for developing Impala)). At some point of the installation I saw:

Does anyone knows what this message is about? I ended pressing my ESC key and :wq to allow the installation to continue but this left me intrigued.

I deployed the latest version of Apache Impala from:

http://www.apache.org/dyn/closer.cgi?action=download&filename=impala/3.3.0/apache-impala-3.3.0.tar.gz

and to see its used ports I used netstat -- listen (see below). Instead of 21000 I tried to use 31000 as the used ports by Impala are described at:

https://www.cloudera.com/documentation/enterprise/5-14-x/topics/impala_ports.html

but could not connect from an impala-shell located at another computer (Tried 21000 but failed, too). Am I missing something? The impala daemon is running as if I do

root@bb9f4792e21d:/opt/Impala/bin# ps -ef | grep -i impalad
root     23067     1  0 15:31 pts/0    00:00:00 grep --color=auto -i impalad

I can see it is running.

root@bb9f4792e21d:/opt/Impala/bin# netstat --listen
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State      
tcp        0      0 *:11050                 *:*                     LISTEN     
tcp        0      0 *:16010                 *:*                     LISTEN     
tcp        0      0 *:7051                  *:*                     LISTEN     
tcp        0      0 localhost:31020         *:*                     LISTEN     
tcp        0      0 localhost:31021         *:*                     LISTEN     
tcp        0      0 *:5070                  *:*                     LISTEN     
tcp        0      0 localhost:31022         *:*                     LISTEN     
tcp        0      0 *:30130                 *:*                     LISTEN     
tcp        0      0 *:10002                 *:*                     LISTEN     
tcp        0      0 *:8051                  *:*                     LISTEN     
tcp        0      0 localhost:16020         *:*                     LISTEN     
tcp        0      0 localhost:20500         *:*                     LISTEN     
tcp        0      0 localhost:16022         *:*                     LISTEN     
tcp        0      0 *:ssh                   *:*                     LISTEN     
tcp        0      0 localhost:16023         *:*                     LISTEN     
tcp        0      0 *:31000                 *:*                     LISTEN     
tcp        0      0 localhost:postgresql    *:*                     LISTEN     
tcp        0      0 *:31001                 *:*                     LISTEN     
tcp        0      0 *:30010                 *:*                     LISTEN     
tcp        0      0 *:31002                 *:*                     LISTEN     
tcp        0      0 *:9083                  *:*                     LISTEN     
tcp        0      0 localhost:45979         *:*                     LISTEN     
tcp        0      0 *:16030                 *:*                     LISTEN     
tcp        0      0 localhost:30911         *:*                     LISTEN     
tcp        0      0 *:6080                  *:*                     LISTEN     
tcp        0      0 *:16032                 *:*                     LISTEN     
tcp        0      0 localhost:16000         *:*                     LISTEN     
tcp        0      0 localhost:31200         *:*                     LISTEN     
tcp        0      0 *:9600                  *:*                     LISTEN     
tcp        0      0 *:16033                 *:*                     LISTEN     
tcp        0      0 localhost:31201         *:*                     LISTEN     
tcp        0      0 localhost:37857         *:*                     LISTEN     
tcp        0      0 localhost:31202         *:*                     LISTEN     
tcp        0      0 *:31010                 *:*                     LISTEN     
tcp        0      0 *:31011                 *:*                     LISTEN     
tcp        0      0 *:30020                 *:*                     LISTEN     
tcp        0      0 *:31300                 *:*                     LISTEN     
tcp        0      0 *:31012                 *:*                     LISTEN     
tcp        0      0 localhost:6085          *:*                     LISTEN     
tcp        0      0 *:2181                  *:*                     LISTEN     
tcp        0      0 *:31301                 *:*                     LISTEN     
tcp        0      0 localhost:42213         *:*                     LISTEN     
tcp        0      0 *:31302                 *:*                     LISTEN     
tcp        0      0 127.0.0.11:45001        *:*                     LISTEN     
tcp6       0      0 [::]:ssh                [::]:*                  LISTEN     
udp        0      0 bb9f4792e21d:ntp        *:*                                
udp        0      0 localhost:ntp           *:*                                
udp        0      0 *:ntp                   *:*                                
udp        0      0 127.0.0.11:39611        *:*                                
udp6       0      0 [::]:ntp                [::]:*                             
Active UNIX domain sockets (only servers)
Proto RefCnt Flags       Type       State         I-Node   Path
unix  2      [ ACC ]     STREAM     LISTENING     40977947 /var/lib/hadoop-hdfs/socket.31001
unix  2      [ ACC ]     STREAM     LISTENING     40872735 /var/run/postgresql/.s.PGSQL.5432
unix  2      [ ACC ]     STREAM     LISTENING     40975999 /var/lib/hadoop-hdfs/socket.31000
unix  2      [ ACC ]     STREAM     LISTENING     40977072 /var/lib/hadoop-hdfs/socket.31002
root@bb9f4792e21d:/opt/Impala/bin# 

I have been deploying tomcat 8.5.45 on a Centos 7 docker container. I deployed and after setting the logs to Fine I found an Error parsing HTTP header error every time I use:

http://localhost:8080

I have the feeling this error is related to my server.xml file. What could cause from my server.xml file to get the next error:

    03-Sep-2019 21:05:39.781 INFO [http-nio-8080-exec-2] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header
     Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.
        java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
            at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:430)
            at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:682)
            at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
            at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:810)
            at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1498)
            at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
            at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
            at java.lang.Thread.run(Thread.java:748)

Server.Xml Contents:

<?xml version="1.0" encoding="UTF-8"?>
<!--
  Licensed to the Apache Software Foundation (ASF) under one or more
  contributor license agreements.  See the NOTICE file distributed with
  this work for additional information regarding copyright ownership.
  The ASF licenses this file to You under the Apache License, Version 2.0
  (the "License"); you may not use this file except in compliance with
  the License.  You may obtain a copy of the License at

      http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an "AS IS" BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.
-->
<!-- Note:  A "Server" is not itself a "Container", so you may not
     define subcomponents such as "Valves" at this level.
     Documentation at /docs/config/server.html
 -->
<Server port="8005" shutdown="SHUTDOWN">
  <Listener className="org.apache.catalina.startup.VersionLoggerListener" />
  <!-- Security listener. Documentation at /docs/config/listeners.html
  <Listener className="org.apache.catalina.security.SecurityListener" />
  -->
  <!--APR library loader. Documentation at /docs/apr.html -->
  <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" />
  <!-- Prevent memory leaks due to use of particular java/javax APIs-->
  <Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener" />
  <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
  <Listener className="org.apache.catalina.core.ThreadLocalLeakPreventionListener" />

  <!-- Global JNDI resources
       Documentation at /docs/jndi-resources-howto.html
  -->
  <GlobalNamingResources>
    <!-- Editable user database that can also be used by
         UserDatabaseRealm to authenticate users
    -->
    <Resource name="UserDatabase" auth="Container"
              type="org.apache.catalina.UserDatabase"
              description="User database that can be updated and saved"
              factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
              pathname="conf/tomcat-users.xml" />
  </GlobalNamingResources>

  <!-- A "Service" is a collection of one or more "Connectors" that share
       a single "Container" Note:  A "Service" is not itself a "Container",
       so you may not define subcomponents such as "Valves" at this level.
       Documentation at /docs/config/service.html
   -->
  <Service name="Catalina">

    <!--The connectors can use a shared executor, you can define one or more named thread pools-->
    <!--
    <Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
        maxThreads="150" minSpareThreads="4"/>
    -->


    <!-- A "Connector" represents an endpoint by which requests are received
         and responses are returned. Documentation at :
         Java HTTP Connector: /docs/config/http.html
         Java AJP  Connector: /docs/config/ajp.html
         APR (HTTP/AJP) Connector: /docs/apr.html
         Define a non-SSL/TLS HTTP/1.1 Connector on port 8080
    -->
    <Connector port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" />
    <!-- A "Connector" using the shared thread pool-->
    <!--
    <Connector executor="tomcatThreadPool"
               port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" />
    -->
    <!-- Define a SSL/TLS HTTP/1.1 Connector on port 8443
         This connector uses the NIO implementation. The default
         SSLImplementation will depend on the presence of the APR/native
         library and the useOpenSSL attribute of the
         AprLifecycleListener.
         Either JSSE or OpenSSL style configuration may be used regardless of
         the SSLImplementation selected. JSSE style configuration is used below.
    -->
    <!--
    <Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol"
               maxThreads="150" SSLEnabled="true">
        <SSLHostConfig>
            <Certificate certificateKeystoreFile="conf/localhost-rsa.jks"
                         type="RSA" />
        </SSLHostConfig>
    </Connector>
    -->
    <!-- Define a SSL/TLS HTTP/1.1 Connector on port 8443 with HTTP/2
         This connector uses the APR/native implementation which always uses
         OpenSSL for TLS.
         Either JSSE or OpenSSL style configuration may be used. OpenSSL style
         configuration is used below.
    -->
    <!--
    <Connector port="8443" protocol="org.apache.coyote.http11.Http11AprProtocol"
               maxThreads="150" SSLEnabled="true" >
        <UpgradeProtocol className="org.apache.coyote.http2.Http2Protocol" />
        <SSLHostConfig>
            <Certificate certificateKeyFile="conf/localhost-rsa-key.pem"
                         certificateFile="conf/localhost-rsa-cert.pem"
                         certificateChainFile="conf/localhost-rsa-chain.pem"
                         type="RSA" />
        </SSLHostConfig>
    </Connector>
    -->

    <!-- Define an AJP 1.3 Connector on port 8009 -->
    <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" />


    <!-- An Engine represents the entry point (within Catalina) that processes
         every request.  The Engine implementation for Tomcat stand alone
         analyzes the HTTP headers included with the request, and passes them
         on to the appropriate Host (virtual host).
         Documentation at /docs/config/engine.html -->

    <!-- You should set jvmRoute to support load-balancing via AJP ie :
    <Engine name="Catalina" defaultHost="localhost" jvmRoute="jvm1">
    -->
    <Engine name="Catalina" defaultHost="localhost">

      <!--For clustering, please take a look at documentation at:
          /docs/cluster-howto.html  (simple how to)
          /docs/config/cluster.html (reference documentation) -->
      <!--
      <Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/>
      -->

      <!-- Use the LockOutRealm to prevent attempts to guess user passwords
           via a brute-force attack -->
      <Realm className="org.apache.catalina.realm.LockOutRealm">
        <!-- This Realm uses the UserDatabase configured in the global JNDI
             resources under the key "UserDatabase".  Any edits
             that are performed against this UserDatabase are immediately
             available for use by the Realm.  -->
        <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
               resourceName="UserDatabase"/>
      </Realm>

      <Host name="localhost"  appBase="webapps"
            unpackWARs="true" autoDeploy="true">

        <!-- SingleSignOn valve, share authentication between web applications
             Documentation at: /docs/config/valve.html -->
        <!--
        <Valve className="org.apache.catalina.authenticator.SingleSignOn" />
        -->

        <!-- Access log processes all example.
             Documentation at: /docs/config/valve.html
             Note: The pattern used is equivalent to using pattern="common" -->
        <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
               prefix="localhost_access_log" suffix=".txt"
               pattern="%h %l %u %t &quot;%r&quot; %s %b" />

      </Host>
    </Engine>
  </Service>
</Server>

I want to create a docker container to install Tomcat within it. It seems that my docker compiles with no problem and I am also able to run tomcat with no problems reported through the logs. Yet, if I try to open tomcat I get a 404 error. I do not know what I am missing. Any ideas, please? The next is the content of my Dockerfile:

FROM centos:7
MAINTAINER joseccz

EXPOSE 8080
EXPOSE 8009


RUN yum install -y mc
RUN yum install -y wget
# RUN yum install -y apr-devel openssl-devel
RUN yum install -y gcc
RUN yum install epel-release -y
RUN yum install dnf -y
RUN yum install net-tools -y
RUN yum install libtool -y

ENV JAVA_HOME       /opt/javaSDK
ENV JRE_HOME        ${JAVA_HOME}/jre

ADD javaSDK ${JAVA_HOME}

ADD tomcat.service /etc/systemd/system/




# ----------------------------------------------- Copy Tomcat Files to /opt/tomcat -----------------------------------------------
ENV TOMCAT_MAJOR 8
ENV TOMCAT_VERSION 8.5.45
ENV CATALINA_HOME   /opt/tomcat

# http://www-us.apache.org/dist/tomcat/tomcat-8/v8.5.45/bin/apache-tomcat-8.5.45.tar.gz

ENV PATH        $JAVA_HOME/bin:$CATALINA_HOME/bin:$CATALINA_HOME/lib:$PATH

RUN wget http://www-us.apache.org/dist/tomcat/tomcat-${TOMCAT_MAJOR}/v${TOMCAT_VERSION}/bin/apache-tomcat-${TOMCAT_VERSION}.tar.gz && \
 tar -xvf apache-tomcat-${TOMCAT_VERSION}.tar.gz 

RUN mv apache-tomcat-${TOMCAT_VERSION} tomcat

RUN rm apache-tomcat*.tar.gz
RUN mv tomcat /opt/tomcat
# --------------------------------------------------------------------------------------------------------------------------------



RUN groupadd tomcat
RUN useradd -s /bin/nologin -g tomcat -d /opt/tomcat tomcat

# RUN wget https://rpmfind.net/linux/mageia/distrib/cauldron/x86_64/media/core/release/tomcat-native-1.2.23-1.mga8.x86_64.rpm
# RUN rpm -i tomcat-native-1.2.23-1.mga8.x86_64.rpm

# RUN cd /opt/tomcat
RUN chgrp -R tomcat /opt/tomcat/conf
RUN chmod g+rwx /opt/tomcat/conf
RUN chmod g+r /opt/tomcat/conf/*
RUN chown -R tomcat /opt/tomcat/logs/ /opt/tomcat/temp/ /opt/tomcat/webapps/ /opt/tomcat/work/

RUN chgrp -R tomcat /opt/tomcat/bin
RUN chgrp -R tomcat /opt/tomcat/lib
RUN chmod g+rwx /opt/tomcat/bin
RUN chmod g+r /opt/tomcat/bin/*

#----------------------------------Create /opt/software folder for addinitonal soft needed by Tomcat ------------------------------
RUN mkdir /opt/software

#---------------------------------------- copy and compile Development tools ---------------------------------------------------------

RUN yum groupinstall "Development Tools" -y

#---------------------------------------- Donwload and install open ssl ------------------------------------------------------------
RUN wget https://www.openssl.org/source/openssl-1.0.2l.tar.gz
RUN tar -xvf openssl-1.0.2l.tar.gz
RUN mv openssl-1.0.2l openssl
RUN mv openssl /opt/software/openssl
RUN cd /opt/software/openssl && ./config -fPIC --prefix=/opt/software/ --openssldir=/opt/software/ && make && make install

#---------------------------------------- Donwload and install open apr ------------------------------------------------------------
ENV APRVERSION 1.6.5
RUN wget http://apache.mirrors.ionfish.org//apr/apr-${APRVERSION}.tar.gz
RUN tar -xvf apr-${APRVERSION}.tar.gz
RUN mv apr-${APRVERSION} apr
RUN mv apr /opt/software/apr
RUN cd /opt/software/apr/ && \
    ./configure --prefix=/opt/software/ && \
     make && make install

#------------------------------------------ Copy TOMCAT native


# compiling tomcat native

RUN cd ${CATALINA_HOME}/bin/ && \
    tar -xvf tomcat-native.tar.gz && \
    cd tomcat-native-1.2.23-src/native/ && \
     ./configure --with-apr=/opt/software/ --with-java-home=/opt/javaSDK/  --with-ssl=/opt/software  --prefix=/opt/tomcat && \
    make && \
    make install

ADD setenv.sh /opt/tomcat/bin/

my setenv.sh file content is:

export JAVA_HOME=/opt/javaSDK
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$CATALINA_HOME/lib
export LD_LIBRARY_PATH

I have a postgress database installed in a Docker container called dbDocker. This container is not using any of the server ports and the container's port for postgres 5342 is only visible from containers in the same virtual network. I want to create another docker container to allow users out of the network to contact that database. Is it possible to do this? So, this new container will appear as the one having the database.

Thanks

I am trying to use nginx in a docker container. I created a configuration file that works with / but not with /team/soccer (I need this). In this case it goes to the site that is located on the server that contains the docker machines. Am I missing something? myserver is the name of a docker container that contains the site I need to open. docker_nginx is the name of the docker that contains nginx. All the docker machines are within a docker network. The next is the nginx.conf file:

    events {
  worker_connections 1024; # increase if you have lots of clients
  accept_mutex off; # "on" if nginx worker_processes > 1
  # use epoll; # enable for Linux 2.6+
  # use kqueue; # enable for FreeBSD, OSX
}

http {
#   proxy_buffering    off;    <- don't forget to comment out or remove this line.
    proxy_set_header   X-Real-IP $remote_addr;
    proxy_set_header   X-Scheme $scheme;
    proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header   Host $http_host;
    # proxy_cache_path   /var/lib/nginx/cache levels=1:2 keys_zone=one:1000m;
    proxy_cache_methods GET HEAD;
    proxy_cache_key $host$uri$is_args$args;
    proxy_cache_valid 200 10m;

# Do gzip compression with nginx, not the play application
    gzip on;
    gzip_comp_level 9;
    gzip_proxied any;

# This is important if you use Play chunked response as chunked response is only available with HTTP 1.1
    proxy_http_version 1.1;

    upstream mybackend {
        server myserver:9000;
    }

    include       /etc/nginx/mime.types;
    default_type  application/octet-stream;

    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for"';

    access_log  /var/log/nginx/access.log  main;

    sendfile        on;

    keepalive_timeout  65;

    index   index.html index.htm;

    server {
        listen       docker_nginx:80;
        #server_name  docker_nginx;

        location / {
            proxy_buffering off;
            proxy_pass http://mybackend;
        }

        location /team/soccer {
            proxy_buffering off;
            proxy_pass http://mybackend;
        }

 #       location ~ ^/(assets|webjars)/ {
 #           # proxy_cache one;
 #           proxy_cache_key "$host$request_uri";
 #           proxy_cache_valid 200 30d;
 #           proxy_cache_valid 301 302 10m;
 #           proxy_cache_valid 404 1m;

 #           proxy_pass http://backend;
#        }
    }

}

I am able to access the website of a server (running Linux Mint 18 Sylvia) that uses an http like:

http://myserver.house.pckhrest.edu

I can not do remote connection to myserver.house.pckhrest.edu but if I use its IP adddress then I can do the remote connection. I can ping this ip address but I can not ping using myserver.house.pckhrest.edu.

Is there any ufw firewall setting I am missing? I am trying to test my app and do remote web development.

Error messages:

• If I try to use myserver.house.pckhrest.edu for RDP I get the message: 'Error connecting to host'.
• For ping I get ping: unknown host

But if I use the IP address all goes through.