Connection could not be loaded

Can you share some screenshots and the windows version? 

Maybe also share your .pro File with blurred Information. 

.pro-File:
[
{
"display_name": "NAME_VPN-1",
"gateway": "<DNS1>",
"user_portal_port": 443,
"otp": true,
"auto_connect_host": "<DNS1>",
"can_save_credentials": true,
"check_remote_availability": true,
"run_logon_script": false
},
{
"display_name": "NAME_VPN-2",
"gateway": "<DNS2>",
"user_portal_port": 443,
"otp": true,
"auto_connect_host": "<DNS2>",
"can_save_credentials": true,
"check_remote_availability": true,
"run_logon_script": false
}
]

Windows 10(x64) Version 10.0.18363 Build 18363

Screenshot from log (german):

If I do import my old .scx file I can connect without any issue.

Hello,

What is the event you see in the dashboard events tab when you are getting this error?

Please update with the results.

Regards,
ramesh

Hello Fred,

You can PM me if you like so I can go over your log files and help you to resolve this problem.

Regards,

Ramesh

Hello, please see case 9848229

Hello Fred,

Did you check the two things I had mentioned in my email? Are you still having problems? Are you able to get it working?

Regards,

Ramesh

Hello,

I can import the previous .sxc file and the user can connect without any issue (he is included).  In dashboard the same message appears as in the event's (see screenshot above). Logs can be reviewed from ftp case 9848229.

Regards,
Fred.

Hello Fred,

I cannot access that case. If you are available to PM then we can connect on a zoom call to get this resolved.

Regards,

Ramesh

Hello Fred,

Please let me know if the issue you had reported is resolved or not. If not yes resolved please let us know. If it was resolved then please let us know what was the problem and how it was resolved.

Regards,
Ramesh

The issue is not resolved. Please see PM.

just to update this thread:

It looks like authentication with AD and OTP is not working.

Hello Fred,

After the tests performed on your setup, I tried it and I do not have the problem you are seeing. I even have the special character in my password. There is a setup problem in your case and we need to figure it out. There are two things that was different in your setup. The user you were trying yesterday belonged to the Adminstrators group. Second can you try create another user in AD who is not part of the administrators group and then send an update.

Ramesh

Hello Fred,

After the tests performed on your setup, I tried it and I do not have the problem you are seeing. I even have the special character in my password. There is a setup problem in your case and we need to figure it out. There are two things that was different in your setup. The user you were trying yesterday belonged to the Adminstrators group. Second can you try create another user in AD who is not part of the administrators group and then send an update.

Ramesh

Hello Ramesh,

yes, I can confirm that this belongs to Adminstrators group. I've created a user in AD an was able to connect. Once it was changed in XG to Adminstrators group I could not connect anymore.

Please note, its important to be able to use administrators as well (especially as they are not real administrators but only have the capability of security profiles). Also there is no way to change a user back to users group.

Thanks for assistance.

Fred

Thank you Fred for the update. We will look into this issue. Also I need to understand this statement. "Once it was changed in XG toAdminstrators group". So this is what the step is. After you login as the new AD user from the User Portal with the OTP, you then move this user to the administrator group (see the step below and try it one more time please). From that point on it stops working? Is that how to re-create this issue?

Can you please try one more thing for me. After you move the user to the administrator group, please delete the OTP for this user and re-login to the user portal and generate a new OTP. Then try the  provisioning. Please let me know after you try this step.

steps I've done:

create user & otp
delete existing connection
add connection
test login -> possible

changed user to admin group
test login -> possible

delete existing connection
add connection
test login -> NOT possible

removed OTP & created new one
test login -> NOT possible

only way to let them login is now to remove the user (and theretofore OTP)
get new OTP (now he is a user again)
test login -> possible