failed to read ICMP packet: i/o timeout #42

New Issue

Closed

opened 2025-11-19 07:12:42 -06:00 by GiteaMirror · 1 comment

GiteaMirror commented 2025-11-19 07:12:42 -06:00

Owner

Copy Link

Copy Source

Originally created by @codewhizz on GitHub (Jul 19, 2025).

My Raspberry Pi today got disconnected from newt to my pangolin. Then, I researched and found out that newt latest version could be causing issues so, after that I updated my pangolin to latest and while using newt latest still getting the problem.

My other server with old newt I installed a month ago is working fine though, before and after update. But this newt was installed recently this week

On Pangolin dashboard, it shows 1.3.4 as version. But never connects

Here are newt logs.

INFO: 2025/07/18 23:02:00 Newt version 1.3.4
INFO: 2025/07/18 23:02:01 Websocket connected
INFO: 2025/07/18 23:02:01 Requesting exit nodes from server
INFO: 2025/07/18 23:02:01 Received ping message
INFO: 2025/07/18 23:02:01 Received registration message
INFO: 2025/07/18 23:02:01 Connecting to endpoint: MY_SERVER_IP_ADDRESS
WARN: 2025/07/18 23:02:32 Initial reliable ping failed, but continuing: all 5 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
WARN: 2025/07/18 23:02:37 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/18 23:02:42 Ping attempt 2 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/18 23:02:49 Ping attempt 3 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/18 23:02:56 Ping attempt 4 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/18 23:03:03 Ping attempt 5 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/07/18 23:03:03 Increasing ping retry delay to 3s
WARN: 2025/07/18 23:03:11 Ping attempt 6 failed: failed to read ICMP packet: i/o timeout
...

after some time

WARN: 2025/07/18 23:46:29 Initial reliable ping failed, but continuing: all 5 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
WARN: 2025/07/18 23:46:34 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/07/18 23:46:34 Received registration message
INFO: 2025/07/18 23:46:34 Stopping ping check
WARN: 2025/07/18 23:46:34 Ping attempt 2 failed: failed to read ICMP packet: ping read: endpoint is closed for receive
INFO: 2025/07/18 23:46:34 Connecting to endpoint: MY_SERVER_IP_ADDRESS
WARN: 2025/07/18 23:47:05 Initial reliable ping failed, but continuing: all 5 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
WARN: 2025/07/18 23:47:10 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout
INFO: 2025/07/18 23:47:10 Received registration message
INFO: 2025/07/18 23:47:10 Stopping ping check
WARN: 2025/07/18 23:47:10 Ping attempt 2 failed: failed to read ICMP packet: ping read: endpoint is closed for receive
INFO: 2025/07/18 23:47:10 Connecting to endpoint: MY_SERVER_IP_ADDRESS
ERROR: 2025/07/18 23:47:27 Ping failed: write tcp 172.19.0.3:41524->172.67.142.152:443: write: broken pipe
WARN: 2025/07/18 23:47:41 Initial reliable ping failed, but continuing: all 5 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
WARN: 2025/07/18 23:47:46 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0xc0 pc=0x370eec]

goroutine 51 [running]:
github.com/gorilla/websocket.(*Conn).NextReader(0x0)
        /go/pkg/mod/github.com/gorilla/websocket@v1.5.3/conn.go:1000 +0x1c
github.com/gorilla/websocket.(*Conn).ReadJSON(0x400045ed10?, {0x562ba0, 0x40000444a0})
        /go/pkg/mod/github.com/gorilla/websocket@v1.5.3/json.go:50 +0x24
github.com/fosrl/newt/websocket.(*Client).readPumpWithDisconnectDetection(0x4000186320)
        /app/websocket/client.go:406 +0x8c
created by github.com/fosrl/newt/websocket.(*Client).establishConnection in goroutine 10
        /app/websocket/client.go:337 +0x4b0
INFO: 2025/07/18 23:47:47 Newt version 1.3.4
ERROR: 2025/07/18 23:47:48 Failed to get token with status code: 521
ERROR: 2025/07/18 23:47:48 Failed to connect: failed to get token: failed to get token with status code: 521. Retrying in 3s...
ERROR: 2025/07/18 23:47:51 Failed to get token with status code: 521
ERROR: 2025/07/18 23:47:51 Failed to connect: failed to get token: failed to get token with status code: 521. Retrying in 3s...
ERROR: 2025/07/18 23:47:54 Failed to get token with status code: 521
ERROR: 2025/07/18 23:47:54 Failed to connect: failed to get token: failed to get token with status code: 521. Retrying in 3s...
ERROR: 2025/07/18 23:47:57 Failed to get token with status code: 521
ERROR: 2025/07/18 23:47:57 Failed to connect: failed to get token: failed to get token with status code: 521. Retrying in 3s...
ERROR: 2025/07/18 23:48:00 Failed to get token with status code: 521
ERROR: 2025/07/18 23:48:00 Failed to connect: failed to get token: failed to get token with status code: 521. Retrying in 3s...
ERROR: 2025/07/18 23:48:22 Failed to get token with status code: 522
ERROR: 2025/07/18 23:48:22 Failed to connect: failed to get token: failed to get token with status code: 522. Retrying in 3s...
ERROR: 2025/07/18 23:48:25 Failed to get token with status code: 521
ERROR: 2025/07/18 23:48:25 Failed to connect: failed to get token: failed to get token with status code: 521. Retrying in 3s...
ERROR: 2025/07/18 23:48:28 Failed to get token with status code: 521
ERROR: 2025/07/18 23:48:28 Failed to connect: failed to get token: failed to get token with status code: 521. Retrying in 3s...
ERROR: 2025/07/18 23:48:31 Failed to get token with status code: 521
ERROR: 2025/07/18 23:48:31 Failed to connect: failed to get token: failed to get token with status code: 521. Retrying in 3s...
ERROR: 2025/07/18 23:48:36 Failed to get token with status code: 525
ERROR: 2025/07/18 23:48:36 Failed to connect: failed to get token: failed to get token with status code: 525. Retrying in 3s...
ERROR: 2025/07/18 23:48:39 Failed to get token with status code: 403
ERROR: 2025/07/18 23:48:39 Failed to connect: failed to get token: failed to get token with status code: 403. Retrying in 3s...
ERROR: 2025/07/18 23:48:42 Failed to get token with status code: 403
ERROR: 2025/07/18 23:48:42 Failed to connect: failed to get token: failed to get token with status code: 403. Retrying in 3s...
ERROR: 2025/07/18 23:48:45 Failed to get token with status code: 403
ERROR: 2025/07/18 23:48:45 Failed to connect: failed to get token: failed to get token with status code: 403. Retrying in 3s...
ERROR: 2025/07/18 23:48:48 Failed to get token with status code: 403
ERROR: 2025/07/18 23:48:48 Failed to connect: failed to get token: failed to get token with status code: 403. Retrying in 3s...
ERROR: 2025/07/18 23:48:51 Failed to get token with status code: 403
ERROR: 2025/07/18 23:48:51 Failed to connect: failed to get token: failed to get token with status code: 403. Retrying in 3s...
ERROR: 2025/07/18 23:48:54 Failed to get token with status code: 403
ERROR: 2025/07/18 23:48:54 Failed to connect: failed to get token: failed to get token with status code: 403. Retrying in 3s...
ERROR: 2025/07/18 23:48:58 Failed to get token with status code: 403
ERROR: 2025/07/18 23:48:58 Failed to connect: failed to get token: failed to get token with status code: 403. Retrying in 3s...
ERROR: 2025/07/18 23:49:01 Failed to get token with status code: 403
ERROR: 2025/07/18 23:49:01 Failed to connect: failed to get token: failed to get token with status code: 403. Retrying in 3s...
ERROR: 2025/07/18 23:49:04 Failed to get token with status code: 403
ERROR: 2025/07/18 23:49:04 Failed to connect: failed to get token: failed to get token with status code: 403. Retrying in 3s...
INFO: 2025/07/18 23:49:11 Websocket connected
INFO: 2025/07/18 23:49:11 Requesting exit nodes from server
INFO: 2025/07/18 23:49:11 Received ping message
INFO: 2025/07/18 23:49:12 Received registration message
INFO: 2025/07/18 23:49:12 Connecting to endpoint: MY_SERVER_IP_ADDRESS
WARN: 2025/07/18 23:49:42 Initial reliable ping failed, but continuing: all 5 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
WARN: 2025/07/18 23:49:47 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/18 23:49:52 Ping attempt 2 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/18 23:49:59 Ping attempt 3 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/18 23:50:06 Ping attempt 4 failed: failed to read ICMP packet: i/o timeout
WARN: 2025/07/18 23:50:13 Ping attempt 5 failed: failed to read ICMP packet: i/o timeout
...

Extra Information (Don't know if its relevant) -
First of all I'm not sure why these errors started, because it could be because of my firewall of OpenWRT which I installed recently, because I'm new to that. My Broadband IP Address also changed recently due to dynamic ip and its possible that in past I would've set some settings that blocks access from my server to my IP due to change, could be cloudflare proxy, could be my cloud vps firewall rules. I will be checking later this afternoon.

Originally created by @codewhizz on GitHub (Jul 19, 2025). My Raspberry Pi today got disconnected from newt to my pangolin. Then, I researched and found out that newt latest version could be causing issues so, after that I updated my pangolin to latest and while using newt latest still getting the problem. My other server with old newt I installed a month ago is working fine though, before and after update. But this newt was installed recently this week On Pangolin dashboard, it shows 1.3.4 as version. But never connects Here are newt logs. ``` INFO: 2025/07/18 23:02:00 Newt version 1.3.4 INFO: 2025/07/18 23:02:01 Websocket connected INFO: 2025/07/18 23:02:01 Requesting exit nodes from server INFO: 2025/07/18 23:02:01 Received ping message INFO: 2025/07/18 23:02:01 Received registration message INFO: 2025/07/18 23:02:01 Connecting to endpoint: MY_SERVER_IP_ADDRESS WARN: 2025/07/18 23:02:32 Initial reliable ping failed, but continuing: all 5 ping attempts failed, last error: failed to read ICMP packet: i/o timeout WARN: 2025/07/18 23:02:37 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/18 23:02:42 Ping attempt 2 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/18 23:02:49 Ping attempt 3 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/18 23:02:56 Ping attempt 4 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/18 23:03:03 Ping attempt 5 failed: failed to read ICMP packet: i/o timeout INFO: 2025/07/18 23:03:03 Increasing ping retry delay to 3s WARN: 2025/07/18 23:03:11 Ping attempt 6 failed: failed to read ICMP packet: i/o timeout ... ``` after some time ``` WARN: 2025/07/18 23:46:29 Initial reliable ping failed, but continuing: all 5 ping attempts failed, last error: failed to read ICMP packet: i/o timeout WARN: 2025/07/18 23:46:34 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout INFO: 2025/07/18 23:46:34 Received registration message INFO: 2025/07/18 23:46:34 Stopping ping check WARN: 2025/07/18 23:46:34 Ping attempt 2 failed: failed to read ICMP packet: ping read: endpoint is closed for receive INFO: 2025/07/18 23:46:34 Connecting to endpoint: MY_SERVER_IP_ADDRESS WARN: 2025/07/18 23:47:05 Initial reliable ping failed, but continuing: all 5 ping attempts failed, last error: failed to read ICMP packet: i/o timeout WARN: 2025/07/18 23:47:10 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout INFO: 2025/07/18 23:47:10 Received registration message INFO: 2025/07/18 23:47:10 Stopping ping check WARN: 2025/07/18 23:47:10 Ping attempt 2 failed: failed to read ICMP packet: ping read: endpoint is closed for receive INFO: 2025/07/18 23:47:10 Connecting to endpoint: MY_SERVER_IP_ADDRESS ERROR: 2025/07/18 23:47:27 Ping failed: write tcp 172.19.0.3:41524->172.67.142.152:443: write: broken pipe WARN: 2025/07/18 23:47:41 Initial reliable ping failed, but continuing: all 5 ping attempts failed, last error: failed to read ICMP packet: i/o timeout WARN: 2025/07/18 23:47:46 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0xc0 pc=0x370eec] goroutine 51 [running]: github.com/gorilla/websocket.(*Conn).NextReader(0x0) /go/pkg/mod/github.com/gorilla/websocket@v1.5.3/conn.go:1000 +0x1c github.com/gorilla/websocket.(*Conn).ReadJSON(0x400045ed10?, {0x562ba0, 0x40000444a0}) /go/pkg/mod/github.com/gorilla/websocket@v1.5.3/json.go:50 +0x24 github.com/fosrl/newt/websocket.(*Client).readPumpWithDisconnectDetection(0x4000186320) /app/websocket/client.go:406 +0x8c created by github.com/fosrl/newt/websocket.(*Client).establishConnection in goroutine 10 /app/websocket/client.go:337 +0x4b0 INFO: 2025/07/18 23:47:47 Newt version 1.3.4 ERROR: 2025/07/18 23:47:48 Failed to get token with status code: 521 ERROR: 2025/07/18 23:47:48 Failed to connect: failed to get token: failed to get token with status code: 521. Retrying in 3s... ERROR: 2025/07/18 23:47:51 Failed to get token with status code: 521 ERROR: 2025/07/18 23:47:51 Failed to connect: failed to get token: failed to get token with status code: 521. Retrying in 3s... ERROR: 2025/07/18 23:47:54 Failed to get token with status code: 521 ERROR: 2025/07/18 23:47:54 Failed to connect: failed to get token: failed to get token with status code: 521. Retrying in 3s... ERROR: 2025/07/18 23:47:57 Failed to get token with status code: 521 ERROR: 2025/07/18 23:47:57 Failed to connect: failed to get token: failed to get token with status code: 521. Retrying in 3s... ERROR: 2025/07/18 23:48:00 Failed to get token with status code: 521 ERROR: 2025/07/18 23:48:00 Failed to connect: failed to get token: failed to get token with status code: 521. Retrying in 3s... ERROR: 2025/07/18 23:48:22 Failed to get token with status code: 522 ERROR: 2025/07/18 23:48:22 Failed to connect: failed to get token: failed to get token with status code: 522. Retrying in 3s... ERROR: 2025/07/18 23:48:25 Failed to get token with status code: 521 ERROR: 2025/07/18 23:48:25 Failed to connect: failed to get token: failed to get token with status code: 521. Retrying in 3s... ERROR: 2025/07/18 23:48:28 Failed to get token with status code: 521 ERROR: 2025/07/18 23:48:28 Failed to connect: failed to get token: failed to get token with status code: 521. Retrying in 3s... ERROR: 2025/07/18 23:48:31 Failed to get token with status code: 521 ERROR: 2025/07/18 23:48:31 Failed to connect: failed to get token: failed to get token with status code: 521. Retrying in 3s... ERROR: 2025/07/18 23:48:36 Failed to get token with status code: 525 ERROR: 2025/07/18 23:48:36 Failed to connect: failed to get token: failed to get token with status code: 525. Retrying in 3s... ERROR: 2025/07/18 23:48:39 Failed to get token with status code: 403 ERROR: 2025/07/18 23:48:39 Failed to connect: failed to get token: failed to get token with status code: 403. Retrying in 3s... ERROR: 2025/07/18 23:48:42 Failed to get token with status code: 403 ERROR: 2025/07/18 23:48:42 Failed to connect: failed to get token: failed to get token with status code: 403. Retrying in 3s... ERROR: 2025/07/18 23:48:45 Failed to get token with status code: 403 ERROR: 2025/07/18 23:48:45 Failed to connect: failed to get token: failed to get token with status code: 403. Retrying in 3s... ERROR: 2025/07/18 23:48:48 Failed to get token with status code: 403 ERROR: 2025/07/18 23:48:48 Failed to connect: failed to get token: failed to get token with status code: 403. Retrying in 3s... ERROR: 2025/07/18 23:48:51 Failed to get token with status code: 403 ERROR: 2025/07/18 23:48:51 Failed to connect: failed to get token: failed to get token with status code: 403. Retrying in 3s... ERROR: 2025/07/18 23:48:54 Failed to get token with status code: 403 ERROR: 2025/07/18 23:48:54 Failed to connect: failed to get token: failed to get token with status code: 403. Retrying in 3s... ERROR: 2025/07/18 23:48:58 Failed to get token with status code: 403 ERROR: 2025/07/18 23:48:58 Failed to connect: failed to get token: failed to get token with status code: 403. Retrying in 3s... ERROR: 2025/07/18 23:49:01 Failed to get token with status code: 403 ERROR: 2025/07/18 23:49:01 Failed to connect: failed to get token: failed to get token with status code: 403. Retrying in 3s... ERROR: 2025/07/18 23:49:04 Failed to get token with status code: 403 ERROR: 2025/07/18 23:49:04 Failed to connect: failed to get token: failed to get token with status code: 403. Retrying in 3s... INFO: 2025/07/18 23:49:11 Websocket connected INFO: 2025/07/18 23:49:11 Requesting exit nodes from server INFO: 2025/07/18 23:49:11 Received ping message INFO: 2025/07/18 23:49:12 Received registration message INFO: 2025/07/18 23:49:12 Connecting to endpoint: MY_SERVER_IP_ADDRESS WARN: 2025/07/18 23:49:42 Initial reliable ping failed, but continuing: all 5 ping attempts failed, last error: failed to read ICMP packet: i/o timeout WARN: 2025/07/18 23:49:47 Ping attempt 1 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/18 23:49:52 Ping attempt 2 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/18 23:49:59 Ping attempt 3 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/18 23:50:06 Ping attempt 4 failed: failed to read ICMP packet: i/o timeout WARN: 2025/07/18 23:50:13 Ping attempt 5 failed: failed to read ICMP packet: i/o timeout ... ``` Extra Information (Don't know if its relevant) - First of all I'm not sure why these errors started, because it could be because of my firewall of OpenWRT which I installed recently, because I'm new to that. My Broadband IP Address also changed recently due to dynamic ip and its possible that in past I would've set some settings that blocks access from my server to my IP due to change, could be cloudflare proxy, could be my cloud vps firewall rules. I will be checking later this afternoon.

GiteaMirror closed this issue 2025-11-19 07:12:42 -06:00

GiteaMirror commented 2025-11-19 07:12:43 -06:00

Author

Owner

Copy Link

Copy Source

@codewhizz commented on GitHub (Jul 19, 2025):

Oh my god, I'm so sorry! It was indeed my Cloud VPS Firewall Ingress Rule. I changed it to XXX.XXX.XXX.0/24

I found that on https://ipinfo.io/what-is-my-ip

Now, its connecting properly :)

@codewhizz commented on GitHub (Jul 19, 2025): Oh my god, I'm so sorry! It was indeed my Cloud VPS Firewall Ingress Rule. I changed it to XXX.XXX.XXX.0/24 <img width="1326" height="53" alt="Image" src="https://github.com/user-attachments/assets/70ac3fb3-13cf-4269-a817-4af2bdb3badd" /> I found that on https://ipinfo.io/what-is-my-ip <img width="1377" height="772" alt="Image" src="https://github.com/user-attachments/assets/74054832-fedc-4f10-a8cc-0d3215f26a1a" /> Now, its connecting properly :)

GiteaMirror referenced this issue 2026-04-12 06:35:13 -05:00

[GH-ISSUE #42] HTTP PROXY support #192

GiteaMirror referenced this issue 2026-04-16 03:27:12 -05:00

[GH-ISSUE #42] HTTP PROXY support #482

GiteaMirror referenced this issue 2026-04-19 14:15:59 -05:00

[GH-ISSUE #42] HTTP PROXY support #781

GiteaMirror referenced this issue 2026-04-22 00:54:08 -05:00

[GH-ISSUE #42] HTTP PROXY support #1080

GiteaMirror referenced this issue 2026-04-24 19:58:44 -05:00

[GH-ISSUE #42] HTTP PROXY support #1381

GiteaMirror referenced this issue 2026-04-27 22:18:29 -05:00

[GH-ISSUE #42] HTTP PROXY support #1686

GiteaMirror referenced this issue 2026-05-03 05:41:00 -05:00

[GH-ISSUE #42] HTTP PROXY support #1996

GiteaMirror referenced this issue 2026-05-08 16:26:18 -05:00

[GH-ISSUE #42] HTTP PROXY support #2314

GiteaMirror referenced this issue 2026-05-12 22:00:17 -05:00

[GH-ISSUE #42] HTTP PROXY support #2643

GiteaMirror referenced this issue 2026-05-15 06:40:37 -05:00

[GH-ISSUE #42] HTTP PROXY support #2977

GiteaMirror referenced this issue 2026-05-17 19:52:33 -05:00

[GH-ISSUE #42] HTTP PROXY support #3314

GiteaMirror referenced this issue 2026-05-20 16:10:28 -05:00

[GH-ISSUE #42] HTTP PROXY support #3655

GiteaMirror referenced this issue 2026-05-24 17:04:14 -05:00

[GH-ISSUE #42] HTTP PROXY support #3996

GiteaMirror referenced this issue 2026-06-02 02:16:47 -05:00

[GH-ISSUE #42] HTTP PROXY support #4528

GiteaMirror referenced this issue 2026-06-07 18:17:59 -05:00

[GH-ISSUE #42] HTTP PROXY support #5071

GiteaMirror referenced this issue 2026-06-08 18:32:51 -05:00

[GH-ISSUE #42] HTTP PROXY support #5426

GiteaMirror referenced this issue 2026-06-10 20:54:42 -05:00

[GH-ISSUE #42] HTTP PROXY support #5784

GiteaMirror referenced this issue 2026-06-18 18:40:04 -05:00

[GH-ISSUE #42] HTTP PROXY support #6753

GiteaMirror referenced this issue 2026-06-20 14:43:06 -05:00

[GH-ISSUE #42] HTTP PROXY support #7119

GiteaMirror referenced this issue 2026-06-21 23:41:09 -05:00

[GH-ISSUE #42] HTTP PROXY support #7486

GiteaMirror referenced this issue 2026-07-12 11:22:41 -05:00

[GH-ISSUE #42] HTTP PROXY support #7854

GiteaMirror referenced this issue 2026-07-13 14:36:44 -05:00

[GH-ISSUE #42] HTTP PROXY support #8240

GiteaMirror referenced this issue 2026-07-14 20:52:25 -05:00

[GH-ISSUE #42] HTTP PROXY support #8628

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

dependabot/go_modules/go-dependencies-fc6bc20c87

dev

dependabot/github_actions/github-actions-dependencies-13b4f17173

fix-471

1.20.0

v1.20.0

1.19.1

v1.19.1

1.19.0

v1.19.0

1.18.1

v1.18.1

1.18.0

v1.18.0

1.17.0

v1.17.0

1.16.0

v1.16.0

1.15.0

v1.15.0

1.14.0

v1.14.0

1.13.0

v1.13.0

1.13.0-rc.0

1.12.5

v1.12.5

1.12.4

v1.12.4

1.12.3

v1.12.3

1.12.2

v1.12.2

1.12.1

v1.12.1

1.12.0

v1.12.0

v1.12.0-rc.1

1.12.0-rc.0

1.11.0

v1.11.0

1.10.4

1.10.3

v1.10.3

1.10.2

v1.10.2

1.10.1

v1.10.1

1.10.0

v1.10.0

1.9.5

1.9.4

1.9.3

1.9.2

1.9.1

1.9.0

v1.9.0

1.8.1

v1.8.1

v1.8.0

1.8.0

1.8.0-rc.0

1.7.0

1.6.1

1.7.0-rc.0

1.6.0

v1.0.1

1.4.9

1.5.2

1.5.1

1.5.0

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.4

1.3.3

1.3.2

1.3.1

1.3.0

1.2.1

1.2.0

1.1.3

1.1.2

1.1.1

1.1.0

1.0.0

1.0.0-beta.5

1.0.0-beta.4

1.0.0-beta.3

1.0.0-beta.2

1.0.0-beta.1

Labels

Clear labels

bug

dependencies

docker

enhancement

go

good first issue

help wanted

Improvement

needs investigating

pull-request

Mirrored from GitHub Pull Request

stale

wontfix

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

GiteaMirror ninjasurge (Kaehlen Rog)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/newt#42