External access to Wildfly - Error 111: Connection refused

Question

External access to Wildfly - Error 111: Connection refused

Navigation

#1 by (0 votes)
#2 by (0 votes)

0

Hi, guys ... I need some tips on setting up my server for access of any machine within my network. I am testing in the following development / testing environment:

Eclipse EE Luna SR2 in Java 8;

Wildfly 8.2.1 server started by Eclipse;

In localhost my application runs beauty, but when I try to access through another machine it gives the error "The System error 111: Connection refused". I have already created exceptions in the firewall (input and output) for port 8080 and nothing. My standalone.xml is configured like this:

<interfaces>
    <interface name="management">
        <any-address />
    </interface>
    <interface name="public">
        <any-address />
    </interface>
    <interface name="unsecure">
        <inet-address value="${jboss.bind.address.unsecure:0.0.0.0}"/>
    </interface>
</interfaces>

What else do I need to do? Note: I only want access from within my network.

jboss wildfly

asked by anonymous 26.01.2018 / 21:53

2 answers

Navbar bootstrap 3.2 giving display error Query Analytics without the client being authenticated

score 0 · Answer 1

Note: google translator

You can change this
<inet-address value ="${jboss.bind.address.unsecure: 0.0.0.0}"/> Home for this
<inet-address value ="125.126.127.133"/> Home Where 125.126.127.133 is the actual IP address of the server. (can also be the host name) Home Either in the startup script or if you are running manually, add the connection argument, p. Ex% run.sh -b 125.126.127.133 or run.sh -b your.hostname.com

When you try to -b 125.126.127.133 or run.sh -b your.hostname.com and if Eclipse is starting the server, do the following:

Right-click the server, select Open.

Click the link for "Open boot configuration", first hyperlink in the upper left corner.

Add -b 125.126.127.133 or 'run.sh -b your.hostname.com' shortly after the last entry in the "Program Arguments" panel - be sure to put a space between the arguments.

Example, mine looked like this
-mp "C:/jboss-eap-7.0/modules" org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\jboss-eap-7.0\standalone Home Switch to this -mp "C:/jboss-eap-7.0/modules" org.jboss.as.standalone -b 125.126.127.133 --server-config=standalone.xml -Djboss.server.base.dir=C:\jboss-eap-7.0\standalone

score 0 · Answer 2

The final part of the log looks like this: 14: 47: 53,849 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.2.Final 14: 48: 32,576 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1) 14: 48: 32,577 WARN [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016012: Deployment deployment "Sisprot.war" contains CDI annotations but no bean archive was found (no beans.xml or class with bean defining annotations). 14: 48: 32,610 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) JBAS010417: Started Driver service with driver-name = Sisprot.war_com.mysql.jdbc.Driver_5_1 14:48:32,853 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: / Sisprot 14: 48: 32,912 INFO [org.jboss.as.server] (ServerService Thread Pool - 28) JBAS018559: Deployed "Sisprot.war" (runtime-name: "Sisprot.war") 14: 48: 33,009 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on link 14: 48: 33,010 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on link 14: 48: 33,010 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.1.Final "Tweek" started in 41889ms - Started 270 of 325 services (92 services are lazy, passive or on-demand)