[X] My Assistant

So it's a comcast issue? Great that's never getting fixed I guess.

I'm on comcast as well, so that's great

Yup I might as well delete H@H off my PC because it's just eating space now, Comcast ain't gonna fix shit.

Yup I might as well delete H@H off my PC because it's just eating space now, Comcast ain't gonna fix shit.

I found a fix, if you go to [internet.xfinity.com] https://internet.xfinity.com/more under my serveices and disable advanced security protection, H@H starts working again, at least for me

I'm having a really weird issue, my logs are fine up through startup and the speed tests, but then nothing happens. That nothing else happens makes some sense because the dashboard still shows my client as offline. The weird part is that the client logs show no errors or warnings and it seems to pass the lines where it contacts the server to notify it is online and ready. I've waited a few hours now since starting it back up (a few times, and comp restarts). It was working yesterday on 1.6.

Hmm... Seems like something in my OpenVPN config was messing it up. I haven't used that in a while so I just removed it instead of figuring out what was wrong. But I seem to be up and running now!

Update: Well, it seems like it's running MOSTLY right. Every once in a while it'll still timeout on server checkins and my quality tanked sometime in the last 5 hours. Restarted it and quality is slowly climbing back. Hopefully it was just a blip! And now we're back down to 2100, ho boy. Not seeing any reason for it in my logs, though... Everything has been fine for the last hour or so.

2020-02-06T19:00:53Z [info] Loaded login settings from client_login
2020-02-06T19:00:53Z [info] Connecting to the Hentai@Home Server to register client with ID xxxxx...
2020-02-06T19:01:01Z [info] Reading Hentai@Home client settings from server...
2020-02-06T19:01:02Z [info] Applying settings...
2020-02-06T19:01:02Z [info] Finished applying settings
2020-02-06T19:01:02Z [info] CacheHandler: Attempting to load persistent cache data...
2020-02-06T19:01:02Z [info] CacheHandler: All persistent fields found, loading remaining objects
2020-02-06T19:01:02Z [info] CacheHandler: Loaded static range ages
2020-02-06T19:01:02Z [info] CacheHandler: Loaded LRU cache
2020-02-06T19:01:02Z [info] CacheHandler: Successfully loaded persistent cache data
2020-02-06T19:01:02Z [info] Requesting certificate from server...
2020-02-06T19:01:02Z [info] Starting up the internal HTTP Server...
2020-02-06T19:01:02Z [info] Internal HTTP Server was successfully started, and is listening on port 22333
2020-02-06T19:01:02Z [info] Notifying the server that we have finished starting up the client...
2020-02-06T19:01:04Z [info] {1/xx.xxx.xx.xx} Code=200 Bytes=36 GET /servercmd/still_alive//1581015663/fc4130579e57818aea36d2769c1b17fedc695c43 HTTP/1.1
2020-02-06T19:01:04Z [info] {1/xx.xxx.xx.xx} Code=200 Bytes=36 Finished processing request in 0.00 seconds
2020-02-06T19:01:05Z [info] {3/xx.xxx.xx.xx} Code=200 Bytes=2500002 GET /servercmd/speed_test/testsize=2500002/1581015664/d34b1729fd78125a1bf1e6ac50d9d4f2f5abe4e0 HTTP/1.1
2020-02-06T19:01:05Z [info] {2/xx.xxx.xx.xx} Code=200 Bytes=2500001 GET /servercmd/speed_test/testsize=2500001/1581015664/68d479942f793c81cbfe27be274e600eca93615c HTTP/1.1
2020-02-06T19:01:06Z [info] {2/xx.xxx.xx.xx} Code=200 Bytes=2500001 Finished processing request in 1.15 seconds (2173.91 KB/s)
2020-02-06T19:01:06Z [info] {3/xx.xxx.xx.xx} Code=200 Bytes=2500002 Finished processing request in 1.16 seconds (2151.46 KB/s)
2020-02-06T19:01:08Z [info] {4/xx.xxx.xx.xx} Code=200 Bytes=4380685 GET /servercmd/speed_test/testsize=4380685/1581015667/a88178617f317129bdc9fb96f165ea1830383450 HTTP/1.1
2020-02-06T19:01:08Z [info] {5/xx.xxx.xx.xx} Code=200 Bytes=4380686 GET /servercmd/speed_test/testsize=4380686/1581015667/d8f01d3b18fa16bb5c7b409073ff601eef36ffb7 HTTP/1.1
2020-02-06T19:01:08Z [info] {6/xx.xxx.xx.xx} Code=200 Bytes=4380684 GET /servercmd/speed_test/testsize=4380684/1581015667/86a579d70777a3957ea23c006bed8ad7c95634f2 HTTP/1.1
2020-02-06T19:01:09Z [info] {5/xx.xxx.xx.xx} Code=200 Bytes=4380686 Finished processing request in 1.46 seconds (2992.27 KB/s)
2020-02-06T19:01:09Z [info] {4/xx.xxx.xx.xx} Code=200 Bytes=4380685 Finished processing request in 1.48 seconds (2969.96 KB/s)
2020-02-06T19:01:09Z [info] {6/xx.xxx.xx.xx} Code=200 Bytes=4380684 Finished processing request in 1.50 seconds (2924.36 KB/s)

Update: It's still in startup for some reason, just got some connection requests:

2020-02-06T19:50:26Z [WARN] Rejecting connection request from 8.41.5.9 during startup.
2020-02-06T19:50:26Z [WARN] Rejecting connection request from 8.39.205.10 during startup.
2020-02-06T19:50:26Z [WARN] Rejecting connection request from 8.41.5.9 during startup.
2020-02-06T19:50:26Z [WARN] Rejecting connection request from 8.39.205.10 during startup.
2020-02-06T19:50:26Z [WARN] Rejecting connection request from 8.41.5.9 during startup.
2020-02-06T19:50:26Z [WARN] Rejecting connection request from 8.39.205.10 during startup.
2020-02-06T19:50:26Z [WARN] Rejecting connection request from 8.41.5.9 during startup.
2020-02-06T19:50:26Z [WARN] Rejecting connection request from 8.39.205.10 during startup.
2020-02-06T19:50:26Z [WARN] Rejecting connection request from 8.41.5.9 during startup.
2020-02-06T19:50:26Z [WARN] Rejecting connection request from 8.39.205.10 during startup.
2020-02-06T19:50:29Z [WARN] Rejecting connection request from 8.40.107.77 during startup.
2020-02-06T19:50:29Z [WARN] Rejecting connection request from 8.40.107.77 during startup.
2020-02-06T19:50:29Z [WARN] Rejecting connection request from 8.40.107.77 during startup.
2020-02-06T19:50:29Z [WARN] Rejecting connection request from 8.40.107.77 during startup.
2020-02-06T19:50:29Z [WARN] Rejecting connection request from 8.40.107.77 during startup.

Any ideas why it would still be in startup but not saying anything?

Update 2:
Apparently it was just taking forever to fail. Here's the relevant portion:

2020-02-06T20:01:02Z [WARN] Request host did not send Content-Length, aborting transfer. (sun.net.www.protocol.http.HttpURLConnection:http://94.100.29.74/15/rpc?clientbuild=151&act=client_start&add=&cid=26948&acttime=1581015662&actkey=6a1e79631a3126b7ecf5398600d74737556950bc)
2020-02-06T20:01:02Z [WARN] Note: A common reason for this is running firewalls with outgoing restrictions or programs like PeerGuardian/PeerBlock. Verify that the remote host is not blocked.
2020-02-06T20:01:02Z [WARN] java.net.SocketException: Invalid or missing Content-Length
2020-02-06T20:01:02Z [WARN] Retrying.. (2 tries left)
2020-02-06T20:01:07Z [WARN] java.net.SocketTimeoutException: connect timed out
2020-02-06T20:01:07Z [WARN] Retrying.. (1 tries left)
2020-02-06T20:01:08Z [WARN] Server reported expired key; attempting to refresh time from server and retrying

So Time to figure out what changed in my firewall! I should be able to figure it out from here.

This post has been edited by Kumouri: Feb 7 2020, 17:26

I found a fix, if you go to [internet.xfinity.com] https://internet.xfinity.com/more under my serveices and disable advanced security protection, H@H starts working again, at least for me

Yup that did the trick, started working the second I disabled it.

That must have been a brand new feature they added.

thankyou Tenboro (IMG:[invalid] style_emoticons/default/smile.gif)

nice

2020-02-20T01:34:50Z [info] Starting up the internal HTTP Server...
2020-02-20T01:34:51Z [info] Internal HTTP Server was successfully started, and is listening on port 443
2020-02-20T01:34:51Z [info] Notifying the server that we have finished starting up the client...
2020-02-20T01:34:58Z [WARN] Startup Failure: FAIL_CONNECT_TEST:SSL connect error
2020-02-20T01:34:58Z [info]
2020-02-20T01:34:58Z [info] ************************************************************************************************************************************
2020-02-20T01:34:58Z [info] The client has failed the external connection test.
2020-02-20T01:34:58Z [info] The server failed to verify that this client is online and available from the Internet.
2020-02-20T01:34:58Z [info] If you are behind a firewall, please check that port 443 is forwarded to this computer.
2020-02-20T01:34:58Z [info] You might also want to check that
I updated from 1.4.2 to 1.6.0 on the server. I tried to change the port but it didn't work. It was normal on 1.4.2.

^ read the text in front of you, it exist for a reason

why the picture data of my ehentai client is blurred. by the way, how exactly can I know my https address of my client

The quality of one of my h@h client often dropped to 4000-6000. I didn't take care about it because it just a new client. 2 months passed, however, the drop didn't stop. I checked the error log, finding that this kind of error occurred about twice or 3 times a day:

CODE

2020-02-20T06:22:50Z [WARN] java.net.SocketTimeoutException: connect timed out
2020-02-20T06:22:50Z [WARN] Retrying.. (2 tries left)
2020-02-20T06:22:50Z [WARN] java.net.SocketTimeoutException: connect timed out
2020-02-20T06:22:50Z [WARN] Retrying.. (2 tries left)
2020-02-20T06:22:55Z [WARN] java.net.SocketTimeoutException: connect timed out
2020-02-20T06:22:55Z [WARN] Retrying.. (1 tries left)
2020-02-20T06:22:55Z [WARN] java.net.SocketTimeoutException: connect timed out
2020-02-20T06:22:55Z [WARN] Retrying.. (1 tries left)
2020-02-20T06:23:00Z [WARN] java.net.SocketTimeoutException: connect timed out
2020-02-20T06:23:00Z [WARN] Retrying.. (0 tries left)
2020-02-20T06:23:00Z [WARN] Exhaused retries or aborted getting https://***.********.hath.network:*****/t/********
2020-02-20T06:23:00Z [WARN] java.net.SocketTimeoutException: connect timed out
2020-02-20T06:23:00Z [WARN] Retrying.. (0 tries left)
2020-02-20T06:23:00Z [WARN] Exhaused retries or aborted getting https://***.*******.hath.network:*****/t/********

Besides, another kind of error is also seen in the log. The frequency is the same as the former:

CODE

2020-02-20T07:15:55Z [WARN] java.net.NoRouteToHostException: No route to host (Host unreachable)
2020-02-20T07:15:55Z [WARN] Retrying.. (2 tries left)
2020-02-20T07:15:55Z [WARN] java.net.NoRouteToHostException: No route to host (Host unreachable)
2020-02-20T07:15:55Z [WARN] Retrying.. (2 tries left)
2020-02-20T07:15:55Z [WARN] java.net.NoRouteToHostException: No route to host (Host unreachable)
2020-02-20T07:15:55Z [WARN] Retrying.. (1 tries left)
2020-02-20T07:15:55Z [WARN] java.net.NoRouteToHostException: No route to host (Host unreachable)
2020-02-20T07:15:55Z [WARN] Retrying.. (1 tries left)
2020-02-20T07:15:55Z [WARN] java.net.NoRouteToHostException: No route to host (Host unreachable)
2020-02-20T07:15:55Z [WARN] Retrying.. (1 tries left)
2020-02-20T07:15:55Z [WARN] java.net.NoRouteToHostException: No route to host (Host unreachable)
2020-02-20T07:15:55Z [WARN] Retrying.. (0 tries left)
2020-02-20T07:15:55Z [WARN] Exhaused retries or aborted getting https://***.*********.hath.network:*****/t/*******
2020-02-20T07:15:55Z [WARN] java.net.NoRouteToHostException: No route to host (Host unreachable)
2020-02-20T07:15:55Z [WARN] Retrying.. (0 tries left)
2020-02-20T07:15:55Z [WARN] Exhaused retries or aborted getting https://***.*********.hath.network:*****/t/*******

I checked my firewall settings but the firewall is not working at all. What should I do to solve these problems?

The quality of one of my h@h client often dropped to 4000-6000. I didn't take care about it because it just a new client. 2 months passed, however, the drop didn't stop. I checked the error log, finding that this kind of error occurred about twice or 3 times a day:

4-6000 is still fine. You generally will see some quality fluctuations over day with dips during peak hours due to how it is calculated, but this will generally affect all clients in the region the same.

Those particular errors you see wouldn't affect the quality of your client.

2020-02-20T15:54:12Z [info] Starting up the internal HTTP Server...
2020-02-20T15:54:12Z [info] Internal HTTP Server was successfully started, and is listening on port 27020
2020-02-20T15:54:12Z [info] Notifying the server that we have finished starting up the client...
2020-02-20T15:54:20Z [WARN] Startup Failure: FAIL_CONNECT_TEST:SSL connect error

I tried to change the port but it didn't work. It was working yesterday.

2020-02-20T15:54:12Z [info] Starting up the internal HTTP Server...
2020-02-20T15:54:12Z [info] Internal HTTP Server was successfully started, and is listening on port 27020
2020-02-20T15:54:12Z [info] Notifying the server that we have finished starting up the client...
2020-02-20T15:54:20Z [WARN] Startup Failure: FAIL_CONNECT_TEST:SSL connect error

I tried to change the port but it didn't work. It was working yesterday.

我也一样，你是从1.4.2升级上来的的还是？

how to solve "fail to get initial stat from server?"(the only line in error log)
seems my client have been blocked from accessing the server for sometime due to flood control, what should i do?

EDIT:
the client used to work with 1.6 of h@h, and suddenly goes wrong ,i will reinstall the system to see if problem still persist.

This post has been edited by Me1_base_honor: Feb 22 2020, 11:27

https://ehwiki.org/wiki/Technical_Issues#Startup_Errors

How can I get H@H to interact nicely with Windows shutdown/restart?

I did a manual restart and: my client is still shown as Online and has to do a full cache verify.

Windows 10 1909
Java 11.0.6
Using the GUI.jar

Shut down the program and wait for it to terminate before shutting off your OS.

https://ehwiki.org/wiki/Technical_Issues#Startup_Errors

i have looked up for solutions before i post, nothing in the wiki similar to my issue. I have set the client up for h@h1.6 since it release, it suddenly failed yesterday. Still debugging.

This post has been edited by Me1_base_honor: Feb 22 2020, 11:33

4-6000 is still fine. You generally will see some quality fluctuations over day with dips during peak hours due to how it is calculated, but this will generally affect all clients in the region the same.

Those particular errors you see wouldn't affect the quality of your client.

please
2020-02-20T01:34:50Z [info] Starting up the internal HTTP Server...
2020-02-20T01:34:51Z [info] Internal HTTP Server was successfully started, and is listening on port 443
2020-02-20T01:34:51Z [info] Notifying the server that we have finished starting up the client...
2020-02-20T01:34:58Z [WARN] Startup Failure: FAIL_CONNECT_TEST:SSL connect error
2020-02-20T01:34:58Z [info]
2020-02-20T01:34:58Z [info] ************************************************************************************************************************************
2020-02-20T01:34:58Z [info] The client has failed the external connection test.
2020-02-20T01:34:58Z [info] The server failed to verify that this client is online and available from the Internet.
2020-02-20T01:34:58Z [info] If you are behind a firewall, please check that port 443 is forwarded to this computer.
2020-02-20T01:34:58Z [info] You might also want to check that
I updated from 1.4.2 to 1.6.0 on the server. I tried to change the port but it didn't work. It was normal on 1.4.2.