github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-06 00:22:42 -05:00
Code Issues 464 Packages Projects Releases 71 Wiki Activity

[GH-ISSUE #766] cant connect newt site to pangolin #1617

New Issue
Closed
opened 2026-04-16 08:20:14 -05:00 by GiteaMirror · 11 comments
GiteaMirror commented 2026-04-16 08:20:14 -05:00
Owner
Copy Link

Originally created by @flowy0 on GitHub (May 22, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/766

I am unable to connect a newt site to pangolin.

Deployed Pangolin on VPS
Installed Newt via docker compose on NAS(Portainer)
It seems like it's unable to reach the tunnel IP.

Edit: I was able to connect a separate VM running on a proxomox server (same network)

Errors

INFO: 2025/05/22 08:55:19 Received: {Type:newt/wg/connect Data:map[endpoint:<site-name>:51820 publicKey:<> serverIP:<ip> targets:map[tcp:[] udp:[]] tunnelIP:<ip2>]}

INFO: 2025/05/22 08:55:19 WireGuard device created. Lets ping the server now...


WARN: 2025/05/22 08:59:40 Ping attempt 19 failed: failed to read ICMP packet: i/o timeout

INFO: 2025/05/22 08:59:46 Ping attempt 20
Originally created by @flowy0 on GitHub (May 22, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/766 I am unable to connect a newt site to pangolin. Deployed Pangolin on VPS Installed Newt via docker compose on NAS(Portainer) It seems like it's unable to reach the tunnel IP. Edit: I was able to connect a separate VM running on a proxomox server (same network) Errors ``` INFO: 2025/05/22 08:55:19 Received: {Type:newt/wg/connect Data:map[endpoint:<site-name>:51820 publicKey:<> serverIP:<ip> targets:map[tcp:[] udp:[]] tunnelIP:<ip2>]} INFO: 2025/05/22 08:55:19 WireGuard device created. Lets ping the server now... WARN: 2025/05/22 08:59:40 Ping attempt 19 failed: failed to read ICMP packet: i/o timeout INFO: 2025/05/22 08:59:46 Ping attempt 20 ```
GiteaMirror commented 2026-04-16 08:20:15 -05:00
Author
Owner
Copy Link

@samumatic commented on GitHub (May 22, 2025):

Can you show your compose.yaml of Newt and an nmap scan of the VPS?

<!-- gh-comment-id:2901227820 --> @samumatic commented on GitHub (May 22, 2025): Can you show your compose.yaml of Newt and an nmap scan of the VPS?
GiteaMirror commented 2026-04-16 08:20:15 -05:00
Author
Owner
Copy Link

@flowy0 commented on GitHub (May 23, 2025):

compose

services:
  newt:
    image: fosrl/newt
    container_name: newt
    restart: unless-stopped
    environment:
      - PANGOLIN_ENDPOINT=<site-name>
      - NEWT_ID=<id>
      - NEWT_SECRET=<secret>

nmap

Is this what you meant?

nmap -T5 -A -v localhost
Starting Nmap 7.94SVN ( https://nmap.org ) at 2025-05-23 01:52 UTC
NSE: Loaded 156 scripts for scanning.
NSE: Script Pre-scanning.
Initiating NSE at 01:52
Completed NSE at 01:52, 0.00s elapsed
Initiating NSE at 01:52
Completed NSE at 01:52, 0.00s elapsed
Initiating NSE at 01:52
Completed NSE at 01:52, 0.00s elapsed
Initiating SYN Stealth Scan at 01:52
Scanning localhost (127.0.0.1) [1000 ports]
Discovered open port 443/tcp on 127.0.0.1
Discovered open port 22/tcp on 127.0.0.1
Discovered open port 80/tcp on 127.0.0.1
Completed SYN Stealth Scan at 01:52, 0.07s elapsed (1000 total ports)
Initiating Service scan at 01:52
Scanning 3 services on localhost (127.0.0.1)
Completed Service scan at 01:52, 12.05s elapsed (3 services on 1 host)
Initiating OS detection (try #1) against localhost (127.0.0.1)
NSE: Script scanning 127.0.0.1.
Initiating NSE at 01:52
Completed NSE at 01:52, 0.52s elapsed
Initiating NSE at 01:52
Completed NSE at 01:52, 0.12s elapsed
Initiating NSE at 01:52
Completed NSE at 01:52, 0.00s elapsed
Nmap scan report for localhost (127.0.0.1)
Host is up (0.000058s latency).
Not shown: 997 closed tcp ports (reset)
PORT    STATE SERVICE  VERSION
22/tcp  open  ssh      OpenSSH 9.6p1 Ubuntu 3ubuntu13.5 (Ubuntu Linux; protocol 2.0)
| ssh-hostkey:
|   256 <redacted> (ECDSA)
|_  256 <redacted> (ED25519)
80/tcp  open  http     Golang net/http server (Go-IPFS json-rpc or InfluxDB API)
|_http-title: Site doesn't have a title (text/plain; charset=utf-8).
443/tcp open  ssl/http Golang net/http server (Go-IPFS json-rpc or InfluxDB API)
| ssl-cert: Subject: commonName=TRAEFIK DEFAULT CERT
| Subject Alternative Name: DNS:46ec7f595e89e55ea8126b52332af011.357a0a61dbdeea0089b00537b8c80445.traefik.default
| Issuer: commonName=TRAEFIK DEFAULT CERT
| Public Key type: rsa
| Public Key bits: 2048
| Signature Algorithm: sha256WithRSAEncryption
| Not valid before: 2025-05-22T10:24:31
| Not valid after:  2026-05-22T10:24:31
| MD5:   f1e5:1a4a:a091:3f14:11c0:2836:3427:3894
|_SHA-1: bd54:e118:7aa6:101c:d047:747d:188e:ab9d:9e2a:2ec6
|_http-title: Site doesn't have a title (text/plain; charset=utf-8).
Device type: general purpose
Running: Linux 2.6.X
OS CPE: cpe:/o:linux:linux_kernel:2.6.32
OS details: Linux 2.6.32
Uptime guess: 9.900 days (since Tue May 13 04:16:18 2025)
Network Distance: 0 hops
TCP Sequence Prediction: Difficulty=255 (Good luck!)
IP ID Sequence Generation: All zeros
Service Info: OS: Linux; CPE: cpe:/o:linux:linux_kernel

NSE: Script Post-scanning.
Initiating NSE at 01:52
Completed NSE at 01:52, 0.00s elapsed
Initiating NSE at 01:52
Completed NSE at 01:52, 0.00s elapsed
Initiating NSE at 01:52
Completed NSE at 01:52, 0.00s elapsed
Read data files from: /usr/bin/../share/nmap
OS and Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 14.24 seconds
           Raw packets sent: 1022 (45.778KB) | Rcvd: 2045 (87.112KB)
<!-- gh-comment-id:2903035674 --> @flowy0 commented on GitHub (May 23, 2025): compose ``` services: newt: image: fosrl/newt container_name: newt restart: unless-stopped environment: - PANGOLIN_ENDPOINT=<site-name> - NEWT_ID=<id> - NEWT_SECRET=<secret> ```` nmap Is this what you meant? ``` nmap -T5 -A -v localhost Starting Nmap 7.94SVN ( https://nmap.org ) at 2025-05-23 01:52 UTC NSE: Loaded 156 scripts for scanning. NSE: Script Pre-scanning. Initiating NSE at 01:52 Completed NSE at 01:52, 0.00s elapsed Initiating NSE at 01:52 Completed NSE at 01:52, 0.00s elapsed Initiating NSE at 01:52 Completed NSE at 01:52, 0.00s elapsed Initiating SYN Stealth Scan at 01:52 Scanning localhost (127.0.0.1) [1000 ports] Discovered open port 443/tcp on 127.0.0.1 Discovered open port 22/tcp on 127.0.0.1 Discovered open port 80/tcp on 127.0.0.1 Completed SYN Stealth Scan at 01:52, 0.07s elapsed (1000 total ports) Initiating Service scan at 01:52 Scanning 3 services on localhost (127.0.0.1) Completed Service scan at 01:52, 12.05s elapsed (3 services on 1 host) Initiating OS detection (try #1) against localhost (127.0.0.1) NSE: Script scanning 127.0.0.1. Initiating NSE at 01:52 Completed NSE at 01:52, 0.52s elapsed Initiating NSE at 01:52 Completed NSE at 01:52, 0.12s elapsed Initiating NSE at 01:52 Completed NSE at 01:52, 0.00s elapsed Nmap scan report for localhost (127.0.0.1) Host is up (0.000058s latency). Not shown: 997 closed tcp ports (reset) PORT STATE SERVICE VERSION 22/tcp open ssh OpenSSH 9.6p1 Ubuntu 3ubuntu13.5 (Ubuntu Linux; protocol 2.0) | ssh-hostkey: | 256 <redacted> (ECDSA) |_ 256 <redacted> (ED25519) 80/tcp open http Golang net/http server (Go-IPFS json-rpc or InfluxDB API) |_http-title: Site doesn't have a title (text/plain; charset=utf-8). 443/tcp open ssl/http Golang net/http server (Go-IPFS json-rpc or InfluxDB API) | ssl-cert: Subject: commonName=TRAEFIK DEFAULT CERT | Subject Alternative Name: DNS:46ec7f595e89e55ea8126b52332af011.357a0a61dbdeea0089b00537b8c80445.traefik.default | Issuer: commonName=TRAEFIK DEFAULT CERT | Public Key type: rsa | Public Key bits: 2048 | Signature Algorithm: sha256WithRSAEncryption | Not valid before: 2025-05-22T10:24:31 | Not valid after: 2026-05-22T10:24:31 | MD5: f1e5:1a4a:a091:3f14:11c0:2836:3427:3894 |_SHA-1: bd54:e118:7aa6:101c:d047:747d:188e:ab9d:9e2a:2ec6 |_http-title: Site doesn't have a title (text/plain; charset=utf-8). Device type: general purpose Running: Linux 2.6.X OS CPE: cpe:/o:linux:linux_kernel:2.6.32 OS details: Linux 2.6.32 Uptime guess: 9.900 days (since Tue May 13 04:16:18 2025) Network Distance: 0 hops TCP Sequence Prediction: Difficulty=255 (Good luck!) IP ID Sequence Generation: All zeros Service Info: OS: Linux; CPE: cpe:/o:linux:linux_kernel NSE: Script Post-scanning. Initiating NSE at 01:52 Completed NSE at 01:52, 0.00s elapsed Initiating NSE at 01:52 Completed NSE at 01:52, 0.00s elapsed Initiating NSE at 01:52 Completed NSE at 01:52, 0.00s elapsed Read data files from: /usr/bin/../share/nmap OS and Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 14.24 seconds Raw packets sent: 1022 (45.778KB) | Rcvd: 2045 (87.112KB) ```
GiteaMirror commented 2026-04-16 08:20:16 -05:00
Author
Owner
Copy Link

@flowy0 commented on GitHub (May 23, 2025):

Sorry, i fixed this by restarting and editing my cloudflare api permissions, not sure if it was the issue though

<!-- gh-comment-id:2903069085 --> @flowy0 commented on GitHub (May 23, 2025): Sorry, i fixed this by restarting and editing my cloudflare api permissions, not sure if it was the issue though
GiteaMirror commented 2026-04-16 08:20:17 -05:00
Author
Owner
Copy Link

@RichyHBM commented on GitHub (May 23, 2025):

I seem to be hitting the same issue, from what I can tell this seems to have appeared after moving my pangolin setup from one vps to a new one, as far as I can tell I correctly updated all the IPs and DNS entries

<!-- gh-comment-id:2904606708 --> @RichyHBM commented on GitHub (May 23, 2025): I seem to be hitting the same issue, from what I can tell this seems to have appeared after moving my pangolin setup from one vps to a new one, as far as I can tell I correctly updated all the IPs and DNS entries
GiteaMirror commented 2026-04-16 08:20:17 -05:00
Author
Owner
Copy Link

@RichyHBM commented on GitHub (May 23, 2025):

@flowy0 Don't know if you could reopen the issue?

<!-- gh-comment-id:2904607925 --> @RichyHBM commented on GitHub (May 23, 2025): @flowy0 Don't know if you could reopen the issue?
GiteaMirror commented 2026-04-16 08:20:19 -05:00
Author
Owner
Copy Link

@flowy0 commented on GitHub (May 27, 2025):

reopened

<!-- gh-comment-id:2911012046 --> @flowy0 commented on GitHub (May 27, 2025): reopened
GiteaMirror commented 2026-04-16 08:20:21 -05:00
Author
Owner
Copy Link

@RichyHBM commented on GitHub (May 27, 2025):

Really sorry, this seems to be issue #776, so this one can be closed again

<!-- gh-comment-id:2913146287 --> @RichyHBM commented on GitHub (May 27, 2025): Really sorry, this seems to be issue #776, so this one can be closed again
GiteaMirror commented 2026-04-16 08:20:22 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 11, 2025):

This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.

<!-- gh-comment-id:2960879866 --> @github-actions[bot] commented on GitHub (Jun 11, 2025): This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
GiteaMirror commented 2026-04-16 08:20:23 -05:00
Author
Owner
Copy Link

@Craig-G-NZ commented on GitHub (Jun 14, 2025):

Hi there, I'm new to Pangolin, i setup a vps with cloudserver, setup firewall to allow 80, 443,and 51820, but also having this ping issue.

INFO: 2025/06/14 09:29:13 Newt version 1.2.1
INFO: 2025/06/14 09:29:14 Sent registration message
INFO: 2025/06/14 09:29:14 Received registration message
INFO: 2025/06/14 09:29:14 Received: {Type:newt/wg/connect Data:map[endpoint:pangolin.mydomain.com:51820 publicKey:public_key_here= serverIP:100.89.128.1 targets:map[tcp:[] udp:[]] tunnelIP:100.89.128.4]}
INFO: 2025/06/14 09:29:14 WireGuard device created. Lets ping the server now...
INFO: 2025/06/14 09:29:14 Ping attempt 1
INFO: 2025/06/14 09:29:14 Pinging 100.89.128.1
WARN: 2025/06/14 09:29:24 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/06/14 09:29:24 Starting ping check
INFO: 2025/06/14 09:29:24 Ping attempt 2
INFO: 2025/06/14 09:29:24 Pinging 100.89.128.1
WARN: 2025/06/14 09:29:34 Ping attempt 2 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/06/14 09:29:36 Ping attempt 3
INFO: 2025/06/14 09:29:36 Pinging 100.89.128.1
WARN: 2025/06/14 09:29:46 Ping attempt 3 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/06/14 09:29:48 Ping attempt 4
INFO: 2025/06/14 09:29:48 Pinging 100.89.128.1
INFO: 2025/06/14 09:29:54 Pinging 100.89.128.1
WARN: 2025/06/14 09:29:58 Ping attempt 4 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/06/14 09:30:00 Ping attempt 5
INFO: 2025/06/14 09:30:00 Pinging 100.89.128.1
WARN: 2025/06/14 09:30:04 Connection to server lost. Continuous reconnection attempts will be made.
WARN: 2025/06/14 09:30:04 Please check your internet connection and ensure the Pangolin server is online.
WARN: 2025/06/14 09:30:04 Newt will continue reconnection attempts automatically when connectivity is restored.
WARN: 2025/06/14 09:30:10 Ping attempt 5 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/06/14 09:30:10 Increasing ping retry delay to 3s
INFO: 2025/06/14 09:30:13 Ping attempt 6
INFO: 2025/06/14 09:30:13 Pinging 100.89.128.1
WARN: 2025/06/14 09:30:23 Ping attempt 6 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/06/14 09:30:24 Pinging 100.89.128.1
INFO: 2025/06/14 09:30:26 Ping attempt 7
INFO: 2025/06/14 09:30:26 Pinging 100.89.128.1

gerbil says i have a connection

INFO: 2025/06/14 09:14:29 Fetching remote config from http://pangolin:3001/api/v1/gerbil/get-config
INFO: 2025/06/14 09:14:29 Created WireGuard interface wg0
INFO: 2025/06/14 09:14:29 Assigned IP address 100.89.128.1/24 to interface wg0
INFO: 2025/06/14 09:14:29 Attempting to delete existing MSS clamping rule for chain INPUT
INFO: 2025/06/14 09:14:29 Attempting to delete existing MSS clamping rule for chain OUTPUT
INFO: 2025/06/14 09:14:29 Attempting to delete existing MSS clamping rule for chain FORWARD
INFO: 2025/06/14 09:14:29 Adding MSS clamping rule for chain INPUT
INFO: 2025/06/14 09:14:29 Successfully added and verified MSS clamping rule for chain INPUT
INFO: 2025/06/14 09:14:29 Adding MSS clamping rule for chain OUTPUT
INFO: 2025/06/14 09:14:29 Successfully added and verified MSS clamping rule for chain OUTPUT
INFO: 2025/06/14 09:14:29 Adding MSS clamping rule for chain FORWARD
INFO: 2025/06/14 09:14:29 Successfully added and verified MSS clamping rule for chain FORWARD
INFO: 2025/06/14 09:14:29 WireGuard interface wg0 created and configured
INFO: 2025/06/14 09:14:29 Peer redacted= added successfully
INFO: 2025/06/14 09:14:29 Starting server on :3003
INFO: 2025/06/14 09:14:39 Peer redacted= added successfully
INFO: 2025/06/14 09:15:41 Peer redacted= removed successfully
INFO: 2025/06/14 09:15:41 Peer redacted= added successfully
INFO: 2025/06/14 09:18:08 Peer redacted= removed successfully
INFO: 2025/06/14 09:18:08 Peer redacted= added successfully
INFO: 2025/06/14 09:29:14 Peer redacted= removed successfully
INFO: 2025/06/14 09:29:14 Peer redacted= added successfully

heres the commands im running for the firewall enable

sudo ufw --force reset
sudo ufw default allow outgoing
sudo ufw allow from ip_ip_address_here to any port 22
sudo ufw allow 80/tcp
sudo ufw allow 443/tcp
sudo ufw allow 51820/udp
sudo ufw enable
sudo ufw status verbose

<!-- gh-comment-id:2972554682 --> @Craig-G-NZ commented on GitHub (Jun 14, 2025): Hi there, I'm new to Pangolin, i setup a vps with cloudserver, setup firewall to allow 80, 443,and 51820, but also having this ping issue. INFO: 2025/06/14 09:29:13 Newt version 1.2.1 INFO: 2025/06/14 09:29:14 Sent registration message INFO: 2025/06/14 09:29:14 Received registration message INFO: 2025/06/14 09:29:14 Received: {Type:newt/wg/connect Data:map[endpoint:pangolin.mydomain.com:51820 publicKey:public_key_here= serverIP:100.89.128.1 targets:map[tcp:[] udp:[]] tunnelIP:100.89.128.4]} INFO: 2025/06/14 09:29:14 WireGuard device created. Lets ping the server now... INFO: 2025/06/14 09:29:14 Ping attempt 1 INFO: 2025/06/14 09:29:14 Pinging 100.89.128.1 WARN: 2025/06/14 09:29:24 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout INFO: 2025/06/14 09:29:24 Starting ping check INFO: 2025/06/14 09:29:24 Ping attempt 2 INFO: 2025/06/14 09:29:24 Pinging 100.89.128.1 WARN: 2025/06/14 09:29:34 Ping attempt 2 failed: failed to read ICMP packet: i/o timeout INFO: 2025/06/14 09:29:36 Ping attempt 3 INFO: 2025/06/14 09:29:36 Pinging 100.89.128.1 WARN: 2025/06/14 09:29:46 Ping attempt 3 failed: failed to read ICMP packet: i/o timeout INFO: 2025/06/14 09:29:48 Ping attempt 4 INFO: 2025/06/14 09:29:48 Pinging 100.89.128.1 INFO: 2025/06/14 09:29:54 Pinging 100.89.128.1 WARN: 2025/06/14 09:29:58 Ping attempt 4 failed: failed to read ICMP packet: i/o timeout INFO: 2025/06/14 09:30:00 Ping attempt 5 INFO: 2025/06/14 09:30:00 Pinging 100.89.128.1 WARN: 2025/06/14 09:30:04 Connection to server lost. Continuous reconnection attempts will be made. WARN: 2025/06/14 09:30:04 Please check your internet connection and ensure the Pangolin server is online. WARN: 2025/06/14 09:30:04 Newt will continue reconnection attempts automatically when connectivity is restored. WARN: 2025/06/14 09:30:10 Ping attempt 5 failed: failed to read ICMP packet: i/o timeout INFO: 2025/06/14 09:30:10 Increasing ping retry delay to 3s INFO: 2025/06/14 09:30:13 Ping attempt 6 INFO: 2025/06/14 09:30:13 Pinging 100.89.128.1 WARN: 2025/06/14 09:30:23 Ping attempt 6 failed: failed to read ICMP packet: i/o timeout INFO: 2025/06/14 09:30:24 Pinging 100.89.128.1 INFO: 2025/06/14 09:30:26 Ping attempt 7 INFO: 2025/06/14 09:30:26 Pinging 100.89.128.1 gerbil says i have a connection INFO: 2025/06/14 09:14:29 Fetching remote config from http://pangolin:3001/api/v1/gerbil/get-config INFO: 2025/06/14 09:14:29 Created WireGuard interface wg0 INFO: 2025/06/14 09:14:29 Assigned IP address 100.89.128.1/24 to interface wg0 INFO: 2025/06/14 09:14:29 Attempting to delete existing MSS clamping rule for chain INPUT INFO: 2025/06/14 09:14:29 Attempting to delete existing MSS clamping rule for chain OUTPUT INFO: 2025/06/14 09:14:29 Attempting to delete existing MSS clamping rule for chain FORWARD INFO: 2025/06/14 09:14:29 Adding MSS clamping rule for chain INPUT INFO: 2025/06/14 09:14:29 Successfully added and verified MSS clamping rule for chain INPUT INFO: 2025/06/14 09:14:29 Adding MSS clamping rule for chain OUTPUT INFO: 2025/06/14 09:14:29 Successfully added and verified MSS clamping rule for chain OUTPUT INFO: 2025/06/14 09:14:29 Adding MSS clamping rule for chain FORWARD INFO: 2025/06/14 09:14:29 Successfully added and verified MSS clamping rule for chain FORWARD INFO: 2025/06/14 09:14:29 WireGuard interface wg0 created and configured INFO: 2025/06/14 09:14:29 Peer redacted= added successfully INFO: 2025/06/14 09:14:29 Starting server on :3003 INFO: 2025/06/14 09:14:39 Peer redacted= added successfully INFO: 2025/06/14 09:15:41 Peer redacted= removed successfully INFO: 2025/06/14 09:15:41 Peer redacted= added successfully INFO: 2025/06/14 09:18:08 Peer redacted= removed successfully INFO: 2025/06/14 09:18:08 Peer redacted= added successfully INFO: 2025/06/14 09:29:14 Peer redacted= removed successfully INFO: 2025/06/14 09:29:14 Peer redacted= added successfully heres the commands im running for the firewall enable sudo ufw --force reset sudo ufw default allow outgoing sudo ufw allow from ip_ip_address_here to any port 22 sudo ufw allow 80/tcp sudo ufw allow 443/tcp sudo ufw allow 51820/udp sudo ufw enable sudo ufw status verbose
GiteaMirror commented 2026-04-16 08:20:24 -05:00
Author
Owner
Copy Link

@Craig-G-NZ commented on GitHub (Jun 14, 2025):

Hi there, I'm new to Pangolin, i setup a vps with cloudserver, setup firewall to allow 80, 443,and 51820, but also having this ping issue.

I've just noticed that if I turn off the Cloudflare proxy to the Pangolin DNS entry the ping works ok, is this required or have I missed a step?

INFO: 2025/06/14 09:40:11 WireGuard device created. Lets ping the server now...
INFO: 2025/06/14 09:40:11 Ping attempt 1
INFO: 2025/06/14 09:40:11 Pinging 100.89.128.1
INFO: 2025/06/14 09:40:11 Ping latency: 299.905971ms
INFO: 2025/06/14 09:40:11 Starting ping check
INFO: 2025/06/14 09:40:41 Pinging 100.89.128.1
INFO: 2025/06/14 09:40:41 Ping latency: 147.0694ms
INFO: 2025/06/14 09:41:11 Pinging 100.89.128.1
INFO: 2025/06/14 09:41:11 Ping latency: 147.198775ms
INFO: 2025/06/14 09:41:41 Pinging 100.89.128.1
INFO: 2025/06/14 09:41:41 Ping latency: 147.035224ms
INFO: 2025/06/14 09:42:11 Pinging 100.89.128.1
INFO: 2025/06/14 09:42:11 Ping latency: 149.45041ms
INFO: 2025/06/14 09:42:41 Pinging 100.89.128.1
INFO: 2025/06/14 09:42:41 Ping latency: 147.757209ms

<!-- gh-comment-id:2972558801 --> @Craig-G-NZ commented on GitHub (Jun 14, 2025): > Hi there, I'm new to Pangolin, i setup a vps with cloudserver, setup firewall to allow 80, 443,and 51820, but also having this ping issue. I've just noticed that if I turn off the Cloudflare proxy to the Pangolin DNS entry the ping works ok, is this required or have I missed a step? INFO: 2025/06/14 09:40:11 WireGuard device created. Lets ping the server now... INFO: 2025/06/14 09:40:11 Ping attempt 1 INFO: 2025/06/14 09:40:11 Pinging 100.89.128.1 INFO: 2025/06/14 09:40:11 Ping latency: 299.905971ms INFO: 2025/06/14 09:40:11 Starting ping check INFO: 2025/06/14 09:40:41 Pinging 100.89.128.1 INFO: 2025/06/14 09:40:41 Ping latency: 147.0694ms INFO: 2025/06/14 09:41:11 Pinging 100.89.128.1 INFO: 2025/06/14 09:41:11 Ping latency: 147.198775ms INFO: 2025/06/14 09:41:41 Pinging 100.89.128.1 INFO: 2025/06/14 09:41:41 Ping latency: 147.035224ms INFO: 2025/06/14 09:42:11 Pinging 100.89.128.1 INFO: 2025/06/14 09:42:11 Ping latency: 149.45041ms INFO: 2025/06/14 09:42:41 Pinging 100.89.128.1 INFO: 2025/06/14 09:42:41 Ping latency: 147.757209ms
GiteaMirror commented 2026-04-16 08:20:24 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Jun 16, 2025):

@Craig-G-NZ yes you need to have CF proxy off because it obscures the IP of the VPS and WG traffic cant get through. If you need to use CF proxy you can set the base_endpoint section of the gerbil config file to have the IP of the VPS and it should work for you.

<!-- gh-comment-id:2976685409 --> @oschwartz10612 commented on GitHub (Jun 16, 2025): @Craig-G-NZ yes you need to have CF proxy off because it obscures the IP of the VPS and WG traffic cant get through. If you need to use CF proxy you can set the base_endpoint section of the gerbil config file to have the IP of the VPS and it should work for you.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#1617
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?