[GH-ISSUE #325] newt initial usage on Windows saves settings on different place than when service is looking for them #1762

New Issue

GiteaMirror · 2026-04-27T22:30:21-05:00

GiteaMirror commented

2026-04-27 22:30:21 -05:00

Originally created by @robsiera on GitHub (Apr 25, 2026).
Original GitHub issue: https://github.com/fosrl/newt/issues/325

Describe the Bug

newt's initial usage on Windows saves settings on different place than when newt-as-a-service is looking for them

Environment

OS Type & Version: (e.g., Ubuntu 22.04)
Pangolin Version: 1.17.1
Gerbil Version:
Traefik Version:
Newt Version: 1.11.0
Olm Version: (if applicable)

To Reproduce

I did a fresh install of Pangolin. Self-hosted. Non-Enterprise.
I added a windows site using the newt that was downloaded with the provided curl command.
That first usage saves the config.json in %PROGRAMDATA%\olm\newt-client
When using the same newt.exe with install and start, it says:
"Saved service args to: C:\ProgramData\newt\service_args.json" and connection is not re-established.
This is probably because the config is not in the correct place? The docs say that config should be here: %PROGRAMDATA%\newt\newt-client\config.json

Expected Behavior

What I would expect: that at first usage the config is saved in the same place that is being used when using newt-as-a-service.

Or am I missing something?

Originally created by @robsiera on GitHub (Apr 25, 2026). Original GitHub issue: https://github.com/fosrl/newt/issues/325 ### Describe the Bug newt's initial usage on Windows saves settings on different place than when newt-as-a-service is looking for them ### Environment - OS Type & Version: (e.g., Ubuntu 22.04) - Pangolin Version: 1.17.1 - Gerbil Version: - Traefik Version: - Newt Version: 1.11.0 - Olm Version: (if applicable) ### To Reproduce I did a fresh install of Pangolin. Self-hosted. Non-Enterprise. I added a windows site using the newt that was downloaded with the provided curl command. That first usage saves the config.json in %PROGRAMDATA%\olm\newt-client When using the same newt.exe with install and start, it says: "Saved service args to: C:\ProgramData\newt\service_args.json" and connection is not re-established. This is probably because the config is not in the correct place? The [docs](https://docs.pangolin.net/manage/sites/install-site#service-configuration) say that config should be here: %PROGRAMDATA%\newt\newt-client\config.json ### Expected Behavior What I would expect: that at first usage the config is saved in the same place that is being used when using newt-as-a-service. Or am I missing something?

GiteaMirror commented

2026-04-27 22:30:22 -05:00

@AstralDestiny commented on GitHub (Apr 25, 2026):

The json is just your endpoint and such, I've asked in the past for changing that or allow defining it, But can only assume it's likely due to it wants a static location but %PROGRAMDATA% is the same as C:\ProgramData\ So is it just saving it same place but differing by a single folder?

INFO: 2026/04/25 17:59:31 Config file does not exist at C:\ProgramData\olm\newt-client\config.json, will create it
INFO: 2026/04/25 17:59:32 Server version: 1.18.0-rc.0
INFO: 2026/04/25 17:59:32 Saving config to: C:\ProgramData\olm\newt-client\config.json

From a brand new install what am I missing to get it to show elsewhere?

@AstralDestiny commented on GitHub (Apr 25, 2026): The json is just your endpoint and such, I've asked in the past for changing that or allow defining it, But can only assume it's likely due to it wants a static location but %PROGRAMDATA% is the same as C:\ProgramData\ So is it just saving it same place but differing by a single folder? INFO: 2026/04/25 17:59:31 Config file does not exist at C:\ProgramData\olm\newt-client\config.json, will create it INFO: 2026/04/25 17:59:32 Server version: 1.18.0-rc.0 INFO: 2026/04/25 17:59:32 Saving config to: C:\ProgramData\olm\newt-client\config.json From a brand new install what am I missing to get it to show elsewhere?

GiteaMirror commented

2026-04-27 22:30:23 -05:00

@robsiera commented on GitHub (Apr 26, 2026):

When, in the Pangolin UI, adding a site, one gets these instructions:

curl -o newt.exe -L "https://github.com/fosrl/newt/releases/download/1.11.0/newt_windows_amd64.exe"
newt.exe --id 7zxz8v04rjj16v7 --secret p4wwd04pn7jlbt1sqkdrgr2pe0my2hkfcrxvz989xsvvcxhw --endpoint https://pangolin.example.net

When executed, that will

create a config.json in C:\ProgramData\olm\newt-client\config.json
make succesful conntection

But then, when installing that same newt.exe as a window service, like this:

> newt.exe install 
> newt.exe start

it looks for the config file in a different place: C:\ProgramData\newt\newt-client\config.json
Hence the connection is NOT established.

I had to move the config file from the \olm\.. to \newt\.. folder and restart the service.
Then the connection was re-established.

This inconsistency in location between creation and reading the config file seems to be undesirable.

@robsiera commented on GitHub (Apr 26, 2026): When, in the Pangolin UI, adding a site, one gets these instructions: ``` curl -o newt.exe -L "https://github.com/fosrl/newt/releases/download/1.11.0/newt_windows_amd64.exe" newt.exe --id 7zxz8v04rjj16v7 --secret p4wwd04pn7jlbt1sqkdrgr2pe0my2hkfcrxvz989xsvvcxhw --endpoint https://pangolin.example.net ``` When executed, that will 1. create a config.json in C:\ProgramData\\**olm**\newt-client\config.json 2. make succesful conntection But then, when installing that same newt.exe as a window service, like this: ``` > newt.exe install > newt.exe start ``` it looks for the config file in a different place: C:\ProgramData\\**newt**\newt-client\config.json Hence the connection is NOT established. I had to move the config file from the \olm\\.. to \newt\\.. folder and restart the service. Then the connection was re-established. This inconsistency in location between creation and reading the config file seems to be undesirable.

GiteaMirror commented

2026-04-27 22:30:24 -05:00

@AstralDestiny commented on GitHub (Apr 26, 2026):

Well can replicate we'll look into this soon.

@AstralDestiny commented on GitHub (Apr 26, 2026): Well can replicate we'll look into this soon.

GiteaMirror commented

2026-04-27 22:30:24 -05:00

@robsiera commented on GitHub (Apr 26, 2026):

some more observations:

I should have opened this ticket on the newt repo
As the intro page of Olm repo says "Olm is being phased out", I guess the problem is that the initial config is written to the wrong, obsolete location. Or, if backwards compatibility is a thing, a fallback should be introduced.

@robsiera commented on GitHub (Apr 26, 2026): some more observations: 1. I should have opened this ticket on the newt repo 2. As the intro page of Olm repo says "Olm is being phased out", I guess the problem is that the initial config is written to the wrong, obsolete location. Or, if backwards compatibility is a thing, a fallback should be introduced.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/newt#1762