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

    Set up a port forward, still not connectable

    Scheduled Pinned Locked Moved NAT
    5 Posts 2 Posters 1.5k 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.
    • O
      Octopuss
      last edited by

      I am trying to set port forwarding for qbittorrent.
      https://canyouseeme.org/ this site says I am not connectable on the port, but I can download and upload torrents just fine. There probably still is a problem somewhere, because on one tracker it says you need to be connectable in order for direct connection something something.
      I do NOT understand networking. Not one bit. So please talk to me like to an idiot.

      Qbittorrent is set to listen on port 8999.
      My PC's IP is 192.168.1.10.
      LAN is 192.168.0.1/16.
      WAN is, let's just say WAN.
      I created this rule:
      0_1550335543936_a62b2a2f-a488-45a2-8d5e-135c99acbeb1-image.png

      ...and on the website it still says port 8999 is closed.
      What do I do? What's wrong? I don't understand :(

      1 Reply Last reply Reply Quote 0
      • GrimsonG
        Grimson Banned
        last edited by

        https://docs.netgate.com/pfsense/en/latest/nat/port-forward-troubleshooting.html

        O 1 Reply Last reply Reply Quote 0
        • O
          Octopuss @Grimson
          last edited by Octopuss

          @grimson Does it look like I am capable of understanding that stuff?...
          I need an easy guide damnit.

          GrimsonG 1 Reply Last reply Reply Quote 0
          • GrimsonG
            Grimson Banned @Octopuss
            last edited by

            @octopuss said in Set up a port forward, still not connectable:

            I need an easy guide damnit.

            That is an easy guide, if you can't handle that find (and likely pay) someone that can.

            1 Reply Last reply Reply Quote 0
            • O
              Octopuss
              last edited by

              Just FIY - there was some sort of a firewall running on the AP on the roof, and after contacting our ISP it was deactivated, and now it seems to work like it should.

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