Hello everyone,
I’ve been using the wowza streaming engine for over a year, and now I can’t use the engine manager that shows the error below:
This site can’t be reached
Connection Refused
ERR_CONNECTION_REFUSED
Can someone help me?
Thank you all.
What changes have been made since it was working as expected @Andre Balthazar?
Can you please provide some more details about the issue and what was happening before it occurred.
Is this server in production or testing environment?
Is this an EC2 or other cloud instance or a local hardware box?
Are you out of memory? Have you done a JAVA Heap dump?
To configure Wowza Streaming Engine to create a Java Heap Dump. Details on setting this up are outlined here:
https://www.wowza.com/docs/how-to-create-a-java-heap-dump-on-wowza-streaming-engine
Please share more info when you can so we can try and better assist you. That error does not apply to just one cause. Thank you.
Hello Rose,
What changes have been made since it was working as expected @Andre Balthazar?
—> No change was made. The server operated normally until it presented the reported problem
Is this server in production or testing environment?
Is this an EC2 or other cloud instance or a local hardware box?
—> The Server is in a production environment, and hosted on a dedicated machine in a datacenter.
Are you out of memory? Have you done a JAVA Heap dump?
—> Until the problem occurred, the server had no memory problems, but I followed the steps indicated in the article: https://www.wowza.com/docs/how-to-create-a-java-heap-dump-on-wowza-streaming-engine
After the procedure in the article, the server was restarted, but the problem persists.
A note:
When I typed in my server’s url, I mistakenly put port 8087, and after the requested login, the following result was shown:
4.7.7
403
Your IP address (MY IP ADDRESS) has been blocked
Does this information help with anything?
I use the version: Wowza Streaming Engine 4 Subscription Edition 4.7.7 build20181108145350
Thank you
Hi Rose,
searching the manager’s log files, precisely wmsmanager_access.log, presented the latest records below.
#Version: 1.0
#Start-Date: 2020-01-24 15:52:04 EST
#Software: Wowza Streaming Engine Manager 4.7.7 build20181108145350
#Date: 2020-01-24
#Fields: datetimetzx-serverx-userx-severityx-categoryx-comment
2020-01-2415:52:04ESTINFOrestREST API: Authentication: Successful login for:prime:
2020-01-2419:13:06ESTINFOrestREST API: Authentication: Successful login for:prime:
2020-01-2419:19:17ESTINFOrestREST API: Authentication: Successful login for:prime:
2020-01-2419:19:52ESTWARNorg.restletAn error occurred during the communication with the remote HTTP server.: java.net.ConnectException: Connection refused|at java.net.PlainSocketImpl.socketConnect(Native Method)|at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)|at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)|at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)|at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)|
2020-01-2419:19:52ESTWARNorg.restletAn error occurred during the communication with the remote HTTP server.: java.net.ConnectException: Connection refused|at java.net.PlainSocketImpl.socketConnect(Native Method)|at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)|at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)|at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)|at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)|
After some successful access attempts, it presented 2 errors.
Does this information help?
Thank You
That does help actually as port 8088 is the default port that engine manager uses and your IP address will bind to.
For port 8087, you need to check if it is being blocked by some type of firewall or security config, or if your Wowza Engine service is unable to listen for/receive requests on this port.
Do please check if a network or firewall configuration is blocking port 8087 on your machine. You can verify if your server is able to receive requests by running an nmap on your server.
Let me know what you discover there.
Yes and thanks again for sharing that. This has to do with an error somewhere in a Java config in your files and that change being incompatible with your network.
This will require a support ticket as our engineers will need full access to your zipped up Engine files and logs.
You can submit one here and we will get it figured out for you. Sorry for the issues you are experiencing and thanks again for the good communication so we can help solve this. I’ll be sure to follow your ticket.
