[X] My Assistant

Okay, so I've had my H@H server running on version 1.6.1 for the better part of four years uninterrupted. I realised a mandatory update dropped in December of last year, but I quite literally missed the memo till I decided to manually check if my client was running this evening. which directed me to come to the forums, and what do you know, there was the warning in my pm box that my server was offline, my question is, can I really not reapply for H@H as the warning says? i realise it was an oversight on my part but it really was a genuine error.

You can't reapply via the form if it was revoked, but send me a PM with your location/specs/speedtest and I'll look at it.

If this is the incorrect forum to post this, please tell me the best place to start.

This is the first H@H client I'm trying to configure, but I'm getting a connection error when I start H@H

The client host OS is Rocky Linux 9.5 with the latest version of java and no GUI installed.
For debugging, I'm using "java -Xms16m -Xmx512m -jar HentaiAtHome.jar" to start the client.

My Client ID and profile has been created, and the client has the Client Key entered. The log file seems to show that the client is successfully communicating with the server, downloading data and logging in. But it seems to fail at the last step.
It did connect to the H@H server long enough for the server to show it was online, but then it died.

This is my first post, and the system will not allow me to post any URLs, so I cannot post the log file in this. But if I can get some help, the system may allow me to post it in the next reply.

Suggestions please.

Suggestions please.

You'd need to at least post the lines of the log it fails on for a real answer, but usually that means you didn't forward the port correctly.

You'd need to at least post the lines of the log it fails on for a real answer, but usually that means you didn't forward the port correctly.

I tried again this morning right after I posted, and the server status pages shows the "last contact" was "Today, 19:35". The log shows several successful connections and data downloading

CODE

...
...
...2025-07-16T19:35:56Z [info] CacheHandler: Attempting to load persistent cache data...
2025-07-16T19:35:56Z [debug] CacheHandler: Loaded persistent cacheCount=0
2025-07-16T19:35:56Z [debug] CacheHandler: Loaded persistent cacheSize=0
2025-07-16T19:35:56Z [debug] CacheHandler: Loaded persistent lruClearPointer=0
2025-07-16T19:35:56Z [debug] CacheHandler: Found agesHash=e370291aec49ad8fb423ce671c56fc7d25340cc4
2025-07-16T19:35:56Z [debug] CacheHandler: Found lruHash=04637e367a3209261ba376c07c1458be7acc97b8
2025-07-16T19:35:56Z [info] CacheHandler: All persistent fields found, loading remaining objects
2025-07-16T19:35:56Z [info] CacheHandler: Loaded static range ages
2025-07-16T19:35:56Z [info] CacheHandler: Loaded LRU cache
2025-07-16T19:35:56Z [info] CacheHandler: Successfully loaded persistent cache data
2025-07-16T19:35:56Z [debug] CacheHandler: Checked cache space (cacheSize=0, cacheSizeWithOverhead=0 cacheLimit=107374182400, cacheFree=107374182400)
2025-07-16T19:35:56Z [debug] CacheHandler: Disk space constraints met (1965475917824 bytes free on device)
2025-07-16T19:35:56Z [info] Requesting certificate from server...
2025-07-16T19:35:56Z [debug] Selected rpcServerCurrent=212.7.200.99
2025-07-16T19:35:56Z [debug] Connecting to 212.7.200.99...
2025-07-16T19:35:56Z [debug] FileChannel for output opened
2025-07-16T19:35:56Z [debug] Reading 4318 bytes from http://212.7.200.99/15/rpc?clientbuild=176&act=get_cert&add=&cid=50730&acttime=1752694556&actkey=d0c4a7cfaf8bddf15f6671d06a53e58151b274df
2025-07-16T19:35:56Z [debug] Finished download for http://212.7.200.99/15/rpc?clientbuild=176&act=get_cert&add=&cid=50730&acttime=1752694556&actkey=d0c4a7cfaf8bddf15f6671d06a53e58151b274df in 1 ms, speed=4318KB/s, writeoff=4318, successful=yes
2025-07-16T19:35:56Z [debug] Initialized KeyStore with CN=*.hdwnlochbyud.hath.network
2025-07-16T19:35:56Z [debug] Current system time is Wed Jul 16 12:35:56 PDT 2025 (1752694556859)
2025-07-16T19:35:56Z [debug] Certificate expires on Thu Aug 28 01:07:18 PDT 2025 (1756368438000)
2025-07-16T19:35:56Z [debug] Initialized TrustManagerFactory with algorithm=PKIX
2025-07-16T19:35:56Z [debug] Initialized KeyManagerFactory with algorithm=SunX509
2025-07-16T19:35:56Z [info] Starting up the internal HTTP Server...
2025-07-16T19:35:56Z [debug] Initialized SSLContext with cert data/hathcert.p12 and protocol TLS
2025-07-16T19:35:56Z [debug] Supported ciphers: [TLS_AES_256_GCM_SHA384, TLS_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_RSA_WITH_AES_25
6_CBC_SHA256, TLS_DHE_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128
_CBC_SHA, TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_256_CBC_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_EMPTY_RENEGOTIATION_INFO_SCSV]
2025-07-16T19:35:56Z [debug] Enabled protocols: [TLSv1.3, TLSv1.2]
2025-07-16T19:35:56Z [info] Internal HTTP Server was successfully started, and is listening on port 50730
2025-07-16T19:35:56Z [info] Notifying the server that we have finished starting up the client...
2025-07-16T19:35:56Z [debug] Connecting to 212.7.200.99...
2025-07-16T19:35:58Z [debug] Reading 680 bytes from http://212.7.200.99/15/rpc?clientbuild=176&act=client_start&add=&cid=50730&acttime=1752694556&actkey=49f22a95a8249197df1abc26984948f684ccd034
2025-07-16T19:35:58Z [debug] Finished download for http://212.7.200.99/15/rpc?clientbuild=176&act=client_start&add=&cid=50730&acttime=1752694556&actkey=49f22a95a8249197df1abc26984948f684ccd034 in 0 ms, writeoff=680, successful=yes
2025-07-16T19:35:58Z [debug] Received response: FAIL_CONNECT_TEST:Failed to connect to gwnhsma.hdwnlochbyud.hath.network port 50730: Connection refused
2025-07-16T19:35:58Z [debug] There was even going to be a party for you. A big party that all your friends were invited to. I invited your best friend the companion cube. Of course, he couldn't come because you murdered him. All your other friends couldn't
come either because you don't have any other friends because of how unlikable you are. It says so here in your personnel file: Unlikable. Liked by no one. A bitter, unlikable loner whose passing shall not be mourned. SHALL. NOT. BE. MOURNED. That's exactly
what it says. Very formal. Very official. It also says you're adopted, so that's funny too.
2025-07-16T19:35:58Z [WARN] Startup Failure: FAIL_CONNECT_TEST:Failed to connect to gwnhsma.hdwnlochbyud.hath.network port 50730: Connection refused
2025-07-16T19:35:58Z [debug] ServerResponse {responseStatus=-1, responseText=, failCode=FAIL_CONNECT_TEST:Failed to connect to gwnhsma.hdwnlochbyud.hath.network port 50730: Connection refused}
2025-07-16T19:35:58Z [info]
2025-07-16T19:35:58Z [info] ************************************************************************************************************************************
2025-07-16T19:35:58Z [info] The client has failed the external connectivity test.
2025-07-16T19:35:58Z [info] The server could not connect to the client, which usually means it is not publicly reachable from the internet.

...
...

2025-07-16T19:35:58Z [WARN] Startup Failure: FAIL_CONNECT_TEST:Failed to connect to gwnhsma.hdwnlochbyud.hath.network port 50730: Connection refused

This means your client is not reachable from the internet, so you need to fix your port forwarding. The part of the error message between the asterisks tells you as much.

This means your client is not reachable from the internet, so you need to fix your port forwarding. The part of the error message between the asterisks tells you as much.

I see that, and I'll dig deeper.

But, I also see several successful connections before that last failure. I guess that's what's throwing me off.
I already have the Virtual Server set up and working for my email server on port 25 and a web server for letsencrypt cert renewal on port 443.
Port 50730 (UDP/TCP) is the 3rd and set up for hah.

But, I also see several successful connections before that last failure. I guess that's what's throwing me off.
I already have the Virtual Server set up and working for my email server on port 25 and a web server for letsencrypt cert renewal on port 443.
Port 50730 (UDP/TCP) is the 3rd and set up for hah.

You have successful outgoing connections, no incoming ones.

It's most likely a firewall on the local computer if the forwarding is correct.

You have successful outgoing connections, no incoming ones.

It's most likely a firewall on the local computer if the forwarding is correct.

100% my bad. Sorry for wasting the bandwidth
I didn't expose port 50730 in the compose.yaml file for the Rocky Linux container.
Duh. (IMG:[invalid] style_emoticons/default/blush.gif)

When the client is timeout, I can't edit its port. This makes it difficult to recover timed-out clients, as my client operates behind an ISP NAT, and the port changes every time it starts up.

When the client is timeout, I can't edit its port. This makes it difficult to recover timed-out clients, as my client operates behind an ISP NAT, and the port changes every time it starts up.

I guess it would help more than it hurts to unlock changing the port and stuff if the client is in the timeout state. So I did do that. But note that unless it's actually shut down when you change it, it will stop working until you restart it.

I guess it would help more than it hurts to unlock changing the port and stuff if the client is in the timeout state. So I did do that. But note that unless it's actually shut down when you change it, it will stop working until you restart it.

I developed a custom program to traverse NAT1, synchronize the external port to the configuration interface, and automatically restart the service upon port forwarding failure. While it operates reliably under normal conditions, Hath occasionally fails to terminate cleanly. This leaves the client in a persistent "timeout" state, preventing immediate restart for service recovery (as port modification is blocked). Is there any method—such as an API endpoint—to manually force the client status to "offline"? This would enable my program to automatically reconfigure ports and restart the client without delay.

I developed a custom program to traverse NAT1, synchronize the external port to the configuration interface, and automatically restart the service upon port forwarding failure. While it operates reliably under normal conditions, Hath occasionally fails to terminate cleanly. This leaves the client in a persistent "timeout" state, preventing immediate restart for service recovery (as port modification is blocked). Is there any method—such as an API endpoint—to manually force the client status to "offline"? This would enable my program to automatically reconfigure ports and restart the client without delay.

If it wasn't clear, you should be able to change the port when it goes to the "Timeout" state now. Let me know if it doesn't work.

Is there a service interruption on H@H network? Seems like everyone is having a big drop on H@H toplist, or the measurement is changed. I got two of my client went timeout and have to manually reset.

Is there a service interruption on H@H network? Seems like everyone is having a big drop on H@H toplist, or the measurement is changed. I got two of my client went timeout and have to manually reset.

Nothing on our end, but there was a big drop in China traffic yesterday, which happens from time to time, probably when they mess with the firewall. Seems to be recovering today, though.

If it wasn't clear, you should be able to change the port when it goes to the "Timeout" state now. Let me know if it doesn't work.

Thank you for the adjustment.

So I applied for Hentai@Home last night and got approved and am just now starting it up. Where do I find the Client Key?

-Edit: Never mind, I figured it out

This post has been edited by gamer55567: Jul 22 2025, 00:35

Thanks for your hard work

How come I'm getting so little traffic?
I've allocated 20MB/s and 160GB storage space with 1000 Trust and 10000 Quality running 24/7, and my hitrate is barely hitting 9 per min, well actually less than 9.
I remember back when I was running Hentai@Home like maybe 7, 8 years ago? I was getting much more hit with significantly less everything.

This post has been edited by mm223456789: Jul 30 2025, 08:32

How come I'm getting so little traffic?
I've allocated 20MB/s and 160GB storage space with 1000 Trust and 10000 Quality running 24/7, and my hitrate is barely hitting 9 per min, well actually less than 9.
I remember back when I was running Hentai@Home like maybe 7, 8 years ago? I was getting much more hit with significantly less everything.

It's only been running for two weeks, for one.

It's only been running for two weeks, for one.

Fair, yeah. I guess it takes more time now.
Also, I was reading through wiki and forum as well as online source. Some online source says to not use 443 for port but official wiki and forum says to use it. Why is that? 443 is still better overall, right?