Skip to content

Cassiiopeia/projectops / plugins/projectops-extras/skills/pro-synology-expose

pro-synology-expose

Verified

Guide to expose a new web service from a Synology NAS on an external domain: DNS record, DSM reverse proxy, Let's Encrypt certificate. Use for 'expose service', 'connect domain', 'add reverse proxy'.

FileKindSize
SKILL.mdskill md5.3 KB
references/certificate.mdmarkdown2.0 KB
references/dns.mdmarkdown1.3 KB
references/reverse-proxy.mdmarkdown4.2 KB

references/reverse-proxy.md

View on GitHub
> When to read: when you build the Step 2 (DSM reverse proxy) guide. Field tables for the 2 rules, the 9 WebSocket headers and advanced settings, and output examples (regular and WebSocket).

## Step 2: Synology DSM reverse proxy setup

**Location**: DSM > Control Panel > Login Portal > Advanced tab > Reverse Proxy > "Create"
(Korean DSM: 제어판 > 로그인 포털 > 고급 > 역방향 프록시 > "생성")

Create **2 rules** in total: one for HTTPS (443) and one for the HTTP→HTTPS redirect (80→443).

### Contents

- [Rule 1: HTTPS proxy (443 → local port)](#rule-1-https-proxy-443--local-port)
- [Rule 2: HTTP → HTTPS redirect (80 → 443)](#rule-2-http--https-redirect-80--443)
- [(Conditional) Extra settings for WebSocket services](#conditional-extra-settings-for-websocket-services)
- [Output example (regular service)](#output-example-regular-service)
- [Output example (WebSocket service)](#output-example-websocket-service)

### Rule 1: HTTPS proxy (443 → local port)

**General tab:**

| Field | Value |
|------|-----|
| Reverse proxy name | `{service_name} 443→{local_port}` |
| **Source** | |
| Protocol | `HTTPS` |
| Hostname | `{subdomain}.{domain}` |
| Port | `443` |
| Enable HSTS | checked |
| Access control profile | `Not configured` |
| **Destination** | |
| Protocol | `HTTP` |
| Hostname | `localhost` |
| Port | `{local_port}` |

### Rule 2: HTTP → HTTPS redirect (80 → 443)

**General tab:**

| Field | Value |
|------|-----|
| Reverse proxy name | `{service_name} 80→443` |
| **Source** | |
| Protocol | `HTTP` |
| Hostname | `{subdomain}.{domain}` |
| Port | `80` |
| Enable HSTS | unchecked |
| **Destination** | |
| Protocol | `HTTPS` |
| Hostname | `{subdomain}.{domain}` |
| Port | `443` |

---

### (Conditional) Extra settings for WebSocket services

Add the settings below to **Rule 1 (the HTTPS proxy)** only when the service uses WebSocket. Skip this section for regular services that do not use WebSocket.

#### Custom Header tab

Press "Create" and add all 9 headers below:

| Header name | Value |
|-------------|-----|
| `Upgrade` | `$http_upgrade` |
| `Connection` | `$connection_upgrade` |
| `Sec-WebSocket-Key` | `$http_sec_websocket_key` |
| `Sec-WebSocket-Version` | `13` |
| `Sec-WebSocket-Extensions` | `$http_sec_websocket_extensions` |
| `X-Forwarded-Proto` | `https` |
| `X-Forwarded-For` | `$proxy_add_x_forwarded_for` |
| `Authorization` | `$http_authorization` |
| `Proxy-Authorization` | `$http_authorization` |

#### Advanced Settings tab (optional)

The default timeout is 60 seconds. If the service has operations that take longer than 60 seconds, raise it to the value the user gave.

| Field | Value |
|------|-----|
| Proxy connection timeout (s) | `{timeout}` (default 60) |
| Proxy send timeout (s) | `{timeout}` (default 60) |
| Proxy read timeout (s) | `{timeout}` (default 60) |
| Proxy HTTP version | `HTTP 1.1` |
| Use the error page sent back from the destination server | checked |

---

### Output example (regular service)

```
[Step 2] Reverse proxy setup (create 2)

[Rule 1] {service_name} 443→{local_port}
  General tab:
    Source: HTTPS://{subdomain}.{domain}:443 (HSTS enabled)
    Destination: HTTP://localhost:{local_port}

[Rule 2] {service_name} 80→443
  General tab:
    Source: HTTP://{subdomain}.{domain}:80
    Destination: HTTPS://{subdomain}.{domain}:443
```

### Output example (WebSocket service)

```
[Step 2] Reverse proxy setup (create 2)

[Rule 1] {service_name} 443→{local_port}
  General tab:
    Source: HTTPS://{subdomain}.{domain}:443 (HSTS enabled)
    Destination: HTTP://localhost:{local_port}
  Custom Header tab (add 9):
    Upgrade: $http_upgrade
    Connection: $connection_upgrade
    Sec-WebSocket-Key: $http_sec_websocket_key
    Sec-WebSocket-Version: 13
    Sec-WebSocket-Extensions: $http_sec_websocket_extensions
    X-Forwarded-Proto: https
    X-Forwarded-For: $proxy_add_x_forwarded_for
    Authorization: $http_authorization
    Proxy-Authorization: $http_authorization
  Advanced Settings tab:
    Proxy connection/send/read timeout: {timeout}s
    Proxy HTTP version: HTTP 1.1
    Use destination server's error page: checked

[Rule 2] {service_name} 80→443
  General tab:
    Source: HTTP://{subdomain}.{domain}:80
    Destination: HTTPS://{subdomain}.{domain}:443
```
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall