I tried installing newt on both Alpine and Debian 13, the install script will fail on both ... xxx@newt:~# curl -fsSL https://pangolin.net/get-newt.sh | bash [INFO] Installing latest version of newt... [INFO] Fetching latest version from GitHub... [ERROR] Failed to fetch latest version information
Installing newt manually will also fail to fetch information about the latest version.
Environment
Alpine latest and Debian 13
Newt Version: latest
To Reproduce
Try installing newt on a fresh OS.
Expected Behavior
To download newt-
Originally created by @legionGer on GitHub (Dec 10, 2025).
Original GitHub issue: https://github.com/fosrl/newt/issues/198
### Describe the Bug
Hey,
I tried installing newt on both Alpine and Debian 13, the install script will fail on both ... `xxx@newt:~# curl -fsSL https://pangolin.net/get-newt.sh | bash
[INFO] Installing latest version of newt...
[INFO] Fetching latest version from GitHub...
[ERROR] Failed to fetch latest version information`
curl -fsSL https://api.github.com/repos/fosrl/newt/releases/latest returns a 404.
Installing newt manually will also fail to fetch information about the latest version.
### Environment
- Alpine latest and Debian 13
- Newt Version: latest
### To Reproduce
Try installing newt on a fresh OS.
### Expected Behavior
To download newt-
<!-- gh-comment-id:3638832068 -->
@Tilvisun commented on GitHub (Dec 10, 2025):
I suspect the new RC version as the reason.
As workaround, you could download the installer script and hardcode the latest normal version:
replace this:
https://github.com/fosrl/newt/blob/1271e8235e91c2d28b024339ad4092a60a092886/get-newt.sh#L33-L60
with:
`echo "1.6.0"`
@Malith-Rukshan commented on GitHub (Dec 11, 2025):
Since this repository removed the latest version (Release ID) from GitHub, the default installation script no longer works. The script relies on the https://api.github.com/repos/fosrl/newt/releases/latest endpoint to fetch the latest version, which now returns a 404 error.
Workaround:
You can directly specify the version number you want by replacing the get_latest_version() function with:
<!-- gh-comment-id:3639751106 -->
@Malith-Rukshan commented on GitHub (Dec 11, 2025):
Since this repository removed the latest version (Release ID) from GitHub, the default installation script no longer works. The script relies on the `https://api.github.com/repos/fosrl/newt/releases/latest` endpoint to fetch the latest version, which now returns a 404 error.
<img width="404" height="206" alt="Image" src="https://github.com/user-attachments/assets/612d287c-8bd7-45fe-bdbb-ff85e7379ef7" />
**Workaround:**
You can directly specify the version number you want by replacing the `get_latest_version()` function with:
```shell
get_latest_version() {
echo "1.6.0"
}
```
As mentioned in https://github.com/fosrl/newt/issues/198#issuecomment-3638832068
**✅ Alternative Solution:**
Alternatively, you can use [this modified script](https://gist.github.com/Malith-Rukshan/9b9c8183f8a5e4151bdf1df40a4e5a3b) that already includes the fix:
```bash
curl -fsSL https://gist.github.com/Malith-Rukshan/9b9c8183f8a5e4151bdf1df40a4e5a3b/raw/3c2d9feff840d8ae0449e181e53ca819f2cb3aa9/get-newt.sh | bash
```
<img width="2512" height="540" alt="Image" src="https://github.com/user-attachments/assets/380701ba-fd33-4d04-b765-d864910f6682" />
Can confirm that this works; after updating the script and executing it, newt is now properly getting its' config file, and handling connections properly. Much appreciated for the fix!
<!-- gh-comment-id:3639792284 -->
@mkadrlik commented on GitHub (Dec 11, 2025):
Can confirm that this works; after updating the script and executing it, `newt` is now properly getting its' config file, and handling connections properly. Much appreciated for the fix!
@marcschaeferger commented on GitHub (Dec 11, 2025):
@legionGer @HubEight @gshomelab @bbe123
Fixed now. I just verified it in a fresh VM.
@Tilvisun @Malith-Rukshan It’s not related to the RC release, but to the patch release 1.6.1, which was created only to fix the Nix package / failing go test.
When 1.6.1 was published, the latest tag was moved from 1.6.0 to 1.6.1, but the 1.6.1
release was withdrawn in the release progress for a few reasons. We will re-release 1.6.1 soon.
<!-- gh-comment-id:3639986196 -->
@marcschaeferger commented on GitHub (Dec 11, 2025):
@legionGer @HubEight @gshomelab @bbe123
Fixed now. I just verified it in a fresh VM.
@Tilvisun @Malith-Rukshan It’s not related to the RC release, but to the patch release 1.6.1, which was created **only** to fix the Nix package / failing go test.
When 1.6.1 was published, the latest tag was moved from 1.6.0 to 1.6.1, but the [1.6.1](https://github.com/fosrl/newt/releases/tag/1.6.1)
release was withdrawn in the release progress for a few reasons. We will re-release 1.6.1 soon.
But for now i added the latest tag back to 1.6.0
See #194 for details.
<img width="687" height="244" alt="Image" src="https://github.com/user-attachments/assets/34433943-4976-436f-9837-56ae545b52c3" />
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @legionGer on GitHub (Dec 10, 2025).
Original GitHub issue: https://github.com/fosrl/newt/issues/198
Describe the Bug
Hey,
I tried installing newt on both Alpine and Debian 13, the install script will fail on both ...
xxx@newt:~# curl -fsSL https://pangolin.net/get-newt.sh | bash [INFO] Installing latest version of newt... [INFO] Fetching latest version from GitHub... [ERROR] Failed to fetch latest version informationcurl -fsSL https://api.github.com/repos/fosrl/newt/releases/latest returns a 404.
Installing newt manually will also fail to fetch information about the latest version.
Environment
To Reproduce
Try installing newt on a fresh OS.
Expected Behavior
To download newt-
@HubEight commented on GitHub (Dec 10, 2025):
I have this error too.
@gshomelab commented on GitHub (Dec 10, 2025):
Getting the same error
@Tilvisun commented on GitHub (Dec 10, 2025):
I suspect the new RC version as the reason.
As workaround, you could download the installer script and hardcode the latest normal version:
replace this:
https://github.com/fosrl/newt/blob/1271e8235e91c2d28b024339ad4092a60a092886/get-newt.sh#L33-L60
with:
echo "1.6.0"@bbe123 commented on GitHub (Dec 10, 2025):
Same issue here, deb 13
@Malith-Rukshan commented on GitHub (Dec 11, 2025):
Since this repository removed the latest version (Release ID) from GitHub, the default installation script no longer works. The script relies on the
https://api.github.com/repos/fosrl/newt/releases/latestendpoint to fetch the latest version, which now returns a 404 error.Workaround:
You can directly specify the version number you want by replacing the
get_latest_version()function with:As mentioned in https://github.com/fosrl/newt/issues/198#issuecomment-3638832068
✅ Alternative Solution:
Alternatively, you can use this modified script that already includes the fix:
@mkadrlik commented on GitHub (Dec 11, 2025):
Can confirm that this works; after updating the script and executing it,
newtis now properly getting its' config file, and handling connections properly. Much appreciated for the fix!@marcschaeferger commented on GitHub (Dec 11, 2025):
@legionGer @HubEight @gshomelab @bbe123
Fixed now. I just verified it in a fresh VM.
@Tilvisun @Malith-Rukshan It’s not related to the RC release, but to the patch release 1.6.1, which was created only to fix the Nix package / failing go test.
When 1.6.1 was published, the latest tag was moved from 1.6.0 to 1.6.1, but the 1.6.1
release was withdrawn in the release progress for a few reasons. We will re-release 1.6.1 soon.
But for now i added the latest tag back to 1.6.0
See #194 for details.
@oschwartz10612 commented on GitHub (Dec 11, 2025):
Thank you @marcschaeferger!!