View Single Post
07/30/23, 03:55 PM   #1
furiousmoose0
Join Date: Sep 2018
Posts: 2
Trouble with minion getting blocked by Windows [Eero router]

So I will preface this by stating that I have gone through the extensive troubleshooting steps already. Minion has worked perfectly for a while now, and I have never had any issues. Today, it detects addons and will let me update them. After I select update, it just goes to an infinite updating bar and doesn't continue. Upon inspecting the logs, I get this error.

ERROR 2023-07-30 17:40:37,909 [Thread-107] gg.minion.service.DownloadService:call(81): Catching org.apache.http.conn.HttpHostConnectException: Connect to cdn.esoui.com:443 [cdn.esoui.com/192.168.4.1] failed: Connection refused: connect
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:158)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
at gg.minion.service.DownloadService$1.call(DownloadService.java:79)
at gg.minion.service.DownloadService$1.call(DownloadService.java:72)
at javafx.concurrent.Task$TaskCallable.call(Task.java:1423)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at javafx.concurrent.Service.lambda$null$492(Service.java:725)
at java.security.AccessController.doPrivileged(Native Method)
at javafx.concurrent.Service.lambda$executeTask$493(Service.java:724)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.TwoStacksPlainSocketImpl.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.PlainSocketImpl.connect(PlainSocketImpl.java:172)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:337)
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:141)
... 20 more

DEBUG 2023-07-30 17:40:37,910 [Thread-107] gg.minion.service.DownloadService:call(85): Null response getting addOn details.
DEBUG 2023-07-30 17:40:37,910 [Download Service Thread] gg.minion.util.DownloadManager:lambda$startUpdater$0(89): PreTake - DownloadQueue size: 0

I have tried running in admin
Minion is added to accepted apps in Windows firewall
I have no other firewall options active
I have uninstalled
I have deleted .minion
I have deleted minion.xml
I have set the IPv4stack to true
I can tracert the server just fine
Proxy is set to automatically detect settings
Went into advance settings in windows defender to ensure that inbound rules were applied for minion

I recently updated windows and I believe that is what caused this issue. Some new setting is blocking minion and I have no idea where to find it.

Any advice would be greatly appreciated.

Last edited by furiousmoose0 : 07/30/23 at 04:02 PM. Reason: added troubleshooting
  Reply With Quote