Problem accessing Studio remotely

Support
#1

Hi, guys thanks for time and help, i am testing cuba in a linux server for acces from a network pc and i get this error

Error:
HTTP ERROR: 404
Problem accessing /. Reason:
Not Found
Powered by Jetty://

Logs:

root@test:/opt/studio-6.4.0/bin# ./studio.sh
Run Studio headless
00:01:46,180 INFO [j] CUBA Studio v.6.4.0 built on 2017-01-31 19:16:55
2017-02-01 00:01:46.255:INFO::main: Logging initialized @473ms
2017-02-01 00:01:46.440:INFO:oejs.Server:main: jetty-9.2.11.v20150529
2017-02-01 00:01:46.525:INFO:oejw.StandardDescriptorProcessor:main: NO JSP Support for /studio, did not find org.eclipse.jetty.jsp.JettyJspServlet
00:01:46,580 INFO [IOUtils] META-INF/services/org.atmosphere.cpr.AtmosphereFramework not found in class loader
2017-02-01 00:01:46.834:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppContext@d83da2e{/studio,file:/opt/studio-6.4.0/web/,AVAILABLE}
2017-02-01 00:01:46.844:INFO:oejs.ServerConnector:main: Started ServerConnector@49438269{HTTP/1.1}{0.0.0.0:8111}
2017-02-01 00:01:46.846:INFO:oejs.Server:main: Started @1065ms

#2

Hi,

Which version of Java do you use? Note that JDK 8 should be installed.

And if you launch Studio headless (without GUI), JAVA_HOME must point to the JDK .

#3

java Version:

java version "1.8.0_121"
Java™ SE Runtime Environment (build 1.8.0_121-b13)
Java HotSpot™ 64-Bit Server VM (build 25.121-b13, mixed mode)

javac -version
javac 1.8.0_121

ok, i will check the java_home

Thanks for your time and help

#4

The same error,

Test1:
root@test:/opt/studio-6.4.0/bin# export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/bin/
root@test:/opt/studio-6.4.0/bin# ./studio.sh
ERROR: JAVA_HOME is set to an invalid directory: /usr/lib/jvm/java-8-openjdk-amd64/bin/
Please set the JAVA_HOME variable in your environment to match the
location of your Java installation.

Test2:
root@test:/opt/studio-6.4.0/bin# export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/bin
root@test:/opt/studio-6.4.0/bin# ./studio.sh
ERROR: JAVA_HOME is set to an invalid directory: /usr/lib/jvm/java-8-openjdk-amd64/bin
Please set the JAVA_HOME variable in your environment to match the
location of your Java installation.

Test3:
root@test:/opt/studio-6.4.0/bin# export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64
root@test:/opt/studio-6.4.0/bin# ./studio.sh
Run Studio headless
14:15:40,713 INFO [j] CUBA Studio v.6.4.0 built on 2017-01-31 19:16:55
2017-02-01 14:15:40.791:INFO::main: Logging initialized @490ms
2017-02-01 14:15:40.900:INFO:oejs.Server:main: jetty-9.2.11.v20150529
2017-02-01 14:15:40.989:INFO:oejw.StandardDescriptorProcessor:main: NO JSP Support for /studio, did not find org.eclipse.jetty.jsp.JettyJspServlet
14:15:41,047 INFO [IOUtils] META-INF/services/org.atmosphere.cpr.AtmosphereFramework not found in class loader
2017-02-01 14:15:41.284:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppContext@d83da2e{/studio,file:/opt/studio-6.4.0/web/,AVAILABLE}
2017-02-01 14:15:41.294:INFO:oejs.ServerConnector:main: Started ServerConnector@49438269{HTTP/1.1}{0.0.0.0:8111}
2017-02-01 14:15:41.295:INFO:oejs.Server:main: Started @996ms

Error: 404
Problem accessing /. Reason:
Not Found

#5

Hi some body from the staff i try all :frowning: and i want to use cuba-platform

#6

Hi,

The error has the INFO level and could not be the reason of the problem.

Is the

Enable remote connection

option set in your Studio?
As written in the documentation remote connection is disabled by default.

If you run Studio on a system without DE, you can enable it by modifying the ~/.haulmont/studio/config.xml file.


<remote>
<enable>true</enable>
</remote>
#7

yes i have this config.xml i read all documentation :slight_smile:

/root/.haulmont/studio

root@dsgslswm02:~/.haulmont/studio# ls -lht
total 8.0K
drwxr-xr-x 2 root root 4.0K Feb 2 13:58 logs
-rw-r–r-- 1 root root 76 Feb 1 00:01 config.xml

#8

Is the problem solved?

One important thing: At first run, Studio creates several folders and files (.caches, config.xml etc). Please note that owner of this files is the user who has launched the script.
So if you run the script with sudo for the first time, you should launch it with sudo in future.

#9

Ok, Problem Solved

1 - First Start in GUI Windows/Linux Desktop
2 - Second Start from SSH Worsk Fine!

Now Playing whit cuba-platform :), thanks for the support

#10

Hi, I’m trying to do the same thing, but my server does not have a DE at all, so having the first starting in GUI mode is not an option. How can I get Studio to create the initial caches/config.xml in headless mode? (Is it possible?)

Thanks!

#11

Never mind, my issue was probably caused by something else…
I was trying to connect to http://127.0.0.1:8111/ and got the error, but using http://127.0.0.1:8111/studio/ worked perfectly.