DVLS: 2022.1.13.0 (not able to Update yet due Usergroup Bug)
Hi
Im trying to install Devolutions Gateway side by side on the Devolutions Server.
For the Setup i found the following Instructions: how-to-configure-gateway.pdf (windows.net)
The Setup is running fine and the Instance looks like its running.
Since im using the same Server, i will also use the same SSL Cert and the same public Key from the existing Instance:
The Ports are all open (no blocks on all Firewalls).
But Devolutions Server doesnt like the instance:
Really interessting is the point, that the DVLS Server tells me that he is not able to ping himself?
But yes, of course it is possible:
I noticed via Diagnostics the Message "Your configured public key seems to be invalid" and exported the pem from the pfx, but it doesnt changed anything at all:
Also the same, when i download the Public Key File from Devolutions Server:
Service is running:
I tried with Devolutions Gateway 2022.1.1.0 and also with the newest Version 2022.2.2.0.
The Devolution Server is accessable via Port 443, so i tried also to setup the Access URI to 443, but also here the same Problem.
Do i miss something?
Best Regards,
Andreas
Edit:
I just found out, that i missed the most important Part... It was necessary to add the Port on the Devoltutions URL like this:
Problem solved 😊
Hi!
Thanks for the update, glad you got it working!
Have a great one.
Best regards,
Alex Belisle
Hi,
I wanted to add two things for information only :
1 - If you want to install a side by side gateway, you can select the DVLS instance from the list and install the gateway via the menu
When you install it that way, there is less information to provide
You don't have to provide the access URI, the listeners, the certificat, etc. The URL of the gateway will be exactly the same as your DVLS server. The gateway instance will be created in the DVLS with right information.
2 - If you install with the standalone installation, you can specify the ports here. If you use 7171, your access URI is https://<server_name>:7171 like you set so this is good. You could change it to 443 if it is the port that you want to use.
But glad you got it working, don't hesitate if you have questions
Best regards,
François Dubois