[X] My Assistant

Hello,

I am trying to set up another server on my China Unicom connection, encountering some funny problems here. I can ping rpc.hentaiathome.net and traceroute but I can't curl or open the page in a browser with my China Unicom connection. China Telecom seems fine. So the problem seems to be China Unicom blocked hentaiathome.net's 80 port..?
Anyone have any idea how to potentially bypass this? I do have another China Telecom line available to be (still need to ask for public IP,) guess I might have to use that instead if I can't bypass this.

Some logs: (notice the 502 errors are instantly returned, same as when I curl)

CODE

2023-01-15T17:42:11Z Logging started
2023-01-15T17:42:11Z [info] Hentai@Home 1.6.1 (Build 154) starting up
2023-01-15T17:42:11Z [info] Copyright (c) 2008-2020, E-Hentai.org - all rights reserved.
2023-01-15T17:42:11Z [info] This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL v3 license.
2023-01-15T17:42:11Z [info] Before you can use this client, you will have to register it at http://hentaiathome.net/
2023-01-15T17:42:11Z [info] IMPORTANT: YOU NEED A SEPARATE IDENT FOR EACH CLIENT YOU WANT TO RUN.
2023-01-15T17:42:11Z [info] DO NOT ENTER AN IDENT THAT WAS ASSIGNED FOR A DIFFERENT CLIENT UNLESS IT HAS BEEN RETIRED.
2023-01-15T17:42:11Z [info] After registering, enter your ID and Key below to start your client.
2023-01-15T17:42:11Z [info] (You will only have to do this once.)
2023-01-15T17:42:23Z [info] Connecting to the Hentai@Home Server to register client with ID 44582...
2023-01-15T17:42:23Z [debug] Connecting to rpc.hentaiathome.net...
2023-01-15T17:42:24Z [WARN] java.io.IOException: Server returned HTTP response code: 502 for URL: http://rpc.hentaiathome.net/15/rpc?clientbuild=154&act=server_stat
2023-01-15T17:42:24Z [WARN] Retrying.. (2 tries left)
2023-01-15T17:42:24Z [debug] Connecting to rpc.hentaiathome.net...
2023-01-15T17:42:24Z [WARN] java.io.IOException: Server returned HTTP response code: 502 for URL: http://rpc.hentaiathome.net/15/rpc?clientbuild=154&act=server_stat
2023-01-15T17:42:24Z [WARN] Retrying.. (1 tries left)
2023-01-15T17:42:24Z [debug] Connecting to rpc.hentaiathome.net...
2023-01-15T17:42:24Z [WARN] java.io.IOException: Server returned HTTP response code: 502 for URL: http://rpc.hentaiathome.net/15/rpc?clientbuild=154&act=server_stat
2023-01-15T17:42:24Z [WARN] Retrying.. (0 tries left)
2023-01-15T17:42:24Z [WARN] Exhaused retries or aborted getting http://rpc.hentaiathome.net/15/rpc?clientbuild=154&act=server_stat
2023-01-15T17:42:24Z [ERROR] {hath.base.HentaiAtHomeClient.dieWithError(HentaiAtHomeClient.java:373)} Critical Error: Failed to get initial stat from server.
2023-01-15T17:42:24Z [info] Shutting down...
2023-01-15T17:42:24Z [info] Good-night
2023-01-15T17:42:32Z [info] Logging ended.

CODE

curl -v http://rpc.hentaiathome.net/15/rpc\?clientbuild\=154\&act\=server_stat
*   Trying 94.100.24.67...
* TCP_NODELAY set
* Connected to rpc.hentaiathome.net (94.100.24.67) port 80 (#0)
> GET /15/rpc?clientbuild=154&act=server_stat HTTP/1.1
> Host: rpc.hentaiathome.net
> User-Agent: curl/7.64.1
> Accept: */*
>
* Recv failure: Connection reset by peer
* Closing connection 0
curl: (56) Recv failure: Connection reset by peer

CODE

traceroute rpc.hentaiathome.net
traceroute: Warning: rpc.hentaiathome.net has multiple addresses; using 94.100.24.67
traceroute to hentaiathome.net (94.100.24.67), 64 hops max, 52 byte packets
1  192.168.1.1 (192.168.1.1)  1.912 ms  0.346 ms  0.428 ms
2  temp.fj133165.com (220.250.xx.xxx)  7.219 ms  2.898 ms  3.147 ms
3  220.249.xx.xx (220.249.xx.xx)  2.524 ms  2.029 ms
    220.249.xx.xx (220.249.xx.xx)  3.560 ms
4  218.104.xx.xx (218.104.xx.xx)  7.118 ms
    58.22.xx.xx (58.22.xx.xx)  19.955 ms
    218.104.xx.xx (218.104.xx.xx)  39.276 ms
5  * 219.158.18.149 (219.158.18.149)  21.081 ms
    219.158.106.37 (219.158.106.37)  23.944 ms
6  219.158.7.130 (219.158.7.130)  36.105 ms
    219.158.8.202 (219.158.8.202)  34.434 ms
    219.158.7.130 (219.158.7.130)  34.799 ms
7  219.158.6.210 (219.158.6.210)  25.295 ms  31.275 ms  24.393 ms
8  219.158.102.110 (219.158.102.110)  173.449 ms  161.380 ms  163.894 ms
9  xe-3-1-3.cr2-sjc1.ip4.gtt.net (173.205.56.141)  174.330 ms  159.168 ms  163.768 ms
10  ae18.cr3-ams1.ip4.gtt.net (213.200.117.218)  239.904 ms  226.589 ms  231.167 ms
11  ip4.gtt.net (92.60.243.54)  232.371 ms  232.441 ms  232.345 ms
12  * * *
13  * * *
14  * * *
15  94-100-24-67.static.hvvc.us (94.100.24.67)  227.932 ms  232.124 ms  241.000 ms

EDIT: seems only port 80 on rpc.hentaiathome.net is blocked, if I replace it with IP address it works fine in browser and curl.
Fiddled with it a bit more, I can telnet rpc's port 80, will connect, so it's only HTTP requests to rpc that's dropped instantly, port 80 itself isn't blocked. HTTP to IP address is fine

EDIT 2: I have found a solution although it's a bit hacky. But nothing last as long as a temp solution that works!
Step 1: download the source code of H@H
Step 2: download sqlite-jdbc-3.7.2.jar file and put it in the source code's src folder
Step 3: go to src/hath/base/Settings.java, change
public static final String CLIENT_RPC_HOST = "rpc.hentaiathome.net";
to any of the 3 IP addresses
Step 4: make
Step 5: make jar
(those wouldn't run on my RPI so I actually just did bash make.sh and bash makejar.sh)
Step 6: use the newly generated HentaiAtHome.jar file (or the GUI one) in the build folder

This post has been edited by Based Brandon: Jan 16 2023, 10:35

Thx! Followed the steps and ran successfully

It only uses the domain if it doesn't have the IP of a server, and you can provide that manually with say --rpc-server-ip=94.100.24.67 so you don't actually need to modify and rebuild it.