<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[App bind address]]></title><description><![CDATA[<p dir="auto">Possible feature request: bind address on the app level. This would essentially allow for creating internal services reachable only from a company subnet, the IP of a VPN tunnel and more.</p>
<p dir="auto">I imagine a good placement for this setting in the GUI is the <em>Advanced</em> tab of the app configuration window.</p>
]]></description><link>https://forum.cloudron.io/topic/1756/app-bind-address</link><generator>RSS for Node</generator><lastBuildDate>Mon, 08 Jun 2026 23:14:44 GMT</lastBuildDate><atom:link href="https://forum.cloudron.io/topic/1756.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 30 Apr 2019 08:15:49 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to App bind address on Thu, 02 May 2019 17:59:32 GMT]]></title><description><![CDATA[<p dir="auto">Thanks for clarifying. I could do that, but I’m only looking to put certain apps behind IP restriction, not all of them.</p>
]]></description><link>https://forum.cloudron.io/post/3454</link><guid isPermaLink="true">https://forum.cloudron.io/post/3454</guid><dc:creator><![CDATA[yusf]]></dc:creator><pubDate>Thu, 02 May 2019 17:59:32 GMT</pubDate></item><item><title><![CDATA[Reply to App bind address on Thu, 02 May 2019 15:34:54 GMT]]></title><description><![CDATA[<p dir="auto">Thanks for the clarification, however this seems to be quite out of scope for Cloudron. Generally we try to keep things simple and cover the most common use-cases for running apps. Instead you could put an external firewall in front of your server, which only allows incoming traffic from those IPs or subnets. Most VPS provider have external firewall support.</p>
]]></description><link>https://forum.cloudron.io/post/3452</link><guid isPermaLink="true">https://forum.cloudron.io/post/3452</guid><dc:creator><![CDATA[nebulon]]></dc:creator><pubDate>Thu, 02 May 2019 15:34:54 GMT</pubDate></item><item><title><![CDATA[Reply to App bind address on Thu, 02 May 2019 15:29:47 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/nebulon" aria-label="Profile: nebulon">@<bdi>nebulon</bdi></a> Sorry for being unclear. What I mean is the ability to configure specific apps to accept connections from a specific IP or IP subnet. <code>84.85.86.87</code> for example, or perhaps <code>84.84.84.0/24</code>.</p>
<p dir="auto">I figure the feature will be easy to implement since every app is reverse proxied by an nginx instance. ?</p>
]]></description><link>https://forum.cloudron.io/post/3451</link><guid isPermaLink="true">https://forum.cloudron.io/post/3451</guid><dc:creator><![CDATA[yusf]]></dc:creator><pubDate>Thu, 02 May 2019 15:29:47 GMT</pubDate></item><item><title><![CDATA[Reply to App bind address on Thu, 02 May 2019 14:18:09 GMT]]></title><description><![CDATA[<p dir="auto">Not exactly sure what the use-case for this is or what you mean with "bind address" as such. If you just want to have apps installed within your private network, thus the public resolving wont work, you have to select the <code>noop</code> backend for that domain. Is that what you were looking for?</p>
]]></description><link>https://forum.cloudron.io/post/3447</link><guid isPermaLink="true">https://forum.cloudron.io/post/3447</guid><dc:creator><![CDATA[nebulon]]></dc:creator><pubDate>Thu, 02 May 2019 14:18:09 GMT</pubDate></item></channel></rss>