Farshad Mohajeri

Merhaba Masaüstünde çalışan mobil emulatorde çalışıyor mu ? Denediniz mi ? Chrome mobil emulator örnek olarak.

Fixed. (1608)

In this case problem lies in a different place. 503 error is a general error which shows your app has become unstable. Can you share Hyperserver log files?

Bu switching to Hyperserver you can deploy your app as standalone exe and still run it under iis.

Have you considered using Hyperserver ?

Hi, Just a quick note regarding the ssl. When using isapi dlls the whole ssl protocol is controlled by iis itself. Probably you need to apply most recent updates to enable tls 1.3. Normally tls 1.3 has been supported by iis for many years.

Probably you have missed below step: https://www.unigui.com/doc/online_help/hyperserver-isapi-module-mode.htm

Please share log files of server and Node in a private message.

Hello, Make sure Nodes are built with 1607 or later. Also HyperServer DLL should be 1607 or later.

Hi, Yes, uniGUI supports wss protocol. Apparently, that's the only way to support Websockets in a secure website. When site itself is secured, uniGUI switches to wss instead of ws. Browsers don't allow mixing https with ws. Our portal uses wss for example. https://prime.fmsoft.net/userv/mportal.dll From our docs: https://www.unigui.com/doc/online_help/index.html?websockets--ssl.htm If you want to use SSL and websockets it is recommended to configure a dedicated websockets server: https://www.unigui.com/doc/online_help/index.html?using-a-dedicated-websockets-s.htm Here is a detailed deployment example: https://www.unigui.com/doc/online_help/index.html?a-real-world-example.htm

Your app consume lots of GDI objects which means that there's a 3rd party software such a reporting tool that may crash while generating reports. So some of the sessions remain stale in the session manager. Is your app 64-bit?

Hi, Perhaps, you have forgotten to install 1607 uniGUI Runtime.

BTW, it is not recommended to use TTimer in a uniGUI application. Use TUniTimer or TUniThreadTimer where applicable.

Try this : In uniguiserver.pas Find and Change In procedure NodeRun; Application.HandleMessage With Application.ProcessMessages

We're looking into this.

BTW, are you running HyperServer as standalone EXE or Apache module?

Hi, For secured Websockets you need to assign PEM files to ServerModule.SSL. Of course, you need to obtain related PEM files first and put them in application folder.

We have found the exact reason and a fix will be published in next build. For now please apply below patch in file uniGUIUtils.pas: function uniRedirect(const ACookie, URL: string; IsAjax: Boolean = True): string; var S : string; begin S := Trim(URL); if S = '' then S := '""' else begin S := AddTrailingChar(S, '"'); S := AddLeadingChar(S, '"'); end; Result := uniSendDoc(ACookie + IfThen(IsAjax,'_clat_();', '') + 'window.onunload=null;try{enableWarnOnClose(false)}catch(e){};window.location=' + S + ';', IsAjax); end;

We are investigating the issue. Thanks

Thanks, Is your app an ISAPI DLL?

You can write a simple 64-bit app which uses same database and FireDAC to see if there's something wrong about drivers or other things.

I recommend switching to HyperServer and delpoy your app as EXE using IIS and HyperServer. Debugging DLLs is extremely difficult.

Can you reduce your app to a simple one with a database connection and a dbgrid only? Maybe there are some global variables in your app. Can it be possible?

Hello, What is the email address you have used to obtain your license?

We have applied this patch to our code so nothing should be done in next builds.