Solving problems when setting up the web server
If you cannot reach the web server, this can have a variety of causes. Verify the following:
- Are the ports unlocked?
In the case the firewall has blocked the ports, enable them. The default port for HTTP is 80, the default port for HTTPS is 443.
- Start the AdminClient and open the module Global settings.
- Click on the Webserver button and change the port number for HTTP and HTTPS in the Port field.
- Confirm by clicking on OK.
- Are you running the versiondog server from a different web server (Apache, Nginx etc.) that is blocking the ports?
If yes, then switch to other ports.
- Does the user have the required rights needed in order to start the web server?
If not, please contact your versiondog administrator.
- Are the processes VDogWebServer.exe and VDogReportingServer.exe running?
Use the Windows Task Manager to check if the processes are running. If this isn't the case, restart VDogMasterService.
- Are you using private keys?
If so, make sure that these are not password protected. The use of password protected private keys with the web server is not supported by versiondog . The field for entering the password will not appear and as such it is not possible to start the web server. When exporting private keys, please be aware that they exported without password protection, otherwise it is not possible to use the web server.
Support for password protected private keys for future versiondog versions is being considered!
- Are you using Microsoft Internet Explorer and experiencing problems when you try to display the web server?
If so, deactivate the compatibility view. In Internet Explorer 11, for example, proceed as follows:
- Open Internet Explorer, click on Extras and then Compatibility View Settings.
- Under Websites you've added to Compatibility View: select a web server entry, click on Remove and then deactivate the check box Display Internet sites in compatibility mode.
FAQ:: The versiondog web server will not open. What could the potential problem be and how can this be solved?
If a webserver is already active on the computer on which the versiondog web server is installed, you will no loner be able to start the web server. The cause of this is that ports 80 (HTTP) and 443 (HTTPS) are used as standard for every web server and a port can only ever be used for a single application.
If it all possible, both system should be kept seperate, and if possible, on two different servers (virtual or real) with different IP addresses.
If variant 1 is not possible, you will to ensure that one of the two servers that it uses different ports. This however brings the disadvantage that the port number needs to attached to the adress with a colon when you access this webserver via the browser. (This is not necessary with standard ports)
Proceed as follows:
The path to your web server may contain special characters (= non ASCII characters). A possible solution is the following: Uninstall and reinstall versiondog with the existing server archive (archives are never deleted when you uninstall versiondog ). Select a path without special characters for the new installation. Set up the WebClient again and call it up in the browser.
If you have tried all scenarios listed above but still continue to experience problems with the web server, please contact support and send in the files in the directory: vdServerArchive/VD$A/Webserver.