Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Offical apps | Community apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Feature Requests
  3. Per-app IP allowlist for internal / company networks (without requiring Cloudron VPN)

Per-app IP allowlist for internal / company networks (without requiring Cloudron VPN)

Scheduled Pinned Locked Moved Feature Requests
1 Posts 1 Posters 26 Views 1 Watching
  • 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.
  • P
    P
    pathab
    App Dev
    wrote last edited by
    #1

    We already run a company VPN. For certain Cloudron apps (admin tools, internal services, staging, etc.) we would like to restrict access so they are only reachable from our existing company network / VPN ranges.

    The current VPN Protection feature solves a similar problem, but it requires users to connect to Cloudron’s own VPN app. For organizations that already have a VPN or a well-defined internal network, this means running and managing a second VPN just for Cloudron apps, which is unnecessary overhead.

    Proposed feature:

    Add a per-app setting (similar to “Require VPN”) that allows defining one or more allowed IP ranges (CIDR). Requests from outside these ranges are rejected (e.g. with a 403 or a simple “Access restricted” page).

    Example use cases:

    • App only reachable from the company VPN / office LAN
    • Different apps with different allowlists (public website vs. internal tools)
    • No need for an additional VPN client when the user is already inside the company network

    Why this is better than only VPN Protection in our case:

    • We already have a VPN. Forcing Cloudron’s VPN on top creates friction and support load.
    • Source IPs are known and stable when users come through the company VPN.
    • Simple CIDR allowlist is easy to understand and configure for admins.

    Technically this should be straightforward to implement in the existing reverse-proxy config generation (Nginx allow / deny per app server block), similar to how VPN Protection already injects rules.

    Would be happy to help test if this gets implemented.

    1 Reply Last reply
    1

    Hello! It looks like you're interested in this conversation, but you don't have an account yet.

    Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

    With your input, this post could be even better 💗

    Register Login
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • Bookmarks
    • Search