Remotely Access Your Mealie Shopping List Without Opening Ports

•

Put your self-hosted Mealie instance behind a Twingate Connector, install the Client on your phone, and pull up your shopping list without opening a single port on your router.

Mealie shipped a redesigned shopping list this past May, and v3.19 followed with important security fixes for its query filter API. It's a good reminder that a recipe app, no matter how friendly it looks, still shouldn't be sitting on the open internet behind a port forward and a fingers-crossed TLS cert. With Thanksgiving less than two weeks away, the grocery run is coming either way. This is the weekend to set it up properly.

Here's the setup: Mealie stays on your home network, a Twingate Connector handles the outbound tunnel, and your phone reaches mealie.home.lan (or whatever you call it) from the dairy aisle like it's on the couch. No inbound ports. No public DNS record pointing at your house.

What you'll have at the end

  • Mealie reachable from your phone over a private address, with no inbound ports open on your router

  • Split tunneling so only Mealie traffic goes through Twingate — Instagram, Spotify, and your grocery store's app go straight to the internet as usual

  • A home-screen icon for Mealie

  • A household member with access to Mealie only, not the rest of your homelab

Why not just port-forward Mealie?

Three reasons, in order of how much they should bother you.

First, Mealie has a login screen, but it's a recipe app, not a hardened edge service. The v3.19 release this past May patched a data-exposure issue in the query filter API — the kind of thing you'd rather not have exposed to drive-by scanners while you wait for your next docker pull. Self-hosted apps patch on their own schedule. The internet does not wait for them.

Second, a port forward gives every bot on the internet a chance to try your login. Even with a strong password, you're renting a slice of your attack surface to anyone running masscan.

Third, if you do want to put Mealie behind a reverse proxy with a public cert, you're now maintaining Caddy or Traefik, a wildcard DNS record, dynamic DNS if your IP changes, and probably Authelia or similar in front of it. That's a lot of yak-shaving for a shopping list.

Twingate skips the exposure. The Connector dials out to Twingate's network, the Client on your phone dials out too, and the two meet in the middle. Your router's inbound firewall rules stay empty.

The architecture, in one paragraph

You'll run a Connector on your home network (a container on your NAS, a Raspberry Pi, whatever's always on). The Connector makes an outbound connection to Twingate's Controller — no inbound ports needed. You'll define Mealie as a Resource in Twingate (something like mealie.home.lan or its internal IP). You'll install the Twingate Client on your phone, sign in with your identity provider, and the Client will intercept DNS queries for that Mealie address and route only that traffic through the Connector. Everything else on your phone uses the regular internet.

If a direct peer-to-peer connection between phone and Connector is possible, Twingate uses it. If not (think: grocery store Wi-Fi with weird NAT), traffic falls back through a Relay. The Relay doesn't decrypt anything; it just passes encrypted bytes.

Prerequisites

  • A running Mealie instance on your home network (Docker is the common path — the official Mealie installation docs cover it)

  • An internal DNS name for Mealie, or at least its stable internal IP

  • A free Twingate account (the free tier supports up to 5 users, which covers most households)

  • Somewhere on your home network to run the Connector — a Pi, a NAS Docker host, a small VM, or the same host running Mealie

Step 1: Create a Remote Network and Connector

Sign in to the Twingate admin console and create a new Remote Network. Call it home or homelab. Inside that network, add a Connector and choose Docker as the deployment method.

The admin console generates a docker run command with your tokens already filled in. Copy it and run it on your Connector host.

The Connector will show up as "Connected" in the admin console within a few seconds. If you want redundancy (and Twingate recommends two Connectors per Remote Network), run a second container on a different host. Cheap insurance.

Step 2: Add Mealie as a Resource

In the admin console, open your Remote Network and add a new Resource. The address is whatever your phone will try to reach — this is the part that trips people up, so pick one and stick with it:

  • If you have internal DNS (Pi-hole, AdGuard Home, your router's DNS), use a name like mealie.home.lan

  • If you don't, use the internal IP of your Mealie host, e.g. 192.168.1.50

  • If Mealie runs on a non-standard port (the default Docker setup uses 9925), access it as mealie.home.lan:9925. Resources allow all ports by default; you can restrict this one to 9925.

Twingate's Client intercepts DNS queries matching your resource addresses and resolves them through the Connector, so internal DNS names work even from your phone on cellular.

Step 3: Set up a household group and policy

Your partner wants the shopping list, not shell access to your Proxmox box.

Invite your partner from the Users page in the admin console. Then create a Group called something like Household. Add yourself and your partner. Then edit the Mealie Resource and grant access to the Household group. Leave your other Resources (Proxmox UI, Home Assistant, that one Jellyfin instance you never finished setting up) restricted to an Admins group that only contains you.

Twingate enforces this at the Resource level, not the network level. Over Twingate, your partner’s Client only knows about Mealie. It can’t scan your network, reach your router’s admin page, or hit port 22 on your NAS. (On your home Wi-Fi, their phone is on your LAN like any other device.) The Client only knows about what you've explicitly granted.

Step 4: Install the Client on your phones

Install the Twingate iOS or Android app on both phones. Sign in with the account you use for Twingate (Google, Microsoft, or whatever you use). The Client will download the policy and start listening for DNS queries that match your Mealie Resource.

Split tunneling is the default behavior. Only traffic destined for your defined Resources goes through the tunnel. Spotify streams normally. The grocery store's wayfinding app hits the public internet directly.

Open a browser and visit your Mealie URL. If it loads, you're done with the hard part.

Step 5: Add Mealie to the home screen

Mealie is a progressive web app, so you can add it to your home screen on both iOS and Android.

On iOS: open Mealie in Safari (the most reliable path on iOS), tap the share button, and choose "Add to Home Screen." On Android: open it in Chrome, tap the three-dot menu, and choose "Install app" or "Add to Home screen."

What this actually gave you

  • Mealie reachable from anywhere, with your router's inbound firewall rules untouched

  • No public DNS record pointing at your home IP and no internet-facing reverse proxy to patch

  • Your partner has Mealie and only Mealie — the rest of the homelab stays out of sight

  • Split tunneling means only Mealie traffic goes through Twingate

  • When Mealie's next CVE lands, it’s only reachable by people you’ve granted access, not every scanner on the internet. That buys you time to patch.

The architectural point underneath all this: Mealie is not a hardened internet-facing service, and treating it like one is a losing game. Keeping it private and reaching it over a least-privilege tunnel is cheaper, safer, and less work than a port forward plus reverse proxy plus auth layer.

Closing

For the full breakdown of Resources, Groups, and policies, the Twingate documentation has the deep dives on everything used here. The Connector deployment guide covers Docker, systemd, Kubernetes, and the major cloud options if your homelab setup is more involved than a single Pi.

New to Twingate? You can use Twingate for free for up to 5 users, request a personalized demo, or reach out to the team over on the Twingate subreddit.

Rapidly implement a modern Zero Trust network that is more secure and maintainable than VPNs.

/

Mealie Remote Access

Remotely Access Your Mealie Shopping List Without Opening Ports

•

Put your self-hosted Mealie instance behind a Twingate Connector, install the Client on your phone, and pull up your shopping list without opening a single port on your router.

Mealie shipped a redesigned shopping list this past May, and v3.19 followed with important security fixes for its query filter API. It's a good reminder that a recipe app, no matter how friendly it looks, still shouldn't be sitting on the open internet behind a port forward and a fingers-crossed TLS cert. With Thanksgiving less than two weeks away, the grocery run is coming either way. This is the weekend to set it up properly.

Here's the setup: Mealie stays on your home network, a Twingate Connector handles the outbound tunnel, and your phone reaches mealie.home.lan (or whatever you call it) from the dairy aisle like it's on the couch. No inbound ports. No public DNS record pointing at your house.

What you'll have at the end

  • Mealie reachable from your phone over a private address, with no inbound ports open on your router

  • Split tunneling so only Mealie traffic goes through Twingate — Instagram, Spotify, and your grocery store's app go straight to the internet as usual

  • A home-screen icon for Mealie

  • A household member with access to Mealie only, not the rest of your homelab

Why not just port-forward Mealie?

Three reasons, in order of how much they should bother you.

First, Mealie has a login screen, but it's a recipe app, not a hardened edge service. The v3.19 release this past May patched a data-exposure issue in the query filter API — the kind of thing you'd rather not have exposed to drive-by scanners while you wait for your next docker pull. Self-hosted apps patch on their own schedule. The internet does not wait for them.

Second, a port forward gives every bot on the internet a chance to try your login. Even with a strong password, you're renting a slice of your attack surface to anyone running masscan.

Third, if you do want to put Mealie behind a reverse proxy with a public cert, you're now maintaining Caddy or Traefik, a wildcard DNS record, dynamic DNS if your IP changes, and probably Authelia or similar in front of it. That's a lot of yak-shaving for a shopping list.

Twingate skips the exposure. The Connector dials out to Twingate's network, the Client on your phone dials out too, and the two meet in the middle. Your router's inbound firewall rules stay empty.

The architecture, in one paragraph

You'll run a Connector on your home network (a container on your NAS, a Raspberry Pi, whatever's always on). The Connector makes an outbound connection to Twingate's Controller — no inbound ports needed. You'll define Mealie as a Resource in Twingate (something like mealie.home.lan or its internal IP). You'll install the Twingate Client on your phone, sign in with your identity provider, and the Client will intercept DNS queries for that Mealie address and route only that traffic through the Connector. Everything else on your phone uses the regular internet.

If a direct peer-to-peer connection between phone and Connector is possible, Twingate uses it. If not (think: grocery store Wi-Fi with weird NAT), traffic falls back through a Relay. The Relay doesn't decrypt anything; it just passes encrypted bytes.

Prerequisites

  • A running Mealie instance on your home network (Docker is the common path — the official Mealie installation docs cover it)

  • An internal DNS name for Mealie, or at least its stable internal IP

  • A free Twingate account (the free tier supports up to 5 users, which covers most households)

  • Somewhere on your home network to run the Connector — a Pi, a NAS Docker host, a small VM, or the same host running Mealie

Step 1: Create a Remote Network and Connector

Sign in to the Twingate admin console and create a new Remote Network. Call it home or homelab. Inside that network, add a Connector and choose Docker as the deployment method.

The admin console generates a docker run command with your tokens already filled in. Copy it and run it on your Connector host.

The Connector will show up as "Connected" in the admin console within a few seconds. If you want redundancy (and Twingate recommends two Connectors per Remote Network), run a second container on a different host. Cheap insurance.

Step 2: Add Mealie as a Resource

In the admin console, open your Remote Network and add a new Resource. The address is whatever your phone will try to reach — this is the part that trips people up, so pick one and stick with it:

  • If you have internal DNS (Pi-hole, AdGuard Home, your router's DNS), use a name like mealie.home.lan

  • If you don't, use the internal IP of your Mealie host, e.g. 192.168.1.50

  • If Mealie runs on a non-standard port (the default Docker setup uses 9925), access it as mealie.home.lan:9925. Resources allow all ports by default; you can restrict this one to 9925.

Twingate's Client intercepts DNS queries matching your resource addresses and resolves them through the Connector, so internal DNS names work even from your phone on cellular.

Step 3: Set up a household group and policy

Your partner wants the shopping list, not shell access to your Proxmox box.

Invite your partner from the Users page in the admin console. Then create a Group called something like Household. Add yourself and your partner. Then edit the Mealie Resource and grant access to the Household group. Leave your other Resources (Proxmox UI, Home Assistant, that one Jellyfin instance you never finished setting up) restricted to an Admins group that only contains you.

Twingate enforces this at the Resource level, not the network level. Over Twingate, your partner’s Client only knows about Mealie. It can’t scan your network, reach your router’s admin page, or hit port 22 on your NAS. (On your home Wi-Fi, their phone is on your LAN like any other device.) The Client only knows about what you've explicitly granted.

Step 4: Install the Client on your phones

Install the Twingate iOS or Android app on both phones. Sign in with the account you use for Twingate (Google, Microsoft, or whatever you use). The Client will download the policy and start listening for DNS queries that match your Mealie Resource.

Split tunneling is the default behavior. Only traffic destined for your defined Resources goes through the tunnel. Spotify streams normally. The grocery store's wayfinding app hits the public internet directly.

Open a browser and visit your Mealie URL. If it loads, you're done with the hard part.

Step 5: Add Mealie to the home screen

Mealie is a progressive web app, so you can add it to your home screen on both iOS and Android.

On iOS: open Mealie in Safari (the most reliable path on iOS), tap the share button, and choose "Add to Home Screen." On Android: open it in Chrome, tap the three-dot menu, and choose "Install app" or "Add to Home screen."

What this actually gave you

  • Mealie reachable from anywhere, with your router's inbound firewall rules untouched

  • No public DNS record pointing at your home IP and no internet-facing reverse proxy to patch

  • Your partner has Mealie and only Mealie — the rest of the homelab stays out of sight

  • Split tunneling means only Mealie traffic goes through Twingate

  • When Mealie's next CVE lands, it’s only reachable by people you’ve granted access, not every scanner on the internet. That buys you time to patch.

The architectural point underneath all this: Mealie is not a hardened internet-facing service, and treating it like one is a losing game. Keeping it private and reaching it over a least-privilege tunnel is cheaper, safer, and less work than a port forward plus reverse proxy plus auth layer.

Closing

For the full breakdown of Resources, Groups, and policies, the Twingate documentation has the deep dives on everything used here. The Connector deployment guide covers Docker, systemd, Kubernetes, and the major cloud options if your homelab setup is more involved than a single Pi.

New to Twingate? You can use Twingate for free for up to 5 users, request a personalized demo, or reach out to the team over on the Twingate subreddit.

Rapidly implement a modern Zero Trust network that is more secure and maintainable than VPNs.

Remotely Access Your Mealie Shopping List Without Opening Ports

•

Put your self-hosted Mealie instance behind a Twingate Connector, install the Client on your phone, and pull up your shopping list without opening a single port on your router.

Mealie shipped a redesigned shopping list this past May, and v3.19 followed with important security fixes for its query filter API. It's a good reminder that a recipe app, no matter how friendly it looks, still shouldn't be sitting on the open internet behind a port forward and a fingers-crossed TLS cert. With Thanksgiving less than two weeks away, the grocery run is coming either way. This is the weekend to set it up properly.

Here's the setup: Mealie stays on your home network, a Twingate Connector handles the outbound tunnel, and your phone reaches mealie.home.lan (or whatever you call it) from the dairy aisle like it's on the couch. No inbound ports. No public DNS record pointing at your house.

What you'll have at the end

  • Mealie reachable from your phone over a private address, with no inbound ports open on your router

  • Split tunneling so only Mealie traffic goes through Twingate — Instagram, Spotify, and your grocery store's app go straight to the internet as usual

  • A home-screen icon for Mealie

  • A household member with access to Mealie only, not the rest of your homelab

Why not just port-forward Mealie?

Three reasons, in order of how much they should bother you.

First, Mealie has a login screen, but it's a recipe app, not a hardened edge service. The v3.19 release this past May patched a data-exposure issue in the query filter API — the kind of thing you'd rather not have exposed to drive-by scanners while you wait for your next docker pull. Self-hosted apps patch on their own schedule. The internet does not wait for them.

Second, a port forward gives every bot on the internet a chance to try your login. Even with a strong password, you're renting a slice of your attack surface to anyone running masscan.

Third, if you do want to put Mealie behind a reverse proxy with a public cert, you're now maintaining Caddy or Traefik, a wildcard DNS record, dynamic DNS if your IP changes, and probably Authelia or similar in front of it. That's a lot of yak-shaving for a shopping list.

Twingate skips the exposure. The Connector dials out to Twingate's network, the Client on your phone dials out too, and the two meet in the middle. Your router's inbound firewall rules stay empty.

The architecture, in one paragraph

You'll run a Connector on your home network (a container on your NAS, a Raspberry Pi, whatever's always on). The Connector makes an outbound connection to Twingate's Controller — no inbound ports needed. You'll define Mealie as a Resource in Twingate (something like mealie.home.lan or its internal IP). You'll install the Twingate Client on your phone, sign in with your identity provider, and the Client will intercept DNS queries for that Mealie address and route only that traffic through the Connector. Everything else on your phone uses the regular internet.

If a direct peer-to-peer connection between phone and Connector is possible, Twingate uses it. If not (think: grocery store Wi-Fi with weird NAT), traffic falls back through a Relay. The Relay doesn't decrypt anything; it just passes encrypted bytes.

Prerequisites

  • A running Mealie instance on your home network (Docker is the common path — the official Mealie installation docs cover it)

  • An internal DNS name for Mealie, or at least its stable internal IP

  • A free Twingate account (the free tier supports up to 5 users, which covers most households)

  • Somewhere on your home network to run the Connector — a Pi, a NAS Docker host, a small VM, or the same host running Mealie

Step 1: Create a Remote Network and Connector

Sign in to the Twingate admin console and create a new Remote Network. Call it home or homelab. Inside that network, add a Connector and choose Docker as the deployment method.

The admin console generates a docker run command with your tokens already filled in. Copy it and run it on your Connector host.

The Connector will show up as "Connected" in the admin console within a few seconds. If you want redundancy (and Twingate recommends two Connectors per Remote Network), run a second container on a different host. Cheap insurance.

Step 2: Add Mealie as a Resource

In the admin console, open your Remote Network and add a new Resource. The address is whatever your phone will try to reach — this is the part that trips people up, so pick one and stick with it:

  • If you have internal DNS (Pi-hole, AdGuard Home, your router's DNS), use a name like mealie.home.lan

  • If you don't, use the internal IP of your Mealie host, e.g. 192.168.1.50

  • If Mealie runs on a non-standard port (the default Docker setup uses 9925), access it as mealie.home.lan:9925. Resources allow all ports by default; you can restrict this one to 9925.

Twingate's Client intercepts DNS queries matching your resource addresses and resolves them through the Connector, so internal DNS names work even from your phone on cellular.

Step 3: Set up a household group and policy

Your partner wants the shopping list, not shell access to your Proxmox box.

Invite your partner from the Users page in the admin console. Then create a Group called something like Household. Add yourself and your partner. Then edit the Mealie Resource and grant access to the Household group. Leave your other Resources (Proxmox UI, Home Assistant, that one Jellyfin instance you never finished setting up) restricted to an Admins group that only contains you.

Twingate enforces this at the Resource level, not the network level. Over Twingate, your partner’s Client only knows about Mealie. It can’t scan your network, reach your router’s admin page, or hit port 22 on your NAS. (On your home Wi-Fi, their phone is on your LAN like any other device.) The Client only knows about what you've explicitly granted.

Step 4: Install the Client on your phones

Install the Twingate iOS or Android app on both phones. Sign in with the account you use for Twingate (Google, Microsoft, or whatever you use). The Client will download the policy and start listening for DNS queries that match your Mealie Resource.

Split tunneling is the default behavior. Only traffic destined for your defined Resources goes through the tunnel. Spotify streams normally. The grocery store's wayfinding app hits the public internet directly.

Open a browser and visit your Mealie URL. If it loads, you're done with the hard part.

Step 5: Add Mealie to the home screen

Mealie is a progressive web app, so you can add it to your home screen on both iOS and Android.

On iOS: open Mealie in Safari (the most reliable path on iOS), tap the share button, and choose "Add to Home Screen." On Android: open it in Chrome, tap the three-dot menu, and choose "Install app" or "Add to Home screen."

What this actually gave you

  • Mealie reachable from anywhere, with your router's inbound firewall rules untouched

  • No public DNS record pointing at your home IP and no internet-facing reverse proxy to patch

  • Your partner has Mealie and only Mealie — the rest of the homelab stays out of sight

  • Split tunneling means only Mealie traffic goes through Twingate

  • When Mealie's next CVE lands, it’s only reachable by people you’ve granted access, not every scanner on the internet. That buys you time to patch.

The architectural point underneath all this: Mealie is not a hardened internet-facing service, and treating it like one is a losing game. Keeping it private and reaching it over a least-privilege tunnel is cheaper, safer, and less work than a port forward plus reverse proxy plus auth layer.

Closing

For the full breakdown of Resources, Groups, and policies, the Twingate documentation has the deep dives on everything used here. The Connector deployment guide covers Docker, systemd, Kubernetes, and the major cloud options if your homelab setup is more involved than a single Pi.

New to Twingate? You can use Twingate for free for up to 5 users, request a personalized demo, or reach out to the team over on the Twingate subreddit.