Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 33 replies
  • Answers 1 answer
  • Subscribers 41 subscribers
  • Views 7826 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Port forwarding within network- LAN to LAN (forward to docker app mapped port)

jang430

Hi.  I am using docker apps, inside Unraid NAS.  I set up a Nextcloud container (docker).  To be able to use it from outside, I created a DNAT rule so that from outside, I can access Nextcloud app.  It is working.  Nextcloud uses port 80 and port 443.  These ports are used by my Unraid NAS.  I mapped incoming http to port 380 of docker app, and incoming https to port 643 of docker app.  So far, so good.

DNAT rule

Source- WAN. Allowed client network- ANY

Destination- WAN port  Services- HTTP and another rule HTTPS

Protected Servers-  NAS IP  Mapped port- 380 and another port 643 for HTTPS

Protected zone- LAN

 

From inside the network, I can't access Nextcloud app



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to jang430

    Hi,

    Have you restarted your PC at any stage during the testing?

    What is the result from nslookup of your device?

    Ian

    XG115W - v20.0.2 MR-2 - Home

    XG on VM 8 - v21 GA

    If a post solves your question please use the 'Verify Answer' button.

  • 0 in reply to rfcat_vk

    Last login: Mon Apr 20 13:48:01 on ttys000

     

    The default interactive shell is now zsh.

    To update your account to use zsh, please run `chsh -s /bin/zsh`.

    For more details, please visit support.apple.com/.../HT208050.

    Jasons-MacBook-Pro-2:~ jason$ nslookup xxx.duckdns.org

    Server: 1.1.1.1

    Address: 1.1.1.1#53

     

    Non-authoritative answer:

    Name: xxx.duckdns.org

    Address: 112.205.60.xx

     

    Jasons-MacBook-Pro-2:~ jason$

  • 0 in reply to jang430

    Hi,

    I see the issue, you are using the external DNS not the XG as your DNS so you will always resolve to the external advertised address.

    Change you DHCP server on the XG to provide the XG as the DNS then try to access your device.

    Ian

    XG115W - v20.0.2 MR-2 - Home

    XG on VM 8 - v21 GA

    If a post solves your question please use the 'Verify Answer' button.

  • 0 in reply to rfcat_vk

    XG acts as my DHCP server.  How do I do "Change you DHCP server on the XG to provide the XG as the DNS then try to access your device?"

    Regards

  • 0 in reply to jang430

    I assumed that 1.1.1.1 is your external DNS.

    Ian

    XG115W - v20.0.2 MR-2 - Home

    XG on VM 8 - v21 GA

    If a post solves your question please use the 'Verify Answer' button.

  • 0 in reply to rfcat_vk

    Yes  using cloudflare 1.1.1.1

    What should I do with it?

  • 0 in reply to jang430

    I suggest you change your DNS settings in your DHCP server to something like mine as below.

     

    Ian

    XG115W - v20.0.2 MR-2 - Home

    XG on VM 8 - v21 GA

    If a post solves your question please use the 'Verify Answer' button.

  • 0 in reply to rfcat_vk

    Hi.  I changed that in my DHCP settings.  192.168.1.1.  Now, when I do traceroute, I get:

     

    traceroute xxx.duckdns.org

    traceroute to xxx.duckdns.org (192.168.1.xx), 64 hops max, 52 byte packets

    1  xxx.duckdns.org (192.168.1.xx)  1.180 ms  1.144 ms  1.310 ms

    Jasons-MacBook-Pro-2:~ jason$

     

    That's an improvement :D. Although, accessing it through xxx.duckdns.org still says "Safari can't open the page."

     

     

     

     

  • 0 in reply to jang430

    One step at a time. That error message indicates you have a security issue with your device eg you have enabled https or TLS and you have not installed the XG CA on your MAC.

    Ian

    XG115W - v20.0.2 MR-2 - Home

    XG on VM 8 - v21 GA

    If a post solves your question please use the 'Verify Answer' button.

  • 0 in reply to rfcat_vk

    I used another device to access the xxx.duckdns.org and it presented my my NAS (device hosting the Nextcloud docker) 192.168.1.xx

    It didn't go to 192.168.1.xx:whatever_port_i'M_using.  While from the outside, whenever I access xxx.duckdns.org automatically routes to 192.168.1.xx:port.  But this can be addressed later.  

    The container is using LetsEncrypt, so I don't use Sophos CA as I don't know how to.  I'm just following video tutorials I've seen :D

Unfiltered HTML