User Tools

Site Tools


faq:general:client_only_works_on_server

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
faq:general:client_only_works_on_server [2016/03/14 10:48]
gbosch
faq:general:client_only_works_on_server [2019/12/09 10:19] (current)
Line 2: Line 2:
  
 **On some installations users might encounter the problem that the GECAMed Client is only working on the same machine the GECAMed server is installed on. When trying to start the client on an other machine, it will refuse to start or the login will not work.** ​ **On some installations users might encounter the problem that the GECAMed Client is only working on the same machine the GECAMed server is installed on. When trying to start the client on an other machine, it will refuse to start or the login will not work.** ​
 +
 +FIRST OF ALL: Make sure that you are able to reach the GECAMed website located on your GECAMed server by opening a browser and connecting to 
 +  ​
 +  http://​192.168.x.x:​8080/​gecamed
 +  ​
 +Where 192.168.x.x is the IP address of your GECAMed server.
 +
 +If this site is not showing up, either,
 +  * the GECAMed server is not working -> Check if GECAMed works on the server itself
 +  * the Firewall is blocking the access from another computer -> [[faq:​technical:​firewall_ports|configure your firewall]]
 +  * You are trying with the wrong IP address -> make sure you have the right IP address for your server.
 +
 +If the Website is showing up, but the client refuses to start or login, please follow the instructions below.
  
 The problem is caused by a wrong or not working DNS configuration of the GECAMed server. ​ The problem is caused by a wrong or not working DNS configuration of the GECAMed server. ​
Line 23: Line 36:
 Make the  server'​s IP address static and declare it in its own hosts file instead of 127.0.1.1 Make the  server'​s IP address static and declare it in its own hosts file instead of 127.0.1.1
  
-remove ​the following line if it exits+Remove or out-comment ​the following line if it exits
  
    ​127.0.1.1 gecamed-server-name    ​127.0.1.1 gecamed-server-name
  
-add the following line+Add the following line
  
    ​192.168.x.x gecamed-server-name    ​192.168.x.x gecamed-server-name
  
-Where 192.168.x.x is the real IP address of your GECAMed server and gecamed-server-name is the hostname of your machine.+Where 192.168.x.x is the real IP address of your GECAMed server and gecamed-server-name is the hostname of your machine. Do not remove the "​127.0.0.1 localhost"​ line.
  
 You can find the hosts file at: You can find the hosts file at:
   * Windows: C:​\Windows\System32\drivers\etc   * Windows: C:​\Windows\System32\drivers\etc
-  * Linux/​OSX: ​ /ets/hosts+  * Linux/​OSX: ​ /etc/hosts
  
 The hosts file needs to be edited with Admin/root rights, otherwise you can't save the changes. The hosts file needs to be edited with Admin/root rights, otherwise you can't save the changes.
Line 43: Line 56:
 If even that is not working, you can try to manually bind JBoss to a specific IP address malually. If even that is not working, you can try to manually bind JBoss to a specific IP address malually.
  
-This is donw by adding the following line to the run.conf file in GECAMed/​jboss/​bin on LINUX and MAC OS installations.+This is done by adding the following line to the run.conf file in GECAMed/​jboss/​bin on LINUX and MAC OSX installations.
  
-  JAVA_OPTS="​%JAVA_OPTS -Djboss.bind.address=192.168.x.x"​+  JAVA_OPTS="​$JAVA_OPTS -Djboss.bind.address=192.168.x.x"​
  
 For Windows Installations please add the following line to the run.bat file in GECAMed/​jboss/​bin For Windows Installations please add the following line to the run.bat file in GECAMed/​jboss/​bin
faq/general/client_only_works_on_server.1457952507.txt.gz · Last modified: 2019/12/09 10:21 (external edit)