disappear9 / h-at-h-docker

Dockerfile of Hentai@Home (arm,x64,x86)

👋 Hi, I’m @Disappear9

Some of my codes have been moved to the D9Lab.

Contact:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

EMail: [email protected]
Key ID: 0x584DAE801883FC3A
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQRyZK4Ai4+Ap9ZBGCeFSeTQSPkChQUCZauPPwAKCRCFSeTQSPkC
hfvqAQCClISkbXoUh3CBStzcQeKyxSl3Oa+DWgqzlyoRz7kUHQEAgdIrk5+xdmj2
92AK34O455pJQFP7LrrTw+FoRwTgIQ0=
=2Kmq
-----END PGP SIGNATURE-----

In Game:

Steam: https://steamcommunity.com/id/Disappear9
BeatSaber: https://scoresaber.com/u/76561198168503842
OSU: https://osu.ppy.sh/users/7187903

h-at-h-docker's Issues

Add docker-compose to documentation

Here's an example one. I'm not sure whether this compose file will work since I don't have an H@H client key yet to test with.

version: '3'

services:
  h_at_h:
    image: ghcr.io/disappear9/hentaiathome:latest
    volumes:
      - h_at_h_data:/hath/data
      - /LOCAL_DOWNLOAD_FOLDER:/hath/download
    ports:
      - YOUR_PORT:YOUR_PORT
    restart: unless-stopped
    environment:
      - HatH_KEY=YOUR_CLIENT_ID-YOUR_CLIENT_KEY

volumes:
  h_at_h_data:

Problems with startup after running for weeks fine

Hello there,
Recently, my instance of HatH went offline and I can't seem to get it up running again.

To give some context, the docker container is running on a Debian VM which is running on a dedicated proxmox server. Port forwarding from the host to the VM works completely fine, but it still seems to have some weird issues now -.-

Port forwarding is the same as always and hasn't changed. What I'm a bit confused is the IP log entry. Should it have this `::ffff: stuff in front of the public ipv4?
Also, the custom domain for the hath.network domain which is in the logs, actually resolves to the public IP of my server, so that "mapping" also is correct.

Thanks for the help^^

Startup logs:

hentaiathome-hentaiAtHome-1  | 2022-10-20T19:53:58Z [info] Hentai@Home 1.6.1 (Build 154) starting up
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:53:58Z [info] Copyright (c) 2008-2020, E-Hentai.org - all rights reserved.
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:53:58Z [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.
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:53:58Z [info] Loaded login settings from client_login
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:53:58Z [info] Connecting to the Hentai@Home Server to register client with ID 43359...
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:53:58Z [info] Reading Hentai@Home client settings from server...
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:53:58Z [info] Applying settings...
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:53:58Z [info] Finished applying settings
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:53:58Z [info] CacheHandler: Initializing the cache system...
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:53:58Z [info] CacheHandler: Cache cleanup pass..
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:53:58Z [info] CacheHandler: Finished scanning 0 cache subdirectories
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:53:58Z [info] CacheHandler: Loading cache...
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:53:58Z [info] CacheHandler: Finished initializing the cache (0 files, 0 apparent bytes, 0 estimated bytes on disk)
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:53:58Z [info] CacheHandler: Found a total of 0 static ranges with files
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:53:58Z [info] Requesting certificate from server...
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:53:58Z [info] Starting up the internal HTTP Server...
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:53:58Z [info] Internal HTTP Server was successfully started, and is listening on port 36900
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:53:58Z [info] Notifying the server that we have finished starting up the client...
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:54:00Z [WARN] Rejecting connection request from 172.16.0.1 during startup.
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:54:00Z [WARN] Startup Failure: FAIL_CONNECT_TEST:OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to XXXX.XXXX.hath.network:36900  
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:54:00Z [info]
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:54:00Z [info] ************************************************************************************************************************************
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:54:00Z [info] The client has failed the external connection test.
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:54:00Z [info] The server failed to verify that this client is online and available from the Internet.
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:54:00Z [info] If you are behind a firewall, please check that port 36900 is forwarded to this computer.
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:54:00Z [info] You might also want to check that ::ffff:XXXXXXXXXX is your actual public IP address.
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:54:00Z [info] If you need assistance with forwarding a port to this client, locate a guide for your particular router at http://portforward.com/  
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:54:00Z [info] The client will remain running so you can run port connection tests.
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:54:00Z [info] Use Program -> Exit in windowed mode or hit Ctrl+C in console mode to exit the program.
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:54:00Z [info] ************************************************************************************************************************************
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:54:00Z [info]
hentaiathome-hentaiAtHome-1  | 2022-10-20T19:54:00Z [info] Startup notification failed.

Enter Client ID: Interrupted

emmm,我试了挺多机器都是这样,不知道是什么原因..

2020-08-26T12:22:52Z [info] Hentai@Home 1.6.1 (Build 154) starting up
2020-08-26T12:22:52Z [info] Copyright (c) 2008-2020, E-Hentai.org - all rights reserved.
2020-08-26T12:22:52Z [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.
2020-08-26T12:22:52Z [info] Before you can use this client, you will have to register it at http://hentaiathome.net/
2020-08-26T12:22:52Z [info] IMPORTANT: YOU NEED A SEPARATE IDENT FOR EACH CLIENT YOU WANT TO RUN.
2020-08-26T12:22:52Z [info] DO NOT ENTER AN IDENT THAT WAS ASSIGNED FOR A DIFFERENT CLIENT UNLESS IT HAS BEEN RETIRED.
2020-08-26T12:22:52Z [info] After registering, enter your ID and Key below to start your client.
2020-08-26T12:22:52Z [info] (You will only have to do this once.)
Enter Client ID: Interrupted
2020-08-26T12:22:52Z [info] Shutting down...
2020-08-26T12:22:52Z [info] No hard feelings
2020-08-26T12:22:52Z [info] Logging ended.

It doesn't seem to be working as expected

here's the log

2023-04-29T18:39:05Z Logging started
2023-04-29T18:39:05Z [info] Hentai@Home 1.6.1 (Build 154) starting up
2023-04-29T18:39:05Z [info] Copyright (c) 2008-2020, E-Hentai.org - all rights reserved.
2023-04-29T18:39:05Z [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-04-29T18:39:05Z [info] Before you can use this client, you will have to register it at http://hentaiathome.net/
2023-04-29T18:39:05Z [info] IMPORTANT: YOU NEED A SEPARATE IDENT FOR EACH CLIENT YOU WANT TO RUN.
2023-04-29T18:39:05Z [info] DO NOT ENTER AN IDENT THAT WAS ASSIGNED FOR A DIFFERENT CLIENT UNLESS IT HAS BEEN RETIRED.
2023-04-29T18:39:05Z [info] After registering, enter your ID and Key below to start your client.
2023-04-29T18:39:05Z [info] (You will only have to do this once.)
2023-04-29T18:39:05Z [info] Shutting down...
2023-04-29T18:39:05Z [info] Whyyyyyyyy...
2023-04-29T18:39:05Z [info] Logging ended.

/hath/start.sh: 5: killall: not found问题

在unraid docker中使用，下载[email protected]在添加容器时选择此模版，第一次选了shell 并 关闭特权，运行正常。
直到在unraid docker标签页点停止容器，日志提示/hath/start.sh: 5: killall: not found，容器照常运行 直到docker超时强制关闭。e站hath面板最终也显示服务器timeout。

试过shell改bash，开关特权，都一样not found。

对了unraid新版移除了Template Repositories：
https://forums.unraid.net/topic/112170-allow-template-repositories-to-be-hosted-from-other-sources/#comment-1021630

Beginning with Unraid 6.10.0-rc1, the entire Template Repositories section has been removed (Thanks be to JoBu)

2 Choices:

save the xml's within /config/plugins/dockerMan/templates-user on the flash drive and use the Add Container Button
save the xml's within /config/plugins/community.applications/private/LTM on the flash drive and use CA to manage them (If not categorized, they will appear within the Private Category)

unraid版本: 6.10.3
Docker 版本: 20.10.14

image gone from docker hub

Was this project abandoned or retired? https://hub.docker.com/r/disappear9/hentaiathome returns 404 now, and it's impossible to pull the image:

Error response from daemon: pull access denied for disappear9/hentaiathome, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

Entering ID Interrupted

Hey, trying to get a docker container setup with your template but struggling to get it to work.

When it should be passing the variable, it seems to be interupted by something else, like so

2020-08-01T21:01:42Z [info] Hentai@Home 1.6.0 (Build 151) starting up
2020-08-01T21:01:42Z [info] Copyright (c) 2008-2019, E-Hentai.org - all rights reserved.
2020-08-01T21:01:42Z [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.
2020-08-01T21:01:42Z [info] Before you can use this client, you will have to register it at http://hentaiathome.net/
2020-08-01T21:01:42Z [info] IMPORTANT: YOU NEED A SEPARATE IDENT FOR EACH CLIENT YOU WANT TO RUN.
2020-08-01T21:01:42Z [info] DO NOT ENTER AN IDENT THAT WAS ASSIGNED FOR A DIFFERENT CLIENT UNLESS IT HAS BEEN RETIRED.
2020-08-01T21:01:42Z [info] After registering, enter your ID and Key below to start your client.
2020-08-01T21:01:42Z [info] (You will only have to do this once.)
Enter Client ID: Interrupted2020-08-01T21:01:42Z [info] Shutting down...
2020-08-01T21:01:42Z [info] No hard feelings
2020-08-01T21:01:42Z [info] Logging ended.

I'm using port 80 and mapping to 7000 on local host, ID and code are using 12345-ascAFZDCVqas123 format, 2 paths are /h_at_home to local appdata and /download dir set to desired path with r/w right

I'm using Unraid docker for this container.
Any thoughts?

Add notes to the ReadME

Compared to these repos, what makes this docker special?

• https://github.com/Yukariin/hath (C++)
• https://github.com/Mizore/hath (C#)
• https://github.com/tioover/hath (just a docker file)

it can not work, always show the error ip?

It show

2020-06-29T08:57:48Z [info] The client has failed the external connection test.
2020-06-29T08:57:48Z [info] The server failed to verify that this client is online and available from the Internet.
2020-06-29T08:57:48Z [info] If you are behind a firewall, please check that port 33445 is forwarded to this computer.
2020-06-29T08:57:48Z [info] You might also want to check that ::ffff:203.69.229.94 is your actual public IP address.
2020-06-29T08:57:48Z [info] If you need assistance with forwarding a port to this client, locate a guide for your particular router at http:
//portforward.com/
2020-06-29T08:57:48Z [info] The client will remain running so you can run port connection tests.
2020-06-29T08:57:48Z [info] Use Program -> Exit in windowed mode or hit Ctrl+C in console mode to exit the program.
2020-06-29T08:57:48Z [info] ****************************************************************************************************************

---

2020-06-29T08:57:48Z [info]
2020-06-29T08:57:48Z [info] Startup notification failed.

but my qnap's public ip is 140.130.xx.xx and i setup the container network as host, why it always get 203.69.229.xxx?
how to slove the problem?

Enter Client ID: Interrupted

It's similar with #1

2020-07-15T05:48:25Z [info] Hentai@Home 1.6.0 (Build 151) starting up
2020-07-15T05:48:25Z [info] Copyright (c) 2008-2019, E-Hentai.org - all rights reserved.
2020-07-15T05:48:25Z [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.
2020-07-15T05:48:25Z [info] Before you can use this client, you will have to register it at http://hentaiathome.net/
2020-07-15T05:48:25Z [info] IMPORTANT: YOU NEED A SEPARATE IDENT FOR EACH CLIENT YOU WANT TO RUN.
2020-07-15T05:48:25Z [info] DO NOT ENTER AN IDENT THAT WAS ASSIGNED FOR A DIFFERENT CLIENT UNLESS IT HAS BEEN RETIRED.
2020-07-15T05:48:25Z [info] After registering, enter your ID and Key below to start your client.
2020-07-15T05:48:25Z [info] (You will only have to do this once.)
Enter Client ID: Interrupted2020-07-15T05:48:25Z [info] Shutting down...
2020-07-15T05:48:25Z [info] I don't hate you
2020-07-15T05:48:25Z [info] Logging ended.

My command

docker run -d --name='HentaiAtHome' --net='br1' --ip='192.168.1.7' -e TZ="Asia/Shanghai" -e HOST_OS="Unraid" -e 'HatH_KEY'='3**73-ruhkq****TGRf' -v '/mnt/user/appdata/HentaiAtHome/':'/hath/data':'rw' -v '/mnt/user/library/Downloads/HentaiAtHome/':'/hath/download':'rw' 'disappear9/hentaiathome'

HAH has updated.

HAH is now (as of writing) at version 1.6.0. An update to the docker image would be appreciated.

Cannot start container after resetting client key

It appears that /hath/data/data/client_login takes precedence than $HatH_KEY, and if key was reset the old key will be used and cause login failure even if you enter the new key in docker run command. At this point the container would just stop.

Maybe make $HatH_KEY take precedence or delete client_login after login failure?

Graceful shutdown

Since docker stop only sends SIGTERM to the main process, in this case the start.sh, the actual java client never receives a signal before forcefully killed. As a result it was not able to notify the server it's going offline, creating trust/quality issues.

Here is what worked for me in bash, should work in sh as well? Replace rm -rf "$tmpdir" with killall java.

trap 'rm -rf "$tmpdir"' INT TERM EXIT;
wait

Use github actions for dockerfile build

😉

Can't get it running.

Docker gives this error

2019-07-08T14:37:32Z [info] Hentai@Home 1.4.2 (Build 134) starting up 2019-07-08T14:37:32Z [info] Copyright (c) 2008-2017, E-Hentai.org - all rights reserved. 2019-07-08T14:37:32Z [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. 2019-07-08T14:37:32Z [info] Loaded login settings from client_login 2019-07-08T14:37:32Z [info] Before you can use this client, you will have to register it at http://hentaiathome.net/ 2019-07-08T14:37:32Z [info] IMPORTANT: YOU NEED A SEPARATE IDENT FOR EACH CLIENT YOU WANT TO RUN. 2019-07-08T14:37:32Z [info] DO NOT ENTER AN IDENT THAT WAS ASSIGNED FOR A DIFFERENT CLIENT UNLESS IT HAS BEEN RETIRED. 2019-07-08T14:37:32Z [info] After registering, enter your ID and Key below to start your client. 2019-07-08T14:37:32Z [info] (You will only have to do this once.) Enter Client ID: Interrupted2019-07-08T14:37:32Z [info] Shutting down... 2019-07-08T14:37:32Z [info] Your business is appreciated 2019-07-08T14:37:32Z [info] Logging ended.

Ran this command to start it

sudo docker run -d --name h_at_h -p 11112:11112 -v h_at_h_data:/hath/data -v /sharedfolders/Docker/HH:/hath/download -e HatH_KEY=36698-GVuf8t55555555azeG disappear9/hentaiathome

At all possible to get this to run on Unraid?

I know you kinda scratched out the Unraid section, just wondering if there is an unofficial way of getting this to run on Unraid?

There is insufficient memory for the Java Runtime Environment to continue.

Recently started getting an error with the hath image. Tracked it down to a change made to the base java image used in creating this container when the Eclipse team migrated to the newest Ubuntu version. Backing off to the 'focal' version seemed to fix the problem.

Pull request here.

#15