Good morning/night/evening/the time for you right now, ever since I set up Snikket, my web pages other than Snikket’s have been displaying nginx 404 not found errors. I can access the website locally but when I go to the domain name it pops up the error. When I go to localhost:443 it also shows the nginx not found 404 thing so I think that’s where my other website pages are getting the error from, but I never port fowarded port 443, at least I don’t think so. I use the standard nginx reverse proxy for Snikket, and Nginx Proxy Manager for my other web pages. I really hope someone can help me. Thank you very much in advance.

  • Eager EagleEnglish
    1•12 hours ago

    find out which process is really binding to 443 if you don’t recognize that port as being used

    sudo ss -unapt | grep 443
    • @[email protected]OPEnglish
      1•11 hours ago
      tcp   LISTEN    0      4096                                     0.0.0.0:9443                   0.0.0.0:*     users:(("docker-proxy",pid=1550,fd=4))                                                                                                             tcp   LISTEN    0      511                                      0.0.0.0:443                    0.0.0.0:*     users:(("nginx",pid=2511847,fd=6),("nginx",pid=2511846,fd=6),("nginx",pid=2511845,fd=6),("nginx",pid=2511844,fd=6),("nginx",pid=2511843,fd=6))     tcp   LISTEN    0      511                                      0.0.0.0:5443                   0.0.0.0:*     users:(("nginx",pid=2540528,fd=6),("nginx",pid=2540399,fd=6))                                                                                      tcp   LAST-ACK  0      1                                  192.168.0.107:443               91.84.87.137:40016                                                                                                                                                    tcp   LISTEN    0      4096                                        [::]:9443                      [::]:*     users:(("docker-proxy",pid=1560,fd=4))                                                                                                             tcp   LISTEN    0      511                                         [::]:443                       [::]:*     users:(("nginx",pid=2511847,fd=5),("nginx",pid=2511846,fd=5),("nginx",pid=2511845,fd=5),("nginx",pid=2511844,fd=5),("nginx",pid=2511843,fd=5))     tcp   LISTEN    0      511                                         [::]:5443                      [::]:*     users:(("nginx",pid=2540528,fd=7),("nginx",pid=2540399,fd=7))

      I don’t know how to even interpret this, I know it says nginx but which nginx?? I got like 4 nginx web servers running

      • Eager EagleEnglish
        1•10 hours ago

        you do have an nginx process with PID 2511847 using the port

        get more info with

        ps aux | grep 2511847

        or kill it, if you need to spawn a new one with the right configuration

        • @[email protected]OPEnglish
          1•10 hours ago

          apparently it’s my native nginx… wtf. I used

          sudo systemctl stop nginx

          And the websites that had the nginx error went down. I don’t know how this could even happen? My containers use their own nginxes??? Maybe the mix of native nginx and docker nginx is messing everything up, if I can’t find a solution I’m probably gonna nuke my native nginx and use docker nginx for all of my nginx needs