Hello Andreas, For OM 5.0 you can specify `address` for Connector https://tomcat.apache.org/tomcat-9.0-doc/config/http.html For 4.0.x you need to set http.host in `red5.properties` (should work)
On Sat, 11 Apr 2020 at 02:13, ratatouille <ratatoui...@bitclusive.de> wrote: > Hello! > > After solving my problem with the keystore I see this in the log: > > 2020-04-10 20:50:27,231 [main] INFO o.a.c.http11.Http11Nio2Protocol - > Initializing ProtocolHandler ["https-jsse-nio2-0.0.0.0-5443"] > 2020-04-10 20:50:32,351 [main] ERROR o.a.catalina.util.LifecycleBase - > Failed to initialize component [Connector[org.apache.coyote.http11.Http11N > io2Protocol-5443]] > org.apache.catalina.LifecycleException: Protocol handler initialization > failed > > Caused by: java.net.BindException: Die Adresse wird bereits verwendet > translated > Caused by: java.net.BindException: The address is already in use > > The server is binding four IP-addresses: > > ens3 > inet Adresse:37.120.166.21 > > ens3:03 > inet Adresse:46.38.231.180 > > OM should run on 37.120.166.21 only. This is the log: > > 2020-04-10 20:50:32,414 [main] INFO o.a.catalina.core.StandardService - > Starting service [Tomcat] > 2020-04-10 20:50:32,418 [main] INFO o.a.catalina.core.StandardEngine - > Starting Servlet engine: [Apache Tomcat/9.0.29] > 2020-04-10 20:50:32,924 [main] INFO o.a.catalina.startup.ContextConfig - > No global web.xml found > 2020-04-10 20:50:33,229 [main] INFO o.a.c.c.C.[.[0.0.0.0].[/] - No Spring > WebApplicationInitializer types detected on classpath > 2020-04-10 20:50:44,462 [main] INFO o.a.c.c.C.[.[.0.0.0.[/openmeetings] - > No Spring WebApplicationInitializer types detected on classpath > 2020-04-10 20:50:45,244 [main] INFO c.h.config.AbstractConfigLocator - > Loading 'hazelcast.xml' from the classpath. > 2020-04-10 20:50:45,724 [main] WARN c.h.config.AbstractXmlConfigHelper - > Name of the hazelcast schema location is incorrect, using default > 2020-04-10 20:50:47,315 [main] INFO c.hazelcast.instance.AddressPicker - > [LOCAL] [dev] [3.12] Prefer IPv4 stack is true, prefer IPv6 addresses i > s false > 2020-04-10 20:50:47,360 [main] INFO c.hazelcast.instance.AddressPicker - > [LOCAL] [dev] [3.12] Picked [46.38.231.180]:5701, using socket ServerSo > cket[addr=/0:0:0:0:0:0:0:0,localport=5701], bind any local is true > 2020-04-10 20:50:47,452 [main] INFO com.hazelcast.system - > [46.38.231.180]:5701 [dev] [3.12] Hazelcast 3.12 (20190409 - 915d83a) > starting at [46 > .38.231.180]:5701 > 2020-04-10 20:50:47,457 [main] INFO com.hazelcast.system - > [46.38.231.180]:5701 [dev] [3.12] Copyright (c) 2008-2019, Hazelcast, Inc. > All Rights > Reserved. > 2020-04-10 20:50:49,430 [main] INFO c.h.s.i.o.i.BackpressureRegulator - > [46.38.231.180]:5701 [dev] [3.12] Backpressure is disabled > 2020-04-10 20:50:55,153 [main] INFO c.h.s.i.o.i.OperationExecutorImpl - > [46.38.231.180]:5701 [dev] [3.12] Starting 2 partition threads and 3 gen > eric threads (1 dedicated for priority tasks) > 2020-04-10 20:50:55,185 [main] INFO c.h.i.diagnostics.Diagnostics - > [46.38.231.180]:5701 [dev] [3.12] Diagnostics disabled. To enable add -Dhaze > lcast.diagnostics.enabled=true to the JVM arguments. > 2020-04-10 20:50:55,252 [main] INFO com.hazelcast.core.LifecycleService - > [46.38.231.180]:5701 [dev] [3.12] [46.38.231.180]:5701 is STARTING > 2020-04-10 20:50:55,368 [main] WARN com.hazelcast.instance.Node - > [46.38.231.180]:5701 [dev] [3.12] No join method is enabled! Starting > standalo > ne. > 2020-04-10 20:50:55,536 [main] INFO com.hazelcast.core.LifecycleService - > [46.38.231.180]:5701 [dev] [3.12] [46.38.231.180]:5701 is STARTED > > When I try to connect on port 5443 I get a socket timeout with links. > > It seems to connect to 46.38.231.180:5701 and not to 37.120.166.21 > > Can this be solved and is it the reason I get a socket timeout? > > Andreas > -- Best regards, Maxim
