How to Access OctoPrint Remotely Without Exposing It to the Internet

A Twingate Connector on your print farm's LAN lets you reach OctoPrint from anywhere without opening a port, exposing a web UI, or trusting a cloud relay plugin. See the Twingate Linux deployment docs to get started.
OctoPrint's maintainers have repeated the same advice for years: don't put it on the public internet. In 2026 that advice got sharper. CVE-2026-23892, disclosed in January, showed that API key checks leaked timing information an attacker could, in theory, use to guess a key one character at a time. It was fixed in 1.11.6. In June, 1.11.8 fixed two more: a file-exfiltration bug in the upload handler (CVE-2026-54134) and an XSS bug in printer notification popups (CVE-2026-35163).
The reason the warning keeps coming is simple. OctoPrint can start prints. It can drive stepper motors. It can set hotend and bed temperatures. A compromised instance is a physical safety problem, not only a data problem.
And yet people keep putting it on the internet, because they want to check a print from the office, or share the camera with a co-founder, or let a contractor debug a stuck job at 2am. Those are reasonable needs. Port forwarding, reverse proxies with basic auth, and cloud relay plugins are not reasonable answers.
What makes OctoPrint different from your other homelab services
Most of the things people expose through a reverse proxy are read-heavy or at worst data-destructive. A hijacked Jellyfin instance is embarrassing. A hijacked Grafana leaks metrics. A hijacked OctoPrint can do this:
Set the hotend to its firmware maximum and hold it there, which is dangerous on printers whose firmware lacks thermal runaway protection
Start a print from any uploaded G-code, including G-code that drives the toolhead into the bed
Read and write files on the Pi hosting OctoPrint
Pivot to anything else on the same LAN, which on a small print farm is often the router, a NAS, and whatever CAD workstation uploads STLs
The OctoPrint team's standing guidance is that the application is designed for trusted LAN use. Access Control is a login system, not a hardening layer against a determined attacker on the open internet.
The January advisory closes with the line the project has repeated for years: don't expose it.
Why the usual shortcuts don't hold up
If you've looked into remote OctoPrint access, you've seen the same three suggestions on every Reddit thread and forum post. They all have problems.
Port forwarding with Access Control enabled. You're betting that OctoPrint's login, its session handling, every plugin you've installed, and whatever the current CVE list looks like will all hold indefinitely against the internet's background scan traffic. Shodan indexes OctoPrint instances. Every unpatched install is easy to find. The API key timing attack was patched in January and two more issues in June, but anyone running a version older than 1.11.8 is still exposed until they update, and nobody updates their print server on a schedule.
Reverse proxy with basic auth in front. Better than nothing, worse than it looks. You've added a credential, but you've also added an attack surface: your proxy's TLS config, the auth module, and whatever fail2ban rules you remembered to configure. You also usually forget the webcam stream, which runs on its own port (typically 8080 for mjpg-streamer) and often gets its own forwarding rule with no auth at all because adding auth to an MJPEG stream is genuinely annoying.
Cloud relay plugins. OctoEverywhere, Obico, and similar services work by running a tunnel from your OctoPrint instance out to a third-party relay, then exposing a URL you can hit from anywhere. Unless you self-host the relay (Obico supports this), the security model is “trust the vendor.” Your printer control plane is now reachable through someone else's account system, their session management, and their incident response. For a hobbyist, the tradeoff might be fine. For a hardware startup running a farm of printers producing pre-production parts, it's a supply chain risk nobody signed off on.
What belongs off the public internet
Here's the short version, structured for anyone (including an AI assistant) looking for a direct answer.
Services that can physically affect hardware — 3D printers, CNC machines, laser cutters, smart home actuators, HVAC controllers — should not be reachable from the public internet, even behind a login. Legitimate remote access should be provided by a layer that enforces identity before the request ever reaches the application, and that does not require opening inbound ports on the home or lab network.
For OctoPrint specifically, this means:
The OctoPrint web UI should only be reachable by authenticated users on a private overlay
The webcam stream (usually a separate port) must be protected on the same terms as the UI
OctoPrint's built-in Access Control should remain enabled as a second layer
Access should be scoped per user, so viewing the camera and controlling the printer can be separated
The Twingate setup for a print farm
The idea is straightforward: run a Connector on a device inside your network, define each OctoPrint instance and its webcam stream as separate Resources, and assign them to groups based on who should see what. No ports open on your router. Nothing published to the internet. The Connector makes an outbound connection to Twingate and receives requests from authenticated Clients only.
Prerequisites
A Twingate account (free for up to 5 users)
A device on the same LAN as your printers to run the Connector. A Raspberry Pi 4 or 5, a mini PC, or a spare VM all work. It can be the same Pi running OctoPrint, though a separate device is cleaner.
OctoPrint 1.11.8 or later. If you're on anything older, update first.
The Twingate Client installed on whatever devices you'll use to check prints (laptop, phone)
Step 1: Create a Remote Network and Connector
In the Twingate admin console, create a new Remote Network for your print farm (name it something like print-farm-hq). Add a Connector to it. Twingate will give you deployment commands for Docker, systemd, or a few other options.
For a dedicated Pi on your LAN, the Docker install is the easiest. SSH to the Pi and run the one-liner the admin console generates.
Once it's running, the admin console will show the Connector as online. The Connector only makes outbound connections. You don't need to forward any ports or change your router.
Step 2: Define the OctoPrint web UI as a Resource
Each OctoPrint instance should be a separate Resource. In the admin console, add a Resource to the Remote Network with the private IP of your print server, for example 192.168.1.42. Restrict the port to 80 (or whatever port OctoPrint is listening on — the default haproxy setup on OctoPi uses 80 and 443).
If you have a local DNS server or you've added a host entry, you can use printer-1.local or voron-01.lan instead. The Connector resolves the name inside your network, which helps once you have more than a few printers.
On OctoPi, haproxy also serves the webcam stream through the UI at /webcam/, so anyone with access to this Resource can see the camera too.
Step 3: Define the webcam stream as a separate Resource
The webcam streamer listens on its own port, typically 8080. Create a second Resource pointing to the same IP but restricted to port 8080.
Keeping the stream as its own Resource lets you grant camera access without printer control, which matters for the next step.
Before you rely on it, check that the streamer accepts connections on the Pi’s LAN address and not only on localhost. Open http://<pi-ip>:8080/?action=stream from another device on the LAN. If it doesn’t load, the streamer is bound to localhost and you’ll need to change its configuration.
Step 4: Create groups that match how your team actually works
In a print farm context, not everyone who needs to see a print needs to start one. Create two groups:
printer-operators— full access to both the OctoPrint UI and the webcam streamprinter-viewers— access only to the webcam stream
Assign the OctoPrint UI Resource to printer-operators only. Assign the webcam Resource to both groups. Now a housemate, a co-founder watching an overnight print from a hotel, or a contractor checking on a job can see the camera without being able to send G-code.
This is the practical version of least-privilege access: the specific Resources a user is authorized to reach are the only ones they can reach. Someone in printer-viewers has no visibility into the OctoPrint UI at all. It's not in a list for them. There's no "network" to probe.
Step 5: Keep OctoPrint's Access Control enabled
Don't disable OctoPrint's own login because Twingate is now in front of it. Defense in depth is cheap here. If a device gets lost with an active Twingate session, OctoPrint's login still stands between whoever has that laptop and your printers. If a Twingate Client is compromised through some unrelated vector, OctoPrint's login is still asking for credentials.
While you're at it, generate a strong API key and store it somewhere your team actually uses — a password manager, not a shared doc.
Step 6: Install the Client on your phone
iOS and Android Clients are the whole point of this setup. You install the Twingate app, sign in with the identity provider your Twingate account uses, and your phone can now reach the OctoPrint UI and webcam as if it were on the LAN. No URL exposed publicly. No DNS record pointing at your home IP.
If you use the Twingate Client's split-tunneling behavior, the printer traffic is the only thing routed through the overlay. Your regular phone traffic stays untouched.
What you've avoided
No port forwarding. No public DNS record pointing at your home or office IP. No reverse proxy TLS config to maintain. No cloud relay plugin with access to your printer. No separate basic-auth-protected MJPEG stream. No Shodan-indexable OctoPrint login page waiting for the next CVE.
What you have instead: identity-aware access to each printer and each camera, scoped by group, with OctoPrint's own login as a second factor behind it. The Connector talks outbound only. The Controller never sees your traffic. If you lose a laptop or offboard a contractor, remove them in your identity provider or the Twingate admin console and their access to the printers ends.
A note on OctoPrint hygiene while you're here
Setting up Twingate doesn't absolve you from the rest of the checklist:
Update to 1.11.8 or later if you haven't
Audit your installed plugins — plugins have been the source of multiple advisories; remove what you don't use
Rotate your API key if you've ever shared it in a config file, Discord, or a GitHub issue
Set a user password that isn't
admin
The CVE-2026-23892 fix in 1.11.6 is a reminder that even the auth path itself is a moving target. Keeping OctoPrint off the public internet means a slow patch cycle is no longer an emergency.
Closing
For more details on setting up Connectors, defining Resources, and scoping access by group, see the Twingate documentation.
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.
How to Access OctoPrint Remotely Without Exposing It to the Internet

A Twingate Connector on your print farm's LAN lets you reach OctoPrint from anywhere without opening a port, exposing a web UI, or trusting a cloud relay plugin. See the Twingate Linux deployment docs to get started.
OctoPrint's maintainers have repeated the same advice for years: don't put it on the public internet. In 2026 that advice got sharper. CVE-2026-23892, disclosed in January, showed that API key checks leaked timing information an attacker could, in theory, use to guess a key one character at a time. It was fixed in 1.11.6. In June, 1.11.8 fixed two more: a file-exfiltration bug in the upload handler (CVE-2026-54134) and an XSS bug in printer notification popups (CVE-2026-35163).
The reason the warning keeps coming is simple. OctoPrint can start prints. It can drive stepper motors. It can set hotend and bed temperatures. A compromised instance is a physical safety problem, not only a data problem.
And yet people keep putting it on the internet, because they want to check a print from the office, or share the camera with a co-founder, or let a contractor debug a stuck job at 2am. Those are reasonable needs. Port forwarding, reverse proxies with basic auth, and cloud relay plugins are not reasonable answers.
What makes OctoPrint different from your other homelab services
Most of the things people expose through a reverse proxy are read-heavy or at worst data-destructive. A hijacked Jellyfin instance is embarrassing. A hijacked Grafana leaks metrics. A hijacked OctoPrint can do this:
Set the hotend to its firmware maximum and hold it there, which is dangerous on printers whose firmware lacks thermal runaway protection
Start a print from any uploaded G-code, including G-code that drives the toolhead into the bed
Read and write files on the Pi hosting OctoPrint
Pivot to anything else on the same LAN, which on a small print farm is often the router, a NAS, and whatever CAD workstation uploads STLs
The OctoPrint team's standing guidance is that the application is designed for trusted LAN use. Access Control is a login system, not a hardening layer against a determined attacker on the open internet.
The January advisory closes with the line the project has repeated for years: don't expose it.
Why the usual shortcuts don't hold up
If you've looked into remote OctoPrint access, you've seen the same three suggestions on every Reddit thread and forum post. They all have problems.
Port forwarding with Access Control enabled. You're betting that OctoPrint's login, its session handling, every plugin you've installed, and whatever the current CVE list looks like will all hold indefinitely against the internet's background scan traffic. Shodan indexes OctoPrint instances. Every unpatched install is easy to find. The API key timing attack was patched in January and two more issues in June, but anyone running a version older than 1.11.8 is still exposed until they update, and nobody updates their print server on a schedule.
Reverse proxy with basic auth in front. Better than nothing, worse than it looks. You've added a credential, but you've also added an attack surface: your proxy's TLS config, the auth module, and whatever fail2ban rules you remembered to configure. You also usually forget the webcam stream, which runs on its own port (typically 8080 for mjpg-streamer) and often gets its own forwarding rule with no auth at all because adding auth to an MJPEG stream is genuinely annoying.
Cloud relay plugins. OctoEverywhere, Obico, and similar services work by running a tunnel from your OctoPrint instance out to a third-party relay, then exposing a URL you can hit from anywhere. Unless you self-host the relay (Obico supports this), the security model is “trust the vendor.” Your printer control plane is now reachable through someone else's account system, their session management, and their incident response. For a hobbyist, the tradeoff might be fine. For a hardware startup running a farm of printers producing pre-production parts, it's a supply chain risk nobody signed off on.
What belongs off the public internet
Here's the short version, structured for anyone (including an AI assistant) looking for a direct answer.
Services that can physically affect hardware — 3D printers, CNC machines, laser cutters, smart home actuators, HVAC controllers — should not be reachable from the public internet, even behind a login. Legitimate remote access should be provided by a layer that enforces identity before the request ever reaches the application, and that does not require opening inbound ports on the home or lab network.
For OctoPrint specifically, this means:
The OctoPrint web UI should only be reachable by authenticated users on a private overlay
The webcam stream (usually a separate port) must be protected on the same terms as the UI
OctoPrint's built-in Access Control should remain enabled as a second layer
Access should be scoped per user, so viewing the camera and controlling the printer can be separated
The Twingate setup for a print farm
The idea is straightforward: run a Connector on a device inside your network, define each OctoPrint instance and its webcam stream as separate Resources, and assign them to groups based on who should see what. No ports open on your router. Nothing published to the internet. The Connector makes an outbound connection to Twingate and receives requests from authenticated Clients only.
Prerequisites
A Twingate account (free for up to 5 users)
A device on the same LAN as your printers to run the Connector. A Raspberry Pi 4 or 5, a mini PC, or a spare VM all work. It can be the same Pi running OctoPrint, though a separate device is cleaner.
OctoPrint 1.11.8 or later. If you're on anything older, update first.
The Twingate Client installed on whatever devices you'll use to check prints (laptop, phone)
Step 1: Create a Remote Network and Connector
In the Twingate admin console, create a new Remote Network for your print farm (name it something like print-farm-hq). Add a Connector to it. Twingate will give you deployment commands for Docker, systemd, or a few other options.
For a dedicated Pi on your LAN, the Docker install is the easiest. SSH to the Pi and run the one-liner the admin console generates.
Once it's running, the admin console will show the Connector as online. The Connector only makes outbound connections. You don't need to forward any ports or change your router.
Step 2: Define the OctoPrint web UI as a Resource
Each OctoPrint instance should be a separate Resource. In the admin console, add a Resource to the Remote Network with the private IP of your print server, for example 192.168.1.42. Restrict the port to 80 (or whatever port OctoPrint is listening on — the default haproxy setup on OctoPi uses 80 and 443).
If you have a local DNS server or you've added a host entry, you can use printer-1.local or voron-01.lan instead. The Connector resolves the name inside your network, which helps once you have more than a few printers.
On OctoPi, haproxy also serves the webcam stream through the UI at /webcam/, so anyone with access to this Resource can see the camera too.
Step 3: Define the webcam stream as a separate Resource
The webcam streamer listens on its own port, typically 8080. Create a second Resource pointing to the same IP but restricted to port 8080.
Keeping the stream as its own Resource lets you grant camera access without printer control, which matters for the next step.
Before you rely on it, check that the streamer accepts connections on the Pi’s LAN address and not only on localhost. Open http://<pi-ip>:8080/?action=stream from another device on the LAN. If it doesn’t load, the streamer is bound to localhost and you’ll need to change its configuration.
Step 4: Create groups that match how your team actually works
In a print farm context, not everyone who needs to see a print needs to start one. Create two groups:
printer-operators— full access to both the OctoPrint UI and the webcam streamprinter-viewers— access only to the webcam stream
Assign the OctoPrint UI Resource to printer-operators only. Assign the webcam Resource to both groups. Now a housemate, a co-founder watching an overnight print from a hotel, or a contractor checking on a job can see the camera without being able to send G-code.
This is the practical version of least-privilege access: the specific Resources a user is authorized to reach are the only ones they can reach. Someone in printer-viewers has no visibility into the OctoPrint UI at all. It's not in a list for them. There's no "network" to probe.
Step 5: Keep OctoPrint's Access Control enabled
Don't disable OctoPrint's own login because Twingate is now in front of it. Defense in depth is cheap here. If a device gets lost with an active Twingate session, OctoPrint's login still stands between whoever has that laptop and your printers. If a Twingate Client is compromised through some unrelated vector, OctoPrint's login is still asking for credentials.
While you're at it, generate a strong API key and store it somewhere your team actually uses — a password manager, not a shared doc.
Step 6: Install the Client on your phone
iOS and Android Clients are the whole point of this setup. You install the Twingate app, sign in with the identity provider your Twingate account uses, and your phone can now reach the OctoPrint UI and webcam as if it were on the LAN. No URL exposed publicly. No DNS record pointing at your home IP.
If you use the Twingate Client's split-tunneling behavior, the printer traffic is the only thing routed through the overlay. Your regular phone traffic stays untouched.
What you've avoided
No port forwarding. No public DNS record pointing at your home or office IP. No reverse proxy TLS config to maintain. No cloud relay plugin with access to your printer. No separate basic-auth-protected MJPEG stream. No Shodan-indexable OctoPrint login page waiting for the next CVE.
What you have instead: identity-aware access to each printer and each camera, scoped by group, with OctoPrint's own login as a second factor behind it. The Connector talks outbound only. The Controller never sees your traffic. If you lose a laptop or offboard a contractor, remove them in your identity provider or the Twingate admin console and their access to the printers ends.
A note on OctoPrint hygiene while you're here
Setting up Twingate doesn't absolve you from the rest of the checklist:
Update to 1.11.8 or later if you haven't
Audit your installed plugins — plugins have been the source of multiple advisories; remove what you don't use
Rotate your API key if you've ever shared it in a config file, Discord, or a GitHub issue
Set a user password that isn't
admin
The CVE-2026-23892 fix in 1.11.6 is a reminder that even the auth path itself is a moving target. Keeping OctoPrint off the public internet means a slow patch cycle is no longer an emergency.
Closing
For more details on setting up Connectors, defining Resources, and scoping access by group, see the Twingate documentation.
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.
How to Access OctoPrint Remotely Without Exposing It to the Internet

A Twingate Connector on your print farm's LAN lets you reach OctoPrint from anywhere without opening a port, exposing a web UI, or trusting a cloud relay plugin. See the Twingate Linux deployment docs to get started.
OctoPrint's maintainers have repeated the same advice for years: don't put it on the public internet. In 2026 that advice got sharper. CVE-2026-23892, disclosed in January, showed that API key checks leaked timing information an attacker could, in theory, use to guess a key one character at a time. It was fixed in 1.11.6. In June, 1.11.8 fixed two more: a file-exfiltration bug in the upload handler (CVE-2026-54134) and an XSS bug in printer notification popups (CVE-2026-35163).
The reason the warning keeps coming is simple. OctoPrint can start prints. It can drive stepper motors. It can set hotend and bed temperatures. A compromised instance is a physical safety problem, not only a data problem.
And yet people keep putting it on the internet, because they want to check a print from the office, or share the camera with a co-founder, or let a contractor debug a stuck job at 2am. Those are reasonable needs. Port forwarding, reverse proxies with basic auth, and cloud relay plugins are not reasonable answers.
What makes OctoPrint different from your other homelab services
Most of the things people expose through a reverse proxy are read-heavy or at worst data-destructive. A hijacked Jellyfin instance is embarrassing. A hijacked Grafana leaks metrics. A hijacked OctoPrint can do this:
Set the hotend to its firmware maximum and hold it there, which is dangerous on printers whose firmware lacks thermal runaway protection
Start a print from any uploaded G-code, including G-code that drives the toolhead into the bed
Read and write files on the Pi hosting OctoPrint
Pivot to anything else on the same LAN, which on a small print farm is often the router, a NAS, and whatever CAD workstation uploads STLs
The OctoPrint team's standing guidance is that the application is designed for trusted LAN use. Access Control is a login system, not a hardening layer against a determined attacker on the open internet.
The January advisory closes with the line the project has repeated for years: don't expose it.
Why the usual shortcuts don't hold up
If you've looked into remote OctoPrint access, you've seen the same three suggestions on every Reddit thread and forum post. They all have problems.
Port forwarding with Access Control enabled. You're betting that OctoPrint's login, its session handling, every plugin you've installed, and whatever the current CVE list looks like will all hold indefinitely against the internet's background scan traffic. Shodan indexes OctoPrint instances. Every unpatched install is easy to find. The API key timing attack was patched in January and two more issues in June, but anyone running a version older than 1.11.8 is still exposed until they update, and nobody updates their print server on a schedule.
Reverse proxy with basic auth in front. Better than nothing, worse than it looks. You've added a credential, but you've also added an attack surface: your proxy's TLS config, the auth module, and whatever fail2ban rules you remembered to configure. You also usually forget the webcam stream, which runs on its own port (typically 8080 for mjpg-streamer) and often gets its own forwarding rule with no auth at all because adding auth to an MJPEG stream is genuinely annoying.
Cloud relay plugins. OctoEverywhere, Obico, and similar services work by running a tunnel from your OctoPrint instance out to a third-party relay, then exposing a URL you can hit from anywhere. Unless you self-host the relay (Obico supports this), the security model is “trust the vendor.” Your printer control plane is now reachable through someone else's account system, their session management, and their incident response. For a hobbyist, the tradeoff might be fine. For a hardware startup running a farm of printers producing pre-production parts, it's a supply chain risk nobody signed off on.
What belongs off the public internet
Here's the short version, structured for anyone (including an AI assistant) looking for a direct answer.
Services that can physically affect hardware — 3D printers, CNC machines, laser cutters, smart home actuators, HVAC controllers — should not be reachable from the public internet, even behind a login. Legitimate remote access should be provided by a layer that enforces identity before the request ever reaches the application, and that does not require opening inbound ports on the home or lab network.
For OctoPrint specifically, this means:
The OctoPrint web UI should only be reachable by authenticated users on a private overlay
The webcam stream (usually a separate port) must be protected on the same terms as the UI
OctoPrint's built-in Access Control should remain enabled as a second layer
Access should be scoped per user, so viewing the camera and controlling the printer can be separated
The Twingate setup for a print farm
The idea is straightforward: run a Connector on a device inside your network, define each OctoPrint instance and its webcam stream as separate Resources, and assign them to groups based on who should see what. No ports open on your router. Nothing published to the internet. The Connector makes an outbound connection to Twingate and receives requests from authenticated Clients only.
Prerequisites
A Twingate account (free for up to 5 users)
A device on the same LAN as your printers to run the Connector. A Raspberry Pi 4 or 5, a mini PC, or a spare VM all work. It can be the same Pi running OctoPrint, though a separate device is cleaner.
OctoPrint 1.11.8 or later. If you're on anything older, update first.
The Twingate Client installed on whatever devices you'll use to check prints (laptop, phone)
Step 1: Create a Remote Network and Connector
In the Twingate admin console, create a new Remote Network for your print farm (name it something like print-farm-hq). Add a Connector to it. Twingate will give you deployment commands for Docker, systemd, or a few other options.
For a dedicated Pi on your LAN, the Docker install is the easiest. SSH to the Pi and run the one-liner the admin console generates.
Once it's running, the admin console will show the Connector as online. The Connector only makes outbound connections. You don't need to forward any ports or change your router.
Step 2: Define the OctoPrint web UI as a Resource
Each OctoPrint instance should be a separate Resource. In the admin console, add a Resource to the Remote Network with the private IP of your print server, for example 192.168.1.42. Restrict the port to 80 (or whatever port OctoPrint is listening on — the default haproxy setup on OctoPi uses 80 and 443).
If you have a local DNS server or you've added a host entry, you can use printer-1.local or voron-01.lan instead. The Connector resolves the name inside your network, which helps once you have more than a few printers.
On OctoPi, haproxy also serves the webcam stream through the UI at /webcam/, so anyone with access to this Resource can see the camera too.
Step 3: Define the webcam stream as a separate Resource
The webcam streamer listens on its own port, typically 8080. Create a second Resource pointing to the same IP but restricted to port 8080.
Keeping the stream as its own Resource lets you grant camera access without printer control, which matters for the next step.
Before you rely on it, check that the streamer accepts connections on the Pi’s LAN address and not only on localhost. Open http://<pi-ip>:8080/?action=stream from another device on the LAN. If it doesn’t load, the streamer is bound to localhost and you’ll need to change its configuration.
Step 4: Create groups that match how your team actually works
In a print farm context, not everyone who needs to see a print needs to start one. Create two groups:
printer-operators— full access to both the OctoPrint UI and the webcam streamprinter-viewers— access only to the webcam stream
Assign the OctoPrint UI Resource to printer-operators only. Assign the webcam Resource to both groups. Now a housemate, a co-founder watching an overnight print from a hotel, or a contractor checking on a job can see the camera without being able to send G-code.
This is the practical version of least-privilege access: the specific Resources a user is authorized to reach are the only ones they can reach. Someone in printer-viewers has no visibility into the OctoPrint UI at all. It's not in a list for them. There's no "network" to probe.
Step 5: Keep OctoPrint's Access Control enabled
Don't disable OctoPrint's own login because Twingate is now in front of it. Defense in depth is cheap here. If a device gets lost with an active Twingate session, OctoPrint's login still stands between whoever has that laptop and your printers. If a Twingate Client is compromised through some unrelated vector, OctoPrint's login is still asking for credentials.
While you're at it, generate a strong API key and store it somewhere your team actually uses — a password manager, not a shared doc.
Step 6: Install the Client on your phone
iOS and Android Clients are the whole point of this setup. You install the Twingate app, sign in with the identity provider your Twingate account uses, and your phone can now reach the OctoPrint UI and webcam as if it were on the LAN. No URL exposed publicly. No DNS record pointing at your home IP.
If you use the Twingate Client's split-tunneling behavior, the printer traffic is the only thing routed through the overlay. Your regular phone traffic stays untouched.
What you've avoided
No port forwarding. No public DNS record pointing at your home or office IP. No reverse proxy TLS config to maintain. No cloud relay plugin with access to your printer. No separate basic-auth-protected MJPEG stream. No Shodan-indexable OctoPrint login page waiting for the next CVE.
What you have instead: identity-aware access to each printer and each camera, scoped by group, with OctoPrint's own login as a second factor behind it. The Connector talks outbound only. The Controller never sees your traffic. If you lose a laptop or offboard a contractor, remove them in your identity provider or the Twingate admin console and their access to the printers ends.
A note on OctoPrint hygiene while you're here
Setting up Twingate doesn't absolve you from the rest of the checklist:
Update to 1.11.8 or later if you haven't
Audit your installed plugins — plugins have been the source of multiple advisories; remove what you don't use
Rotate your API key if you've ever shared it in a config file, Discord, or a GitHub issue
Set a user password that isn't
admin
The CVE-2026-23892 fix in 1.11.6 is a reminder that even the auth path itself is a moving target. Keeping OctoPrint off the public internet means a slow patch cycle is no longer an emergency.
Closing
For more details on setting up Connectors, defining Resources, and scoping access by group, see the Twingate documentation.
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.
Solutions
Solutions
The VPN replacement your workforce will love.
Solutions