nobody

I confirm. Rolling back to 2025 build 259 does not cause a freemium license issue. Probably the last best/good* version is the one without sending statistics from April 2025, i.e. 2025.1.1.152 :) And the funniest thing is that there is no information about the licensing change in the 2026 changel

Wow. Thanks a lot. Daniel, I could always count on you :) I'm shocked that there's only a time-limited demo now. I haven't visited the main WebCon website in a long time, not counting this forum. So, what I've been warned about so many times has been confirmed: using low-code or no-code tools and p

Today updated to 2026 build (91) nothing changed... I'm ready to abandon all plans and projects related to the WebCon platform; this environment has been giving me such a hard time lately. If it were a production environment, I probably wouldn't even wait. I've scoured the internet for genera

And one more update... service (requested by IP:8002/LicenceService) return this: Metadata publishing for this service is currently disabled. Why? and How to enabled?

And error notification on admin mailbox. I have no idea what does it mean "value cannot be null / registred connection parameters" Service: BPMS Log Range: Licensing Message: Value cannot be null. Parameter name: For the current thread not registered connection parameters. Category: Licens

Hi I have the same problem/error. All the time :[ In 2025.1 and now 2026.1 (88) Service is activated, license active (can refresh and download without any problem) Restarting services (all) doesnt help at all Logs doesnt tell me anything ... No firewall rules (disabled for checks). One server

OK, as I know in Freemium I can't disable sending data in app configuration, but I can block it on firewall (local machine or network scope) for outgoing trafic? Do you know the destination address, protocol (https?)? And is it in any way dependent on communication with the WEBCON license server?

What exact statistical data is sent to WEBCON starting from version R2?

.

.

.

.

.

.

.

.

.

.

.

.