You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Perry automatically detects and integrates with [Tailscale](https://tailscale.com) to provide secure HTTPS access to your workspaces over your private network.
4
+
5
+
## How It Works
6
+
7
+
When you start the Perry agent, it checks if Tailscale is running on your machine. If Tailscale is detected with HTTPS enabled, Perry automatically starts [Tailscale Serve](https://tailscale.com/kb/1312/serve) to expose the agent over HTTPS using your Tailscale domain.
8
+
9
+
This gives you:
10
+
-**Trusted HTTPS certificates** - No browser warnings, valid certificates from Let's Encrypt
11
+
-**Private network access** - Access Perry from any device on your tailnet
12
+
-**User identity** - Perry can identify who's making requests via Tailscale headers
13
+
14
+
## Setup
15
+
16
+
### 1. Install Tailscale
17
+
18
+
Follow the [Tailscale installation guide](https://tailscale.com/download) for your platform.
19
+
20
+
### 2. Enable HTTPS Certificates
21
+
22
+
Tailscale HTTPS must be enabled for your tailnet. This is typically enabled by default, but you can verify in your [Tailscale admin console](https://login.tailscale.com/admin/dns).
23
+
24
+
### 3. Set Operator Permissions (Required)
25
+
26
+
By default, Tailscale Serve requires root permissions. To allow Perry to use it without sudo, run:
[agent] To enable: Run: sudo tailscale set --operator=$USER
58
+
[agent] Continuing without HTTPS...
59
+
```
60
+
61
+
**Fix:** Run `sudo tailscale set --operator=$USER` and restart the agent.
62
+
63
+
### "Tailscale HTTPS not enabled in tailnet"
64
+
65
+
Your tailnet doesn't have HTTPS certificates enabled. Check your [Tailscale admin DNS settings](https://login.tailscale.com/admin/dns) and ensure "HTTPS Certificates" is enabled.
66
+
67
+
### Tailscale Not Detected
68
+
69
+
If Perry doesn't detect Tailscale at all, verify Tailscale is running:
70
+
71
+
```bash
72
+
tailscale status
73
+
```
74
+
75
+
## Graceful Fallback
76
+
77
+
Perry always starts successfully regardless of Tailscale status:
78
+
79
+
| Scenario | Behavior |
80
+
|----------|----------|
81
+
| Tailscale not installed | Agent starts normally on localhost |
82
+
| Tailscale running, HTTPS enabled, operator set | HTTPS via Tailscale Serve |
83
+
| Tailscale running, HTTPS enabled, no operator | Logs fix instructions, falls back to localhost |
84
+
| Tailscale running, HTTPS not enabled | Falls back to localhost |
85
+
86
+
## Security Considerations
87
+
88
+
When using Tailscale Serve:
89
+
- Traffic is encrypted end-to-end within your tailnet
90
+
- Perry can identify users via `Tailscale-User-*` headers
91
+
- Access is limited to devices on your tailnet
92
+
93
+
Without Tailscale, Perry binds to localhost only by default. For remote access without Tailscale, consider using a reverse proxy with proper authentication.
0 commit comments