Can't access OpenKM from the network

Problems with installing OpenKM? No problemo, the solution is closer than you think.
Forum rules
Please, before asking something see the documentation wiki or use the search feature of the forum. And remember we don't have a crystal ball or mental readers, so if you post about an issue tell us which OpenKM are you using and also the browser and operating system version. For more info read How to Report Bugs Effectively.
noname
Fresh Boarder
Fresh Boarder
Posts: 1
Joined: Mon Jun 15, 2015 11:55 am

Re: Can't access OpenKM from the network

Post by noname » Tue Jun 16, 2015 5:55 am

I got the same issue also, but I installed OpenKM 6.3 community version in centos 7 minimal version, tomcat is used for this version of OpenKM. Does anyone has any idea?

This is my /opt/OpenKM/tomcat/conf/server.xml:

Code: Select all

  <Connector port="8080" address="0.0.0.0" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" />

<!--
    <Connector executor="tomcatThreadPool"
               port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" />
    -->

jllort
Moderator
Moderator
Posts: 9380
Joined: Fri Dec 21, 2007 11:23 am
Location: Sineu - ( Illes Balears ) - Spain
Contact:

Re: Can't access OpenKM from the network

Post by jllort » Wed Jun 17, 2015 7:11 am

You must try to connect from server using the ip ( also see netstat -an | grep 8080 to see bindings ). If you can connect from server using ip, then probably you got a miss configuration with firewall or similar

MNSnilesh
Fresh Boarder
Fresh Boarder
Posts: 3
Joined: Fri Apr 15, 2016 3:56 am
Location: India

Re: Can't access OpenKM from the network

Post by MNSnilesh » Mon Apr 18, 2016 10:18 am

I installed open km on network (Windows 7) and want to access from another computer but I am not able to access the OpenKm by URl like "http://115.112.56.170:8080/OpenKm/login.jsp" . Please sagest me, how can I access OpenKm from network by URL.

jllort
Moderator
Moderator
Posts: 9380
Joined: Fri Dec 21, 2007 11:23 am
Location: Sineu - ( Illes Balears ) - Spain
Contact:

Re: Can't access OpenKM from the network

Post by jllort » Tue Apr 19, 2016 8:31 pm

- First be sure from the server can access from this ip. ( Otherwise take a look at $TOMCAT_HOME/conf/server.xml )

Code: Select all

<Connector address="0.0.0.0" connectionTimeout="20000" port="8180" protocol="HTTP/1.1" redirectPort="8443"/>
- Take a look at netstat -an ( to see if the 8080 port is binding )

- Be sure your firewall is not locking this port.

macsimax
Fresh Boarder
Fresh Boarder
Posts: 1
Joined: Thu Sep 15, 2016 12:20 pm

Re: Can't access OpenKM from the network

Post by macsimax » Fri Sep 16, 2016 9:38 am

I had problems in network connection solved typing
"http://115.112.56.170:8080"
instead of
"http://115.112.56.170:8080/OpenKm/login.jsp" or
"http://115.112.56.170:8080/OpenKm"

jllort
Moderator
Moderator
Posts: 9380
Joined: Fri Dec 21, 2007 11:23 am
Location: Sineu - ( Illes Balears ) - Spain
Contact:

Re: Can't access OpenKM from the network

Post by jllort » Sat Sep 17, 2016 9:23 pm

The correct url should be with OpenKM with O, K and M in uppercase. The context is case sensitive try with http://115.112.56.170:8080/OpenKM

NMGMarques
Fresh Boarder
Fresh Boarder
Posts: 1
Joined: Thu Jan 12, 2017 8:59 am

Re: Re:Can't access OpenKM from the network

Post by NMGMarques » Thu Jan 12, 2017 9:09 am

alloydog wrote:Try this:

Start OpenKM from a terminal with:
run.sh -b 0.0.0.0 (for Linux)
run.bat -b 0.0.0.0 (for Windows)

Remember to keep the terminal open.

On another PC, open a web browser at the address:
http://<server.ip.address>:8080/OpenKM

This thread might help: Remote connection to server
I cannot access from an outside network. I keep seeing post and wiki entries telling me to use run.bat -b 0.0.0.0 but I can't find any run.bat file. This on version 6.3.2 (build: 8289) running off Windows 7 64 bit. I did try running startup.bat -b 0.0.0.0 but still no joy. Firewall is disabled and correct port forwarding is present for 8080. I can connect to the machine from outside and even run other web apps from it.

Here's the netstat -an result if it helps:

Code: Select all

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2869           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3306           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5050           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5051           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5357           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5938           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:8080           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:8081           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:9117           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:32400          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:36123          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49155          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49317          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49322          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:51808          0.0.0.0:0              LISTENING
  TCP    127.0.0.1:5354         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:5939         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:5939         127.0.0.1:49310        ESTABLISHED
  TCP    127.0.0.1:5939         127.0.0.1:58698        ESTABLISHED
  TCP    127.0.0.1:8005         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:8009         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:9990         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:10000        0.0.0.0:0              LISTENING
  TCP    127.0.0.1:32401        0.0.0.0:0              LISTENING
  TCP    127.0.0.1:49222        0.0.0.0:0              LISTENING
  TCP    127.0.0.1:49223        127.0.0.1:49224        ESTABLISHED
  TCP    127.0.0.1:49224        127.0.0.1:49223        ESTABLISHED
  TCP    127.0.0.1:49310        127.0.0.1:5939         ESTABLISHED
  TCP    127.0.0.1:49315        127.0.0.1:49316        ESTABLISHED
  TCP    127.0.0.1:49316        127.0.0.1:49315        ESTABLISHED
  TCP    127.0.0.1:49347        127.0.0.1:49348        ESTABLISHED
  TCP    127.0.0.1:49348        127.0.0.1:49347        ESTABLISHED
  TCP    127.0.0.1:58698        127.0.0.1:5939         ESTABLISHED
  TCP    192.168.1.3:139        0.0.0.0:0              LISTENING
  TCP    192.168.1.3:5051       0.0.0.0:0              LISTENING
  TCP    192.168.1.3:8082       0.0.0.0:0              LISTENING
  TCP    192.168.1.3:32400      192.168.1.81:54832     ESTABLISHED
  TCP    192.168.1.3:51808      46.166.191.8:49845     TIME_WAIT
  TCP    192.168.1.3:51808      65.95.221.136:61783    TIME_WAIT
  TCP    192.168.1.3:51808      84.52.146.128:62381    TIME_WAIT
  TCP    192.168.1.3:51808      165.255.132.226:26319  TIME_WAIT
  TCP    192.168.1.3:51808      173.30.24.186:64720    TIME_WAIT
  TCP    192.168.1.3:51808      173.30.24.186:64960    TIME_WAIT
  TCP    192.168.1.3:51808      183.87.216.243:48900   TIME_WAIT
  TCP    192.168.1.3:51808      208.167.254.53:64209   TIME_WAIT
  TCP    192.168.1.3:52852      104.20.195.17:443      CLOSE_WAIT
  TCP    192.168.1.3:52853      54.230.196.238:443     CLOSE_WAIT
  TCP    192.168.1.3:52854      147.75.199.66:80       CLOSE_WAIT
  TCP    192.168.1.3:52856      5.9.136.14:443         CLOSE_WAIT
  TCP    192.168.1.3:52857      50.16.249.143:443      CLOSE_WAIT
  TCP    192.168.1.3:52858      104.25.209.26:80       CLOSE_WAIT
  TCP    192.168.1.3:55875      169.51.65.136:5938     ESTABLISHED
  TCP    192.168.1.3:55878      82.94.168.55:443       ESTABLISHED
  TCP    192.168.1.3:58295      104.31.18.30:443       CLOSE_WAIT
  TCP    192.168.1.3:58296      85.195.102.27:443      CLOSE_WAIT
  TCP    192.168.1.3:58297      104.24.119.221:443     CLOSE_WAIT
  TCP    192.168.1.3:58697      217.146.14.43:5938     ESTABLISHED
  TCP    192.168.1.3:59200      5.9.136.14:443         ESTABLISHED
  TCP    192.168.1.3:59457      104.25.90.26:80        CLOSE_WAIT
  TCP    192.168.1.3:59459      216.58.214.179:443     CLOSE_WAIT
  TCP    192.168.1.3:59460      173.236.225.67:80      CLOSE_WAIT
  TCP    192.168.1.3:59461      88.221.52.218:80       CLOSE_WAIT
  TCP    192.168.1.3:63032      54.90.121.236:9050     ESTABLISHED
  TCP    [::]:135               [::]:0                 LISTENING
  TCP    [::]:445               [::]:0                 LISTENING
  TCP    [::]:2869              [::]:0                 LISTENING
  TCP    [::]:3306              [::]:0                 LISTENING
  TCP    [::]:3389              [::]:0                 LISTENING
  TCP    [::]:5051              [::]:0                 LISTENING
  TCP    [::]:5357              [::]:0                 LISTENING
  TCP    [::]:5938              [::]:0                 LISTENING
  TCP    [::]:8080              [::]:0                 LISTENING
  TCP    [::]:8081              [::]:0                 LISTENING
  TCP    [::]:9117              [::]:0                 LISTENING
  TCP    [::]:49152             [::]:0                 LISTENING
  TCP    [::]:49153             [::]:0                 LISTENING
  TCP    [::]:49154             [::]:0                 LISTENING
  TCP    [::]:49155             [::]:0                 LISTENING
  TCP    [::]:49317             [::]:0                 LISTENING
  TCP    [::]:49322             [::]:0                 LISTENING
  TCP    [::]:51808             [::]:0                 LISTENING
  TCP    [::1]:8080             [::1]:59238            TIME_WAIT
  TCP    [::1]:8080             [::1]:59239            TIME_WAIT
  TCP    [::1]:8080             [::1]:59241            TIME_WAIT
  TCP    [::1]:8080             [::1]:59242            TIME_WAIT
  TCP    [::1]:8080             [::1]:59243            TIME_WAIT
  TCP    [::1]:8080             [::1]:59244            TIME_WAIT
  TCP    [::1]:8080             [::1]:59246            TIME_WAIT
  TCP    [::1]:8080             [::1]:59247            TIME_WAIT
  TCP    [::1]:8080             [::1]:59248            FIN_WAIT_2
  TCP    [::1]:8080             [::1]:59249            FIN_WAIT_2
  TCP    [::1]:8081             [::1]:53103            ESTABLISHED
  TCP    [::1]:53103            [::1]:8081             ESTABLISHED
  TCP    [::1]:59248            [::1]:8080             CLOSE_WAIT
  TCP    [::1]:59249            [::1]:8080             CLOSE_WAIT
  UDP    0.0.0.0:500            *:*
  UDP    0.0.0.0:1900           *:*
  UDP    0.0.0.0:1900           *:*
  UDP    0.0.0.0:1901           *:*
  UDP    0.0.0.0:3702           *:*
  UDP    0.0.0.0:3702           *:*
  UDP    0.0.0.0:3702           *:*
  UDP    0.0.0.0:3702           *:*
  UDP    0.0.0.0:3838           *:*
  UDP    0.0.0.0:3838           *:*
  UDP    0.0.0.0:4500           *:*
  UDP    0.0.0.0:5355           *:*
  UDP    0.0.0.0:32410          *:*
  UDP    0.0.0.0:32412          *:*
  UDP    0.0.0.0:32413          *:*
  UDP    0.0.0.0:32414          *:*
  UDP    0.0.0.0:36123          *:*
  UDP    0.0.0.0:50862          *:*
  UDP    0.0.0.0:51808          *:*
  UDP    0.0.0.0:54668          *:*
  UDP    0.0.0.0:54670          *:*
  UDP    0.0.0.0:59141          *:*
  UDP    0.0.0.0:63489          *:*
  UDP    127.0.0.1:1900         *:*
  UDP    127.0.0.1:6771         *:*
  UDP    127.0.0.1:51067        *:*
  UDP    127.0.0.1:62503        *:*
  UDP    127.0.0.1:63063        *:*
  UDP    192.168.1.3:137        *:*
  UDP    192.168.1.3:138        *:*
  UDP    192.168.1.3:1900       *:*
  UDP    192.168.1.3:5353       *:*
  UDP    192.168.1.3:5353       *:*
  UDP    192.168.1.3:6771       *:*
  UDP    192.168.1.3:51066      *:*
  UDP    192.168.1.3:59138      *:*
  UDP    192.168.1.3:59139      *:*
  UDP    192.168.1.3:59140      *:*
  UDP    192.168.1.3:62502      *:*
  UDP    192.168.1.3:63062      *:*
  UDP    [::]:500               *:*
  UDP    [::]:3702              *:*
  UDP    [::]:3702              *:*
  UDP    [::]:3702              *:*
  UDP    [::]:3702              *:*
  UDP    [::]:4500              *:*
  UDP    [::]:50863             *:*
  UDP    [::]:51808             *:*
  UDP    [::]:54669             *:*
  UDP    [::]:54671             *:*
  UDP    [::]:59142             *:*
  UDP    [::1]:1900             *:*
  UDP    [::1]:5353             *:*
  UDP    [::1]:62501            *:*
Can anyone help?

Further I am having difficulty getting this to run on a 32 bit box where I intended to test it as the 64 bit box is not mine. Is 32 bit not supported?

jllort
Moderator
Moderator
Posts: 9380
Joined: Fri Dec 21, 2007 11:23 am
Location: Sineu - ( Illes Balears ) - Spain
Contact:

Re: Can't access OpenKM from the network

Post by jllort » Fri Jan 13, 2017 7:23 pm

run.bat is deprecated ( that is from jboss what has been discontinued 3-4 years ago ). Now from command line you must use:

Code: Select all

catalina.bat run
About 32 bits, the problem is on Java Virtual Machine architecture. Must have at least 1,3GB of continuous free memory to starting. In a window scenario, with a lot of process running etc... is not easy. But really consider is not an OpenKM problem, is a problem with any application what uses JAVA in a 32 bits environment. Also another restriction in these scenarios is the total amount of memory what can be used for the VM. If you take a look almost applications at the present are not releasing installers for 32 bits ( I'm talking about applications like OpenKM and similars ) and everybody is releasing only 64 bits. Our next release will going in this directions and we will totally discontinued the 32 bits installer.

Will be possible on future install in a 32 bits ? yes with tomcat-openkm-bundle, but at the present we do not suggest you take in consideration the 32 bits architecture for nothing serious.

Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 1 guest