Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Nginx and HNAP1

    Scheduled Pinned Locked Moved General pfSense Questions
    3 Posts 2 Posters 198 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      jonna99
      last edited by

      Hi!
      Does anyone know how to fix this error. Need help.
      It appears every 24 hours or so.

      "[error] 700#100372: *2581 "/usr/local/www/HNAP1/index.php" is not found (2: No such file or directory), client: 192.168.9.121, server: , request: "GET /HNAP1/ HTTP/2.0", host: "192.168.9.1"

      192.168.9.1 is Pfsense and 192.168.9.121 is a local pc.

      Pfsense 24.11

      Thanks in advance
      Jonna

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        It's harmless in pfSense but it's caused by that local client trying to access a page at the pfSense IP address that doesn't exists in pfSense. So most likely that client was previously connecting to that service at the pfSense IP when it was some other host. It could be something on that client trying to actually use HNAP. It could be the client scanning local hosts. It could be malware on that client looking for local exploitable services. Check that client device.

        J 1 Reply Last reply Reply Quote 1
        • J
          jonna99 @stephenw10
          last edited by

          @stephenw10 said in Nginx and HNAP1:

          It's harmless in pfSense but it's caused by that local client trying to access a page at the pfSense IP address that doesn't exists in pfSense. So most likely that client was previously connecting to that service at the pfSense IP when it was some other host. It could be something on that client trying to actually use HNAP. It could be the client scanning local hosts. It could be malware on that client looking for local exploitable services. Check that client device.

          I see. I will try to investigate the client. Good to know that it´s harmless.
          Thank you,
          Jonna

          1 Reply Last reply Reply Quote 1
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.