# Inbound Proxy?

**URL:** <https://forum.mikrotik.com/t/inbound-proxy/177820>\
**Category:** General\
**Created:** [August 4, 2024, 9:21pm UTC](https://forum.mikrotik.com/t/inbound-proxy/177820 "2024-08-04T21:21:53Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![ehbowen](https://forum.mikrotik.com/letter_avatar/ehbowen/32/6_449c533f586939b6e5f246632a46421f.png) [@ehbowen](https://forum.mikrotik.com/u/ehbowen)\
**Post date:** [August 4, 2024, 9:21pm UTC](https://forum.mikrotik.com/t/inbound-proxy/177820/1 "2024-08-04T21:21:53Z")

</div>

I’ve been going through the WebProxy tool in RouterOS. It appears to be for traffic originating on the LAN which needs filtered or indirect access to WAN. How about the other direction? Suppose that I have, behind a single (static) IP, two NAS units which have content that I want to be web-addressable. Is there a RouterOS provision to take incoming traffic directed to “[nas1.mynet.net](http://nas1.mynet.net)” and “[nas2.mynet.net](http://nas2.mynet.net)” and direct them to the proper LAN destination? Or do I need to set up a separate dedicated proxy server inside the firewall?

---

<div class="post-metadata">

**Author:** ![loloski](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/loloski/32/55501_2.png) [@loloski](https://forum.mikrotik.com/u/loloski)\
**Post date:** [August 4, 2024, 9:39pm UTC](https://forum.mikrotik.com/t/inbound-proxy/177820/2 "2024-08-04T21:39:18Z")

</div>

There’s no built-in support for reverse proxy, If your device has sufficient resource like RB4011 / RB5009 install container package and pull image like nginx or haproxy

---

<div class="post-metadata">

**Author:** ![ehbowen](https://forum.mikrotik.com/letter_avatar/ehbowen/32/6_449c533f586939b6e5f246632a46421f.png) [@ehbowen](https://forum.mikrotik.com/u/ehbowen)\
**Post date:** [August 5, 2024, 2:38am UTC](https://forum.mikrotik.com/t/inbound-proxy/177820/3 "2024-08-05T02:38:11Z")

</div>

> [@](#):
>
> There’s no built-in support for reverse proxy, If your device has sufficient resource like RB4011 / RB5009 install container package and pull image like nginx or haproxy

My main gateway router is an RB4011, but I also have a Raspberry Pi dedicated to network tasks. Best to put it there?

Please note that I’ve never done that before, so if you have links to examples it would be appreciated.

---

<div class="post-metadata">

**Author:** ![pmularski](https://forum.mikrotik.com/letter_avatar/pmularski/32/6_449c533f586939b6e5f246632a46421f.png) [@pmularski](https://forum.mikrotik.com/u/pmularski)\
**Post date:** [August 8, 2024, 5:48am UTC](https://forum.mikrotik.com/t/inbound-proxy/177820/4 "2024-08-08T05:48:11Z")

</div>

You can set up RouterOS to direct incoming traffic to your NAS units without a dedicated proxy server by using port forwarding (destination NAT). Here’s how to do it:

1. DNS Setup: Ensure [nas1.mynet.net](http://nas1.mynet.net) and [nas2.mynet.net](http://nas2.mynet.net) point to your static IP.

2. Create NAT Rules:

- Go to the Firewall section in RouterOS.  
Under the NAT tab, create rules for each NAS.

1. For [nas1.mynet.net](http://nas1.mynet.net):

- Chain: dstnat  
Protocol: tcp  
Dst. Port: (e.g., 80 for HTTP)  
Action: dst-nat  
To Addresses: (IP of NAS1)  
To Ports: (port NAS1 listens on)

1. For [nas2.mynet.net](http://nas2.mynet.net), repeat the above with NAS2’s details.

2. Firewall Filters: Ensure you allow traffic on the specified ports in your firewall.

3. Testing: Access [nas1.mynet.net](http://nas1.mynet.net) and [nas2.mynet.net](http://nas2.mynet.net) from an external network to verify everything is working.

This setup effectively routes incoming traffic based on subdomains to the correct NAS device. If you’re also looking for options for online activities, consider exploring the best shared proxies to enhance your browsing experience while ensuring privacy and security.

---

<div class="post-metadata">

**Author:** ![Elinsoid](https://forum.mikrotik.com/letter_avatar/elinsoid/32/6_449c533f586939b6e5f246632a46421f.png) [@Elinsoid](https://forum.mikrotik.com/u/Elinsoid)\
**Post date:** [May 10, 2025, 1:23pm UTC](https://forum.mikrotik.com/t/inbound-proxy/177820/5 "2025-05-10T13:23:47Z")

</div>

Hello, sorry for bumping this. Have you managed to do it, OP? Can I do it with these proxies - [https://lightningproxies.net/](https://lightningproxies.net/)?

---

<div class="post-metadata">

**Author:** ![mkx](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/mkx/32/1611_2.png) [@mkx](https://forum.mikrotik.com/u/mkx)\
**Post date:** [May 11, 2025, 8:05am UTC](https://forum.mikrotik.com/t/inbound-proxy/177820/6 "2025-05-11T08:05:14Z")

</div>

> [@](#):
>
> Hello, sorry for bumping this. Have you managed to do it OP?

Reply in post #2 is still true.

---

<div class="post-metadata">

**Author:** ![Hyzstried](https://forum.mikrotik.com/letter_avatar/hyzstried/32/6_449c533f586939b6e5f246632a46421f.png) [@Hyzstried](https://forum.mikrotik.com/u/Hyzstried)\
**Post date:** [July 24, 2025, 4:35am UTC](https://forum.mikrotik.com/t/inbound-proxy/177820/7 "2025-07-24T04:35:40Z")

</div>

One time, juggling multiple NAS units behind one IP got tricky until using a reverse proxy made routing neat and easy. Also, for anyone juggling multiple IPs or locations, [Buy Rotating Proxies](https://infatica.io/rotating-proxies/) can be a solid way to manage diverse traffic smoothly.

---

<div class="post-metadata">

**Author:** ![optio](https://forum.mikrotik.com/letter_avatar/optio/32/6_449c533f586939b6e5f246632a46421f.png) [@optio](https://forum.mikrotik.com/u/optio)\
**Post date:** [August 1, 2025, 12:00pm UTC](https://forum.mikrotik.com/t/inbound-proxy/177820/8 "2025-08-01T12:00:55Z")

</div>

Edited 8 days old post to add an Ad?

---

<div class="post-metadata">

**Author:** ![jonhas1](https://forum.mikrotik.com/letter_avatar/jonhas1/32/6_449c533f586939b6e5f246632a46421f.png) [@jonhas1](https://forum.mikrotik.com/u/jonhas1)\
**Post date:** [November 21, 2026, 8:12pm UTC](https://forum.mikrotik.com/t/inbound-proxy/177820/9 "2026-11-21T20:12:21Z")

</div>

Why don't you just use something like a browserproxy instead? Easier to use and safe (in general).
