Nginx: one minute after startup my Nginx failed

[rthamrin]

hi everyone. this is so strange for me.

1. my Nginx is running only a few seconds when bootup? how do I know?
   while bootup I try to ssh my server and run curl localhost, while I run the command, my index.html page showed. Welcome to
   Nginx.... and so on, everything is normal. when one minute later, I tried to run curl localhost again and it took about 5 minutes and showed curl: (28) Failed to connect to localhost port 80: Connection timed out

2. I disable Traefik already because somehow Traefik uses port 80
   what actually happens? any services use port 80
   in my, Nginx log nothing show something error.

I conclude something to run, when Nginx is run, one minute later there is service kill the Nginx.

this is my service in K3S

# kubectl get service --all-namespaces
NAMESPACE       NAME                                 TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)                      AGE
default         kubernetes                           ClusterIP   10.43.0.1      <none>        443/TCP                      37d
kube-system     kube-dns                             ClusterIP   10.43.0.10     <none>        53/UDP,53/TCP,9153/TCP       37d
kube-system     metrics-server                       ClusterIP   10.43.42.85    <none>        443/TCP                      37d
ingress-nginx   ingress-nginx-controller-admission   ClusterIP   10.43.69.64    <none>        443/TCP                      2d8h
ingress-nginx   ingress-nginx-controller             NodePort    10.43.91.127   <none>        80:31065/TCP,443:30174/TCP   2d8h
#

nginx configuration, i don't do any change

user www-data;
worker_processes auto;
pid /run/nginx.pid;
include /etc/nginx/modules-enabled/*.conf;

events {
        worker_connections 768;
        # multi_accept on;
}

http {

        ##
        # Basic Settings
        ##

        sendfile on;
        tcp_nopush on;
        types_hash_max_size 2048;
        # server_tokens off;

        # server_names_hash_bucket_size 64;
        # server_name_in_redirect off;

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

        ##
        # SSL Settings
        ##

        ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3; # Dropping SSLv3, ref: POOD                                                                                                             LE
        ssl_prefer_server_ciphers on;

        ##
        # Logging Settings
        ##

        access_log /var/log/nginx/access.log;
        error_log /var/log/nginx/error.log;

        ##
        # Gzip Settings
        ##

        gzip on;

        # gzip_vary on;
        # gzip_proxied any;
        # gzip_comp_level 6;
        # gzip_buffers 16 8k;
        # gzip_http_version 1.1;
        # gzip_types text/plain text/css application/json application/javascript                                                                                                              text/xml application/xml application/xml+rss text/javascript;

        ##
        # Virtual Host Configs
        ##

        include /etc/nginx/conf.d/*.conf;
        include /etc/nginx/sites-enabled/*;
}


#mail {
#       # See sample authentication script at:
#       # http://wiki.nginx.org/ImapAuthenticateWithApachePhpScript
#
#       # auth_http localhost/auth.php;
#       # pop3_capabilities "TOP" "USER";
#       # imap_capabilities "IMAP4rev1" "UIDPLUS";
#
#       server {
#               listen     localhost:110;
#               protocol   pop3;
#               proxy      on;
#       }
#
#       server {
#               listen     localhost:143;
#               protocol   imap;
#               proxy      on;
#       }
#}

and I do add file simple file to my conf
/etc/nginx/conf.d/website.local.conf

server {
   listen 80 default_server;
   index index.html index.htm index.php;
   server_name website.local;
   root /var/www/website.local;
}

as I mentioned before it's working while startup the ubuntu, after about a minute Nginx cannot be reached. thank you

[rthamrin]

I found the reason the main reason is nginx-ingress, ufw and Iptables
after my service Nginx running my Iptables blocked the port 80 and 443 default, you can remove your iptables rule, but I choose to remove my nginx-ingress :D because I don't need it now.

# kubectl get service --all-namespaces
NAMESPACE       NAME                                 TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)                      AGE
default         kubernetes                           ClusterIP   10.43.0.1      <none>        443/TCP                      37d
kube-system     kube-dns                             ClusterIP   10.43.0.10     <none>        53/UDP,53/TCP,9153/TCP       37d
kube-system     metrics-server                       ClusterIP   10.43.42.85    <none>        443/TCP                      37d
ingress-nginx   ingress-nginx-controller-admission   ClusterIP   10.43.69.64    <none>        443/TCP                      2d8h
ingress-nginx   ingress-nginx-controller             NodePort    10.43.91.127   <none>        80:31065/TCP,443:30174/TCP   2d8h

what I do is remove the ingress-nginx from my machine

kubectl delete namespace ingress-nginx

and deploy nginx from the machine

check first if you already deploy the service
# kubectl get deployment

if not start to deploy your own nginx
# kubectl create deployment nginx --image=nginx

check once more if already there
#kubectl get deployments
NAME READY UP-TO-DATE AVAILABLE AGE
nginx 0/1 1 0 11s

allow the public and local addresses to access our Nginx service
# kubectl create service nodeport nginx --tcp=80:80

check your Nginx port number, that had picked by Kubernetes randomly
# kubectl get service
nginx NodePort 10.43.16.110 80:30249/TCP 7s

test your Nginx service

#curl localhost:30249
#curl iplocal:30249
#curl ippublic:30249

change local and Public addresses with your IP address, and never forget to put the port number.

good luck.