Certainly. The corp firewall substitutes the cert to decrypt the traffic, and browsers refused to accept this injected cert.
However, I'm not sure why that is not a problem for other domains. That should be a concern if you're using the same cert for license validation endpoint...
Yeah, about that.
Excellent site. Very trustworthy.
There is a non-starter for me - the requirement for internet connection. My application (not a product yet) is to be installed on unix boxes that may have an exit to internet but via a proxy only - or may not have it at all.(*)
On more introspection, I think that the issue is deeper - I'm plain scared by the complexity of the thing I see on your site. Geez, I only need to assign them named licenses for now - and you have everything. I do not know where to start, what do I need and what I don't...
I also don't know how much vendor lock-in will it be? Will I be able to take my data off your system if necessary, and how hard will it be? With the complexity I see I'm inclined to answer "no".
Maybe you should consider (I'm not saying that my objection is typical, but maybe) a Basic Licensing Howto -- e.g. "How to setup a licensing schema one-license-per-desktop" and show the minimal steps required if I'm selling one-time licenses for end users. And then another one for license pool - or whatever you consider the most popular licensing schemas are.
P.S. Also, the license management UI. That one of the potential time-savers - because I would have to implement it myself or do an export to Excel - but I do not see screenshots of it. One time see how to configure a license via UI is better than explaining it.
(*) Actually, there is a way for my code to use an internet-based licensing server, but other questions I mentioned are stopping me from even thinking about it.