Hi,
I've opened cmd in admin mode, downloaded olm.exe, tried to configure it via olm.exe --id xxx --secret xxx --endpoint xxx but this doesn't generate the config.json file under programdata. So I added the file manually, but now when I run olm.exe start, the installer window pops up again, same with olm.exe stop. The logfile isn't logging any activity. I'm not sure what is causing the issue.
Originally created by @OneTwo3D on GitHub (Sep 24, 2025).
Original GitHub issue: https://github.com/fosrl/olm/issues/38
Hi,
I've opened cmd in admin mode, downloaded olm.exe, tried to configure it via olm.exe --id xxx --secret xxx --endpoint xxx but this doesn't generate the config.json file under programdata. So I added the file manually, but now when I run olm.exe start, the installer window pops up again, same with olm.exe stop. The logfile isn't logging any activity. I'm not sure what is causing the issue.
The issue seems to be that the windows service is completely ignoring the config.json file or just not able to write/read it. The service runs fine, if it is being started on the command line with command line arguments but it isn't able to start automatically, as it has no way to read in the username, secret, etc
<!-- gh-comment-id:3329937149 -->
@OneTwo3D commented on GitHub (Sep 24, 2025):
The issue seems to be that the windows service is completely ignoring the config.json file or just not able to write/read it. The service runs fine, if it is being started on the command line with command line arguments but it isn't able to start automatically, as it has no way to read in the username, secret, etc
@oschwartz10612 commented on GitHub (Sep 26, 2025):
Also make sure you are not running the installer instead of the binary after running the installer! 😄
<!-- gh-comment-id:3339544895 -->
@oschwartz10612 commented on GitHub (Sep 26, 2025):
Also make sure you are not running the installer instead of the binary after running the installer! 😄
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 @OneTwo3D on GitHub (Sep 24, 2025).
Original GitHub issue: https://github.com/fosrl/olm/issues/38
Hi,
I've opened cmd in admin mode, downloaded olm.exe, tried to configure it via olm.exe --id xxx --secret xxx --endpoint xxx but this doesn't generate the config.json file under programdata. So I added the file manually, but now when I run olm.exe start, the installer window pops up again, same with olm.exe stop. The logfile isn't logging any activity. I'm not sure what is causing the issue.
@OneTwo3D commented on GitHub (Sep 24, 2025):
The issue seems to be that the windows service is completely ignoring the config.json file or just not able to write/read it. The service runs fine, if it is being started on the command line with command line arguments but it isn't able to start automatically, as it has no way to read in the username, secret, etc
@oschwartz10612 commented on GitHub (Sep 26, 2025):
Also make sure you are not running the installer instead of the binary after running the installer! 😄
@OneTwo3D commented on GitHub (Sep 26, 2025):
Thanks :) Yes, it was the installer I was running twice lol...