mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-01-11 14:40:25 +01:00
[BUG]: Could not make a connection to validate an individual commercial use license for xxxx #709
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @gaving on GitHub (Dec 16, 2025).
Originally assigned to: @LGUG2Z on GitHub.
Summary
Hi 👋
Thanks for the great software!
Since
wingeting0.1.39I'm getting the MDM enrolment prompt.However, running
komorebic license xxxxwith my license email is giving:-Due to this:-
f3b7f5ac42/komorebic/src/main.rs (L1675C17-L1680C18)I'm behind a proxy with my employer so I'm guessing that'll need considered when reaching out via
reqwest(common pain in this sort of environment).Is there a official/documented/manual workaround using the
icul.validationfrom thekw-icul.*.com/?email=to avoid phoning home so I can avoid the nagware?I can work it out from the code but figured I'd raise this for your view on the matter.
Version Information
Windows 11
0.1.39
Komorebi Configuration
Hotkey Configuration
Output of komorebic check
@LGUG2Z commented on GitHub (Dec 16, 2025):
Hi!
Thanks for opening this issue - I will look in to adding an optional proxy configuration option to the
komorebi.jsonconfig file for situations like theseIn the meantime, the
icul.validationfile can be generated by making a request tohttps://kw-icul.lgug2z.com/email?your-email@your-domain.com, where the email address is the one which was used to register for the licenseThis endpoint returns a JSON payload which can be saved directly to
C:\Users\<YOUR USER>\AppData\Local\komorebi\icul.validationThe
currentEndPeriodreturned by the payload is the date that the subscription is valid until, which is either the end of the paid month or the paid year depending on the billing frequency@gaving commented on GitHub (Dec 16, 2025):
Thanks for the quick response and workaround.
Good luck with the proxy implementation - from my two decades or so experience dealing with PAC files, NTLM, SSO, Kerberos, blah blah it's sometimes hit or miss getting tools playing nice within my environment.
Happy to test from my corporate world if the time comes!