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
Copy file name to clipboardExpand all lines: documentation/docs/components/operators/snippets/quic-bridge-deployment-script-setup.mdx
+43-3Lines changed: 43 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ import { AccordionTemplate } from 'components/accordion-template.tsx';
6
6
**QUIC bridge is a requirement for all nodes which enable Wireguard functionality. Note that it this feature is compatible with nodes from `v1.18.0` (platform release [`v2025.17-isabirra`](https://github.com/nymtech/nym/releases/tag/nym-binaries-v2025.17-isabirra)) and newer!**
7
7
</ Callout>
8
8
9
-
Nym Network uses various [transport bridges](https://github.com/nymtech/nym-bridges/blob/main/README.md) for routing the packets. Right now operators need to configure [our implementation](https://github.com/nymtech/nym-bridges/tree/main/nym-bridge) of general-purpose transport layer network protocol called [QUIC](https://en.wikipedia.org/wiki/QUIC).
9
+
Nym Network uses various [transport bridges](https://github.com/nymtech/nym-bridges/blob/main/README.md) for routing the packets. Right now operators need to configure [our implementation](https://github.com/nymtech/nym-bridges/tree/main/nym-bridge) of general-purpose transport layer network protocol called [QUIC](https://en.wikipedia.org/wiki/QUIC).
10
10
11
11
Operators can use [Nym Bridge Configuration Tool](https://github.com/nymtech/nym-bridges/tree/main/bridge-cfg) and compile the [Bridge Runner binary](https://github.com/nymtech/nym-bridges/tree/main/nym-bridge) themselves.
12
12
@@ -15,7 +15,7 @@ Operators can use [Nym Bridge Configuration Tool](https://github.com/nymtech/nym
-**For all prompts with default options, we highly recommend to stick to default (press enter)**
38
+
-**For all prompts with default options, we highly recommend to stick to default (press enter)**
39
39
40
40
###### 4. Restart the node service
41
41
- When done with the deployment, please restart your node systemd service
@@ -99,3 +99,43 @@ Quick Start:
99
99
3. Run 'test_bridge_connectivity' to test connectivity
100
100
```
101
101
</AccordionTemplate>
102
+
103
+
### Fixing Metadata Port Showing Not Open in Probe Results
104
+
If you have followed the steps outlined above, but the metadata port is not shown as open in either the Node Status API's probe results or an explorer that gets its data from the API, see below:
105
+
106
+
<Steps>
107
+
###### 1.
108
+
Ensure that in your `config.toml` file, this value is set to the default one - any other value here will cause the metadata endpoint to fail:
109
+
110
+
```
111
+
# Private IP address of the wireguard gateway.
112
+
# default: '10.1.0.1'
113
+
private_ipv4 = '10.1.0.1'
114
+
```
115
+
116
+
Then restart your node.
117
+
118
+
###### 2.
119
+
Run this command if not already done:
120
+
```
121
+
ufw allow in on nymwg to any port 51830 proto tcp
122
+
```
123
+
124
+
Check if the port is open with:
125
+
```
126
+
iptables -S | grep 51830
127
+
```
128
+
129
+
Then ensure the metadata endpoint is listening from the correct address with:
130
+
```
131
+
netstat -an | egrep LISTEN | egrep "51830"
132
+
```
133
+
134
+
###### 3.
135
+
Once the Node Status API has run a probe on your node, the probe results will reflect this - `can_query_metadata_v4` will have `true` as a value.
136
+
137
+
The quickest way to check this is by using the [NymVPN API](https://nymvpn.com/api/public/v1/directory/gateways?show_vpn_only=true) and checking the same field:
0 commit comments