# The local daemon runs but cannot reach online licensing

Separate local broker discovery from outbound HTTPS, proxy and certificate problems. Use the underlying error to choose the next check.

## Compatibility

Daemon builds supporting proxy/CA settings

Published guidance with release-applicability limits. Confirm package applicability before following this guide.

## Identify which connection failed

A successful local ping does not prove access to the online licensing endpoint. Online authorisation uses HTTPS to license.sunmagnetics.net on port 443. Check the recorded network/TLS error with the organisation's network administrator.

Older client messages can label generic connection failures as firewall/antivirus problems. Preserve the underlying code and detail before changing security settings.

## Use supported configuration

1. Check that the installed daemon version supports the required corporate proxy configuration.
2. The documented settings include SMLICENSED_HTTPS_PROXY for a proxy URL, SMLICENSED_NO_PROXY for custom-proxy exclusions and SMLICENSED_CA_BUNDLE for a CA file.
3. Set the required environment for the daemon process and restart the idle daemon through the supported procedure. Existing processes do not acquire newly changed environment settings.
4. Check the resulting product licence request. TLS certificate and hostname verification must remain enabled.

## Share useful diagnostics

A reviewed log can distinguish name resolution, proxy, TLS and server-denial errors. Remove proxy passwords, keys, tokens, identifiers and private paths before sharing it. Offline authorisation and online authorisation have different connectivity requirements; a proxy change does not repair an expired or mismatched offline licence.

## Sources and verification details

Recorded inputs/builds only. Complete walkthrough and final-package acceptance remain separate.



- support:SUP-004: Generalised editorial finding; outcome qualification retained
- smlicensed:README.md: Supported environment settings; TLS; troubleshooting

- The historical proxy discussion did not contain a confirmed working customer configuration. These steps follow the maintained daemon documentation, not a claimed customer reproduction.
- Support history informed this draft. Current-source guidance has been checked; a fresh walkthrough on the intended distributed release and product-owner review remain pending.

## Related guides

- [NO_SEATS_AVAILABLE after a crash or disconnected session](/knowledge-base/shared-no-seats)
- [The licence daemon starts, but the application is still unlicensed](/knowledge-base/shared-daemon-starts-but-unlicensed)