Studio connection probem

After CUBA Studio v.1.6.4 starting on centos 6.6, i have a problem with connection:
HTTP ERROR 500

Problem accessing /studio/. Reason:

Remote connection is not permitted

Caused by:

java.lang.RuntimeException: Remote connection is not permitted
at com.haulmont.studio.server.Main$5.requestInitialized(Main.java:243)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
But studio 1.4.1 has not this problem on this server.

2 Likes

Since v.1.5.0 the Studio server does not allow to connect from non-local adresses by default. Are you sure you are connecting from the local host?

If you want to enable remote connections, just check the appropriate checkbox in the Studio server window.

What if I have only console, without GUI?

Sorry, I don’t understand. What do you mean by console?
From the stack trace I see that you have started the Studio server and trying to connect to it from web browser.

Server has not graphical desktop.

Then edit or add the following value to ~/.haulmont/studio/config.xml:

<connection>
  <remote>
    <enable>true</enable>
  </remote>
</connection>

Hm, adding it does not help. Still remote connection banned.