{"timestamp": "2026-07-10T22:10:17.524496", "data": {"url": "https://caddy.community/t/caddy-on-device-with-multiple-ip-address/14516", "title": "Caddy on device with multiple IP address - Help - Caddy Community", "content": "seanPH (sean) December 27, 2021, 12:03pm 1 1. Caddy version ( caddy version ): v2.4.6 2. How I run Caddy: loaded as a service. autostarts. a. System environment: Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye b. Command: Paste command here. c. Service/unit/compose file: Not using docker Caddy is running nicely here and everything is working. However, the device it runs on currently has 1 ethernet nic with one address ( 192.168.33.11 ). Soon that will change. We plan to add a 2nd address to the nic eg (192.168.33.33 ) . Some traffic will be routed to it on each address. Right now it is simple - one address - Caddy listens on multiple ports and responds accordingly . But we are trying to understand how to configure it so Caddy can service 2 different IP addresses and ensure that all response traffic is sent back only via the same ip address.. For example where it serves out a webpage on 192.168.33.11:8080 , it would be a different webpage to serve out on 192.168.33.33:8080 Even if anybody can point us to the right section in the documentation about how to configure like this . We have already searched the doc and have not found anything similar. We hope that Caddy can actually do this \u2026 seanPH (sean) December 27, 2021, 12:03pm 1 1. Caddy version ( caddy version ): v2.4.6 2. How I run Caddy: loaded as a service. autostarts. a. System environment: Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye b. Command: Paste command here. c. Service/unit/compose file: Not using docker Caddy is running nicely here and everything is working. However, the device it runs on currently has 1 ethernet nic with one address ( 192.168.33.11 ). Soon that will change. We plan to add a 2nd address to the nic eg (192.168.33.33 ) . Some traffic will be routed to it on each address. Right now it is simple - one address - Caddy listens on multiple ports and responds accordingly . But we are trying to understand how to configure it so Caddy can service 2 different IP addresses and ensure that all response traffic is sent back only via the same ip address.. For example where it serves out a webpage on 192.168.33.11:8080 , it would be a different webpage to serve out on 192.168.33.33:8080 Even if anybody can point us to the right section in the documentation about how to configure like this . We have already searched the doc and have not found anything similar. We hope that Caddy can actually do this \u2026", "lists": [["Home", "Categories", "Guidelines", "Terms of Service"]], "tables": [], "code_blocks": ["caddy version", "Distributor ID: Debian\nDescription:    Debian GNU/Linux 11 (bullseye)\nRelease:        11\nCodename:       bullseye", "Distributor ID: Debian\nDescription:    Debian GNU/Linux 11 (bullseye)\nRelease:        11\nCodename:       bullseye", "Paste command here.", "Paste command here.", "Not using docker", "Not using docker", "bind", "0.0.0.0", "a.example.com {\n\tbind 192.168.33.11\n\n\treverse_proxy somewhere:8080\n}\n\nb.example.com {\n\tbind 192.168.33.33\n\n\treverse_proxy elsewhere:8080\n}", "a.example.com {\n\tbind 192.168.33.11\n\n\treverse_proxy somewhere:8080\n}\n\nb.example.com {\n\tbind 192.168.33.33\n\n\treverse_proxy elsewhere:8080\n}"], "meta_description": "1. Caddy version (caddy version):\nv2.4.6 \n2. How I run Caddy:\n\nloaded as a service. autostarts. \na. System environment:\n\nDistributor ID: Debian\nDescription:    Debian GNU/Linux 11 (bullseye)\nRelease:        11\nCodename: \u2026", "meta_keywords": "", "og_image": "https://dqah5woojdp50.cloudfront.net/original/2X/9/9ff57336e95a9ba567e563d5e36d05c91df182df.png", "js_rendered": true, "js_message": "Page appears to be rendered by a JavaScript framework; content may be incomplete.", "success": true, "error": "", "truncated": false, "fetched_bytes": 220767, "total_bytes": null}}