Hi, using win 10, edge as client, to connect to winflector server through public IP, after successful login, app launch fail with Page load timeout expired. Please try again. Any ideas on how to resolve this issue? Thanks in advance.
Forum
>
Product technical support
>
Page Load Timeout
Zaloguj się aby móc pisać na forum.
|
Autor: RM Data: 2020-04-20 18:52:49 |
|
|
Autor: Rafal (staff) Data: 2020-04-21 16:03:23 |
Hi, Please send winflctor server log files at: support@winflector.com (default folder: c:Winflectorserverapplogs) |
|
Autor: RM Data: 2020-04-30 01:41:42 |
All logs were submitted. |
|
Autor: RM Data: 2020-04-30 01:42:07 |
381 2020.04.29 19:32:49 ERR:4502, NUM:0 DSCR:"NETAPI groups error code" [TSV3971b] 2872 2020.04.29 19:33:24 <CINIT> [XNC] ERR:2012, NUM:0 DSCR:"LSNR: TCP timeout error" [TSV3971b] 3063 2020.04.29 19:33:24 <CINIT> [XNC] ERR:2005, NUM:1195725856 DSCR:"LSNR: TCP incorrect packet length" [TSV3971b] 3063 2020.04.29 19:33:25 <CINIT> [XNC] ERR:2005, NUM:1195725856 DSCR:"LSNR: TCP incorrect packet length" [TSV3971b] 3063 2020.04.29 19:33:29 <CINIT> [XNC] ERR:2005, NUM:1195725856 DSCR:"LSNR: TCP incorrect packet length" [TSV3971b] 2872 2020.04.29 19:33:40 <CINIT> [XNC] ERR:2012, NUM:0 DSCR:"LSNR: TCP timeout error" |
|
Autor: JHudler Data: 2020-05-07 14:46:51 |
Same issue here.... Sometime it occurs when trying to log in. Sometimes it shows up after login while loading application list. It also seems that the default timeout is very short (about 10 sec). |
|
Autor: JHudler Data: 2020-05-08 23:45:17 |
I was looking today at this a little deeper... Running in the new Edge chromium-based browser, if I access the Developer Tools (F12) after the timeout alert, there is this message in the logs: A cookie associated with a resource at http://[sitename.com]/ was set with `SameSite=None` but without `Secure`. A future release of Microsoft Edge will only deliver cookies marked `SameSite=None` if they are also marked `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5633521622188032. - Now, running with F12 (Developer Tools) open, it will login normally (all browsers); - If a SSL certificate is setup and Winflector web page run with https, it will also work (all browsers). I believe this is the best practice. - If I run in an old Firefox portable version I have in my machine, it also works. So this seems to be related to the latest browsers versions. I think in this case the Winflector embedded Web-Server should conform to this new cookie generation policy. |
1
Zaloguj się aby móc pisać na forum.
