fosrl / fosrl/newt

newt initial usage on Windows saves settings on different place than when service is looking for them

Open
#325 4 comments 0 reactions 1 assignee Claimed by @oschwartz10612 View on GitHub
bug
Dominant language
Go
Stars
908
Forks
87
Avg merge
1d 15h
Merged PRs (30d)
7

Description

### 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?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.