[X] My Assistant

Is there a way to check the number of HC assigned to a client?

No.

Any chance you can not implement the 443 requirement?
Some home ISP doesn't allow port 443/website hosting
And I run H@H with a server that's also hosting my personal website and the website takes up port 443 as well....

I decided to remove the port 443 requirement for the HC ranges. Of the clients that fulfilled the other requirements, only one third or so run on the default port, so it was looking a bit iffy capacity-wise.

Is there a way to check the number of HC assigned to a client?

There will be, but not yet.

My disk died this morning.

I am planning to recover the data and replace the disk in about 1 month (i.e. not satisfying 90% uptime in past 6 months).

Should my client be temporarily revoked, or letting it stop for 1 month is ok?

This post has been edited by ehaa: Oct 25 2023, 22:37

I am planning to recover the data and replace the disk in about 1 month (i.e. not satisfying 90% uptime in past 6 months).

Should my client be temporarily revoked, or letting it stop for 1 month is ok?

Clients aren't generally revoked for a single downtime, unless it lasts more than three months or the client has a history of being flaky.

The number of high-capacity ranges assigned to a client can now be found along with the readout for the number of priority ranges. (It no longer lists the number of P5 ranges explicitly, since that's just the number of assigned ranges that aren't P1-P4).

Since "hits" from HC ranges will generally be much larger files, there was also a minor tweak to the hath rate calculation. At the point the update was pushed, each hit was 417 KB on average, so the hath rate gain from traffic was changed from 0.15 * hits_per_minute to 0.15 * max(hits_per_minute, KB_per_minute / 420).

KB_per_minute

Would it be possible that we can have a readout on that? (Maybe in MB so the UI won't be stretched crazy wide)

Would it be possible that we can have a readout on that? (Maybe in MB so the UI won't be stretched crazy wide)

I'll consider it, but it might confuse more than enlighten since it's an estimated value rather than something fetched from the client. Basically it calculates the data transfer as the total transferred raw filesize of an estimated peak day, but disregards all protocol overhead, H@H-specific overhead like speed tests, and incoming data usage. It's close enough for backend estimate uses (it over-estimates by around 10% off on one particular test client), but I dunno about actually displaying it.

To fix an issue I noticed with a client that set a data transfer target after being assigned high-capacity ranges, there were some minor tweaks to this mechanism:

- You now have to explicitly check a box saying it's okay to remove HC ranges if you set a transfer limit or reduce the throttle below 10 MB/s. (No one reads these days.)

- If a client with HC ranges sets such limits, all HC ranges will be removed immediately and its traffic estimates will be reset. This prevents an issue where if you set a data transfer limit and the current traffic exceeded the set limit, it would (unnecessarily) start removing priority ranges instead.

CODE

2023-10-28T09:38:45Z [info] Finished applying settings
2023-10-28T09:38:45Z [info] CacheHandler: Attempting to load persistent cache data...
2023-10-28T09:38:45Z [info] CacheHandler: All persistent fields found, loading remaining objects
2023-10-28T09:38:45Z [info] CacheHandler: Loaded static range ages
2023-10-28T09:38:45Z [info] CacheHandler: Loaded LRU cache
2023-10-28T09:38:45Z [info] CacheHandler: Successfully loaded persistent cache data
2023-10-28T09:38:45Z [info] Requesting certificate from server...
2023-10-28T09:38:47Z [info] Starting up the internal HTTP Server...
2023-10-28T09:38:47Z [info] Internal HTTP Server was successfully started, and is listening on port 8886
2023-10-28T09:38:47Z [info] Notifying the server that we have finished starting up the client...
2023-10-28T09:38:51Z [info] {1/94.100.24.69}    Code=200 Bytes=36       GET /servercmd/still_alive//1698485931/1f2643124783fdaf253fbaccd074c6b
2023-10-28T09:38:51Z [info] {1/94.100.24.69}    Code=200 Bytes=36       Finished processing request in 0.00 seconds
2023-10-28T09:38:54Z [info] {3/94.100.24.69}    Code=200 Bytes=2500002  GET /servercmd/speed_test/testsize=2500002/1698485933/02ecd252a99f6f21
2023-10-28T09:38:55Z [info] {2/94.100.24.69}    Code=200 Bytes=2500001  GET /servercmd/speed_test/testsize=2500001/1698485933/ed2b5b15b37725f4
2023-10-28T09:41:01Z [info] {2/94.100.24.69}    Code=200 Bytes=2500001  Finished processing request in 126.06 seconds (19.83 KB/s)
2023-10-28T09:43:00Z [info] {3/94.100.24.69}    Code=200 Bytes=2500002  Finished processing request in 245.47 seconds (10.18 KB/s)
2023-10-28T09:43:52Z [WARN] Startup Failure: FAIL_INITIAL_SPEEDTEST:
2023-10-28T09:43:52Z [info] Startup notification failed.

(IMG:[invalid] style_emoticons/default/cry.gif)
My client was running fine on October 21nd.
Starting from October 22nd, my client has been reporting errors.
No matter what I try, he will report this error:FAIL_INITIAL_SPEEDTEST
My client has been running for a year,
I can guarantee that my upload and download speeds are up to standard.
And I found many netizens who had the same experience as me:
https://forums.e-hentai.org/index.php?showtopic=257252
Post #12953
Post #12967

This post has been edited by Mystery_Seeker: Oct 28 2023, 12:25

(IMG:[i.ibb.co] https://i.ibb.co/H76chK5/20231028062449.jpg)

Can't reconnect after stopping, haven't seen that before. Do you have any suggestions?

Looks like it just is really slow to the point where it times out. I've gone ahead and lowered the size of the speed test for CN clients, see if you can start it up now.

I was trying to check my log_out.old file to see how the speedtest went for me, but didn't see it (may be somewhere else).
But I saw this weird stuff:

CODE

2023-10-27T09:01:10Z [debug] {203286/109.237.98.53}   The connection was interrupted or closed by the remote host.
2023-10-27T09:01:10Z [debug] Unsupported or unrecognized SSL message
2023-10-27T09:01:10Z [debug] {203289/109.237.98.53}   The connection was interrupted or closed by the remote host.
2023-10-27T09:01:10Z [debug] Unsupported or unrecognized SSL message
2023-10-27T09:01:10Z [debug] {203288/109.237.98.53}   Invalid request type 'admin
2023-10-27T09:01:10Z [debug] Response Written:
2023-10-27T09:01:10Z [debug] An error has occurred. (404)
2023-10-27T09:01:10Z [info] {203288/109.237.98.53}   Code=404 Bytes=28       GET /admin/config.php HTTP/1.1
2023-10-27T09:01:10Z [info] {203288/109.237.98.53}   Code=404 Bytes=28       Finished processing request in 0,00 seconds
2023-10-27T09:01:11Z [debug] {203287/109.237.98.53}   The requested URL is invalid or not supported.
2023-10-27T09:01:11Z [debug] Response Written:
2023-10-27T09:01:11Z [debug] An error has occurred. (404)
2023-10-27T09:01:11Z [info] {203287/109.237.98.53}   Code=404 Bytes=28       GET / HTTP/1.1
2023-10-27T09:01:11Z [info] {203287/109.237.98.53}   Code=404 Bytes=28       Finished processing request in 0,00 seconds

Somebody trying to hack or something?

Somebody trying to hack or something?

Just a typical vuln scan, nothing to worry about

I was trying to check my log_out.old file to see how the speedtest went for me, but didn't see it (may be somewhere else).
But I saw this weird stuff:

CODE

bruh

Somebody trying to hack or something?

this is just some network security related thing like somebody want to blow up your frontend, and h@h itself had a tiny firewall system (so you can see it on logs), so nothing worried about.

Looks like it just is really slow to the point where it times out. I've gone ahead and lowered the size of the speed test for CN clients, see if you can start it up now.

It still doesn't work on my client, most Chinese home upload speed is only 30-50Mbps, maybe you can use it as a reference.

It still doesn't work on my client, most Chinese home upload speed is only 30-50Mbps, maybe you can use it as a reference.

Can't say what the problem is for your client specifically, but the current test should be completeable with dial-up modem speeds.

CODE

2023-10-29T00:05:36Z [info] Reading Hentai@Home client settings from server...
2023-10-29T00:05:44Z [info] Applying settings...
2023-10-29T00:05:44Z [info] Finished applying settings
2023-10-29T00:05:44Z [info] CacheHandler: Attempting to load persistent cache data...
2023-10-29T00:05:44Z [info] CacheHandler: All persistent fields found, loading remaining objects
2023-10-29T00:05:44Z [info] CacheHandler: Loaded static range ages
2023-10-29T00:05:44Z [info] CacheHandler: Loaded LRU cache
2023-10-29T00:05:44Z [info] CacheHandler: Successfully loaded persistent cache data
2023-10-29T00:05:44Z [info] Requesting certificate from server...
2023-10-29T00:05:45Z [info] Starting up the internal HTTP Server...
2023-10-29T00:05:45Z [info] Internal HTTP Server was successfully started, and is listening on port 8886
2023-10-29T00:05:45Z [info] Notifying the server that we have finished starting up the client...
2023-10-29T00:05:50Z [WARN] java.net.SocketTimeoutException: connect timed out
2023-10-29T00:05:50Z [WARN] Retrying.. (2 tries left)
2023-10-29T00:06:05Z [info] {1/94.100.24.69}    Code=200 Bytes=36       GET /servercmd/still_alive//1698537957/3076c53bfdc325962a7ab87246462da
2023-10-29T00:06:05Z [info] {1/94.100.24.69}    Code=200 Bytes=36       Finished processing request in 0.00 seconds
2023-10-29T00:06:14Z [WARN] Startup Failure: FAIL_INITIAL_SPEEDTEST:
2023-10-29T00:06:14Z [info] Startup notification failed.

CODE

2023-10-29T00:16:38Z [info] Reading Hentai@Home client settings from server...
2023-10-29T00:16:40Z [info] Applying settings...
2023-10-29T00:16:40Z [info] Finished applying settings
2023-10-29T00:16:40Z [info] CacheHandler: Attempting to load persistent cache data...
2023-10-29T00:16:40Z [info] CacheHandler: All persistent fields found, loading remaining objects
2023-10-29T00:16:41Z [info] CacheHandler: Loaded static range ages
2023-10-29T00:16:41Z [info] CacheHandler: Loaded LRU cache
2023-10-29T00:16:41Z [info] CacheHandler: Successfully loaded persistent cache data
2023-10-29T00:16:41Z [info] Requesting certificate from server...
2023-10-29T00:16:45Z [info] Starting up the internal HTTP Server...
2023-10-29T00:16:45Z [info] Internal HTTP Server was successfully started, and is listening on port 8886
2023-10-29T00:16:45Z [info] Notifying the server that we have finished starting up the client...
2023-10-29T00:16:56Z [info] {1/94.100.24.69}    Code=200 Bytes=36       GET /servercmd/still_alive//1698538613/53dc80993b9af776f5c3c1c985d2b28
2023-10-29T00:16:56Z [info] {1/94.100.24.69}    Code=200 Bytes=36       Finished processing request in 0.00 seconds
2023-10-29T00:17:05Z [info] {2/94.100.24.69}    Code=200 Bytes=50001    GET /servercmd/speed_test/testsize=50001/1698538622/9acd48d71a16c52789
2023-10-29T00:17:06Z [info] {2/94.100.24.69}    Code=200 Bytes=50001    Finished processing request in 0.53 seconds (93.63 KB/s)
2023-10-29T00:19:12Z [WARN] Startup Failure: FAIL_INITIAL_SPEEDTEST:
2023-10-29T00:19:12Z [info] Startup notification failed.

CODE

2023-10-29T00:41:06Z [info] Finished applying settings
2023-10-29T00:41:06Z [info] CacheHandler: Attempting to load persistent cache data...
2023-10-29T00:41:06Z [info] CacheHandler: All persistent fields found, loading remaining objects
2023-10-29T00:41:06Z [info] CacheHandler: Loaded static range ages
2023-10-29T00:41:06Z [info] CacheHandler: Loaded LRU cache
2023-10-29T00:41:06Z [info] CacheHandler: Successfully loaded persistent cache data
2023-10-29T00:41:06Z [info] Requesting certificate from server...
2023-10-29T00:41:07Z [info] Starting up the internal HTTP Server...
2023-10-29T00:41:07Z [info] Internal HTTP Server was successfully started, and is listening on port 8886
2023-10-29T00:41:07Z [info] Notifying the server that we have finished starting up the client...
2023-10-29T00:41:12Z [WARN] java.net.SocketTimeoutException: connect timed out
2023-10-29T00:41:12Z [WARN] Retrying.. (2 tries left)
2023-10-29T00:41:19Z [info] {1/94.100.24.67}    Code=200 Bytes=36       GET /servercmd/still_alive//1698540078/66bdf1e51979a7c0bd0a28fe31cc4b4
2023-10-29T00:41:19Z [info] {1/94.100.24.67}    Code=200 Bytes=36       Finished processing request in 0.00 seconds
2023-10-29T00:41:27Z [info] {2/94.100.24.67}    Code=200 Bytes=50002    GET /servercmd/speed_test/testsize=50002/1698540086/ea8ca0dd5fe97ad3b1
2023-10-29T00:41:28Z [info] {2/94.100.24.67}    Code=200 Bytes=50002    Finished processing request in 0.40 seconds (126.27 KB/s)
2023-10-29T00:46:22Z [WARN] Startup Failure: FAIL_INITIAL_SPEEDTEST:
2023-10-29T00:46:22Z [info] Startup notification failed.

It still doesn't work (IMG:[invalid] style_emoticons/default/cry.gif)



====================

After nearly 30 reboots, it started running

This post has been edited by Mystery_Seeker: Oct 29 2023, 03:05

After nearly 30 reboots, it started running

I've made some further tweaks to the initial speed test for China and, to some extent, the other distant regions where it's not all that relevant. Should be much easier to get it running now.

Added another improvement for high-capacity ranges:

- The system now supports high-capacity ranges on clients that set a monthly data limit, but will only assign them to clients that set it to at least 10 TB/month (10000 GB/month) and that are currently estimated to be using less than 50% of the set limit.

(If you reduce the limit to below 10 TB/month on a client that currently has high-capacity ranges assigned, they will be removed as before.)


Furthermore, clients that are located outside of their home region (country is highlighted in red) will no longer gain any hath. As it says on the H@H settings page, contact me if you need to change your home region or correct your currently detected country.

ohhhh good news (IMG:[invalid] style_emoticons/default/laugh.gif)