Any errors in the logs? On Fri, 12 Jul 2019 at 10:43, Equinoxe 4 <rodolfo_gonza...@hotmail.com> wrote:
> Yes, I modified it too. In fact I connected by https when I upgraded. > > Obtener Outlook para Android <https://aka.ms/ghei36> > > ------------------------------ > *From:* Maxim Solodovnik <solomax...@gmail.com> > *Sent:* Thursday, July 11, 2019 10:39:19 PM > *To:* Openmeetings user-list <user@openmeetings.apache.org> > *Subject:* Re: Can not connect to websockets. > > Hello Rodolfo, > > Have you also modified jee-*.xml to enable HTTPS? > > > On Fri, 12 Jul 2019 at 06:42, Equinoxe 4 <rodolfo_gonza...@hotmail.com> > wrote: > >> Hello, >> >> >> >> I upgraded from 4.0.5 to 4.0.8 according to the “web interface” procedure >> found at https://openmeetings.apache.org/Upgrade.html . I dropped the >> old database, created a new empty one, went to >> https://meetingrooms.example.com:5443 (with the new code) , followed the >> configuration steps, which finished without errors (neither in the web nor >> in the server), and logged in with the admin user. Then I got this in >> Firefox: >> >> >> >> Firefox can’t establish a connection to the server at wss:// >> meetingrooms.example.com:5443/openmeetings/wicket/websocket?pageId=5&wicket-ajax-baseurl=.&wicket-app-name=OpenmeetingsApplication >> . >> >> >> >> The firewall is opened for HTTPS traffic to 5443. >> >> >> >> My red5.properties is as follows (it worked with 4.0.5): >> >> >> >> ################################ red5.properties >> ############################### >> >> >> >> # Socket policy >> >> policy.host=0.0.0.0 >> >> policy.port=843 >> >> >> >> # HTTP >> >> http.host=0.0.0.0 >> >> http.port=5080 >> >> https.port=5443 >> >> http.URIEncoding=UTF-8 >> >> http.max_headers_size=8192 >> >> http.max_keep_alive_requests=-1 >> >> http.max_threads=20 >> >> http.acceptor_thread_count=10 >> >> http.processor_cache=20 >> >> >> >> # RTMP >> >> rtmp.host=0.0.0.0 >> >> rtmp.port=1935 >> >> rtmp.io_threads=8 >> >> rtmp.send_buffer_size=65536 >> >> rtmp.receive_buffer_size=65536 >> >> rtmp.ping_interval=1000 >> >> rtmp.max_inactivity=60000 >> >> rtmp.max_handshake_time=5000 >> >> rtmp.tcp_nodelay=true >> >> rtmp.tcp_keepalive=false >> >> rtmp.default_server_bandwidth=10000000 >> >> rtmp.default_client_bandwidth=10000000 >> >> rtmp.client_bandwidth_limit_type=2 >> >> rtmp.bandwidth_detection=false >> >> rtmp.encoder_base_tolerance=5000 >> >> rtmp.encoder_drop_live_future=false >> >> # traffic optimization hinting. to disable set traffic class set to -1 >> >> # low delay + high throughput == 24 (0x18) >> >> rtmp.traffic_class=-1 >> >> # requested maximum length of the queue of incoming connections >> >> rtmp.backlog=32 >> >> # the interval (seconds) between each throughput calculation >> >> rtmp.thoughput_calc_interval=15 >> >> # enable use of the default mina acceptor >> >> rtmp.default_acceptor=true >> >> # socket i/o pool sizes used when default acceptor is disabled >> >> rtmp.initial_pool_size=0 >> >> rtmp.max_pool_size=2 >> >> rtmp.max_processor_pool_size=8 >> >> rtmp.executor_keepalive_time=60000 >> >> mina.logfilter.enable=false >> >> # scheduler configs (per application) >> >> rtmp.scheduler.pool_size=8 >> >> rtmp.deadlockguard.sheduler.pool_size=8 >> >> # message executor configs (per application) - adjust these as needed if >> you get tasks rejected >> >> rtmp.executor.core_pool_size=4 >> >> rtmp.executor.max_pool_size=32 >> >> rtmp.executor.queue_capacity=64 >> >> # drop audio packets when queue is almost full, to disable this, set to 0 >> >> rtmp.executor.queue_size_to_drop_audio_packets=60 >> >> # maximum amount of time allotted to process a single rtmp message / >> packet in milliseconds, set it as 0 to disable timeout >> >> rtmp.max_handling_time=2000 >> >> # connection tweaks - dont modify unless you know what you're doing >> >> rtmp.channel.initial.capacity=3 >> >> rtmp.channel.concurrency.level=1 >> >> rtmp.stream.initial.capacity=1 >> >> rtmp.stream.concurrency.level=1 >> >> rtmp.pending.calls.initial.capacity=3 >> >> rtmp.pending.calls.concurrency.level=1 >> >> rtmp.reserved.streams.initial.capacity=1 >> >> rtmp.reserved.streams.concurrency.level=1 >> >> # maximum packet size allowed in bytes >> >> rtmp.max_packet_size=3145728 >> >> >> >> # RTMPS >> >> rtmps.host=0.0.0.0 >> >> rtmps.port=8443 >> >> rtmps.ping_interval=5000 >> >> rtmps.max_inactivity=60000 >> >> rtmps.max_keep_alive_requests=-1 >> >> rtmps.max_threads=8 >> >> rtmps.acceptor_thread_count=2 >> >> rtmps.processor_cache=20 >> >> # RTMPS Key and Trust store parameters >> >> rtmps.keystorepass=***** >> >> rtmps.keystorefile=conf/keystore.jks >> >> rtmps.truststorepass=***** >> >> rtmps.truststorefile=conf/truststore.jks >> >> >> >> # RTMPT >> >> rtmpt.host=0.0.0.0 >> >> rtmpt.port=8088 >> >> rtmpt.ping_interval=5000 >> >> rtmpt.max_inactivity=60000 >> >> rtmpt.max_handshake_time=5000 >> >> rtmpt.max_keep_alive_requests=-1 >> >> rtmpt.max_threads=8 >> >> rtmpt.acceptor_thread_count=2 >> >> rtmpt.processor_cache=20 >> >> rtmpt.encoder_base_tolerance=5000 >> >> rtmpt.encoder_drop_live_future=true >> >> # better setting for streaming media >> >> rtmpt.target_reponse_size=32768 >> >> # best setting for small messages or shared objects >> >> #rtmpt.target_reponse_size=8192 >> >> # max incoming messages to process at a time. the most that FP appears to >> send is 166 >> >> rtmpt.max_in_msg_process=166 >> >> # max time in millis that we will wait when offering data to the in or >> out queue >> >> rtmpt.max_queue_offer_time=125 >> >> # max offer attempts >> >> rtmpt.max_queue_offer_attempts=4 >> >> >> >> # WebSocket >> >> ws.host=0.0.0.0 >> >> ws.port=8081 >> >> >> >> # Debug proxy (needs to be activated in red5-core.xml) >> >> proxy.source_host=127.0.0.1 >> >> proxy.source_port=1936 >> >> proxy.destination_host=127.0.0.1 >> >> proxy.destination_port=1935 >> >> >> >> # JMX >> >> jmx.rmi.host=localhost >> >> jmx.rmi.port=9999 >> >> jmx.rmi.sport=9998 >> >> jmx.rmi.port.remoteobjects= >> >> jmx.keystorepass=***** >> >> jmx.mina.monitor.enable=false >> >> jmx.mina.poll.interval=1000 >> >> # Whether to always create the registry in-process, not attempting to >> >> # locate an existing registry at the specified port. Set to "true" in >> order >> >> # to avoid the overhead of locating an existing registry when you always >> intend >> >> # to create a new registry in any case. >> >> jmx.registry.create=true >> >> # Whether or not the MBeanServerFactoryBean should attempt to locate a >> running >> >> # MBeanServer before creating one >> >> jmx.reuse.existing.server=true >> >> # Whether to register the MBeanServer with the MBeanServerFactory, making >> it >> >> # available through MBeanServerFactory.findMBeanServer() >> >> jmx.register.factory=true >> >> # Whether any threads started for the JMXConnectorServer should be >> started as daemon threads >> >> jmx.daemon=true >> >> # Whether the JMXConnectorServer should be started in a separate thread >> >> jmx.threaded=true >> >> >> >> # Server properties >> >> # max events to send in a single update >> >> so.max.events.per.update=64 >> >> so.scheduler.pool_size=4 >> >> keyframe.cache.entry.max=500 >> >> war.deploy.server.check.interval=600000 >> >> fileconsumer.delayed.write=true >> >> fileconsumer.queue.size=120 >> >> fileconsumer.wait.for.keyframe=true >> >> subscriberstream.buffer.check.interval=5000 >> >> subscriberstream.underrun.trigger=100 >> >> subscriberstream.max.pending.frames=10 >> >> subscriberstream.max.sequential.frames=10 >> >> broadcaststream.auto.record=false >> >> >> >> >> ################################################################################ >> >> >> >> If you need some more information (the red5.sh output) please ask me 😊 >> >> >> >> Any help is appreciated. >> >> Rodolfo. >> >> >> >> >> >> >> > > > -- > WBR > Maxim aka solomax > -- WBR Maxim aka solomax
