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

    Nextcloud Firewall rule help

    Scheduled Pinned Locked Moved Firewalling
    5 Posts 4 Posters 4.2k 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.
    • N
      NasKar
      last edited by

      I have a nextcloud server that I used to be able to access from my ddns address inside my network when I was using a off the shelf router.  Now that I'm using PFSense I can only access the nextcloud server from it's local IP address.  This creates a problem as when I copy a link to share a file it gives the internal IP address.  I'm pretty sure this is because I'm missing a rule to allow that traffic in from the WAN.  My several attempts to get it to work have failed.  Created an alias to the ddns host, created a run in WAN for that as the source and destination the local nextcloud server on 443.  Hopefully someone can help clarify how to fix this.  I'm sorry this is so basic.

      Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz
      2 CPUs: 1 package(s) x 2 core(s)
      AES-NI CPU Crypto: No
      2 Gigs Ram
      SSD with ver 2.4.0
      IBM Intel Pro PCI-E Quad Port 10/100/1000 Server Adapter 39Y6138 (K210320)

      1 Reply Last reply Reply Quote 0
      • N
        Nullity
        last edited by

        A WAN firewall rule is needed if you want external access to your internal services, which doesn't seem to be what you are talking about.

        To access local hosts via the external address I think you need to use NAT Reflection. Refer to the pfSense wiki.

        Please correct any obvious misinformation in my posts.
        -Not a professional; an arrogant ignoramous.

        1 Reply Last reply Reply Quote 0
        • DerelictD
          Derelict LAYER 8 Netgate
          last edited by

          I used Split DNS for my owncloud/nextcloud host name.

          https://doc.pfsense.org/index.php/Why_can%27t_I_access_forwarded_ports_on_my_WAN_IP_from_my_LAN/OPTx_networks

          Chattanooga, Tennessee, USA
          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
          Do Not Chat For Help! NO_WAN_EGRESS(TM)

          1 Reply Last reply Reply Quote 0
          • N
            NasKar
            last edited by

            @Derelict:

            I used Split DNS for my owncloud/nextcloud host name.

            https://doc.pfsense.org/index.php/Why_can%27t_I_access_forwarded_ports_on_my_WAN_IP_from_my_LAN/OPTx_networks

            The doc only shows settings for the example with DNS Forwarder is there an example that shows the setup for DNS Resolver? Or am I missing something?

            Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz
            2 CPUs: 1 package(s) x 2 core(s)
            AES-NI CPU Crypto: No
            2 Gigs Ram
            SSD with ver 2.4.0
            IBM Intel Pro PCI-E Quad Port 10/100/1000 Server Adapter 39Y6138 (K210320)

            1 Reply Last reply Reply Quote 0
            • jahonixJ
              jahonix
              last edited by

              If your NextCloud server does have a static DHCP entry then use the "Register DHCP …" checkboxes as well.

              Host Override is another option with the resolver.
              Not too hard to guess, is it?

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