[X] My Assistant

Now that EU region is over saturated. I'm thinking about moving some of the clients in that region to the US. Will I lose my P1 range if I do so?

This post has been edited by ddvd: Dec 4 2024, 00:30

Now that EU region is over saturated. I'm thinking about moving some of the clients in that region to the US. Will I lose my P1 range if I do so?

Range priority is only reset if clients are moved from a secondary region (Oceania, South America or Africa) to a primary one, so EU -> NA would keep them.

Any way to get HatH to run on two different computers on the network? I've got the server running headless in a terminal - no desktop environment or GUI - on an old linux machine, and I'd like to make some use of the downloading on my windows machine, but trying to run it in windows just gave an error about static ranges and exited. I would much rather not have two servers running, and my windows machine isn't stable enough or have enough ram to consistently run a server on it, not while I'm actually using it.

Any way to get HatH to run on two different computers on the network? I've got the server running headless in a terminal - no desktop environment or GUI - on an old linux machine, and I'd like to make some use of the downloading on my windows machine, but trying to run it in windows just gave an error about static ranges and exited. I would much rather not have two servers running, and my windows machine isn't stable enough or have enough ram to consistently run a server on it, not while I'm actually using it.

You need a unique IP address per client, for technical reasons.

Since the old static ranges are for all intents and purposes done away with now is there any plans for a mechanism to prune them and only keep the new/actually used ranges? I imagine I can't be the only one that had their storage filled nearly to the brim from maxing out on the old ranges.

This post has been edited by Scumbini: Dec 7 2024, 09:38

Since the old static ranges are for all intents and purposes done away with now is there any plans for a mechanism to prune them and only keep the new/actually used ranges? I imagine I can't be the only one that had their storage filled nearly to the brim from maxing out on the old ranges.

They have been pruned internally. To prune them from the client's cache, you can either do a manual rescan (startup with --rescan-cache or delete the pcache files from the data directory), or download the 1.6.4 pre-release which will do it automatically.

Though this is only really necessary if your cache still has files from September 2023 or earlier, newer caches shouldn't have any files in the old P5 ranges.

Glad to hear it, much obliged.

My max speed has been dropping from 15000KB/s all the way down to 2517KB/s over the last month. and I've noticed that from time to time the speed drops to 0KB/s when I look at the visualization server, which is strange because the server is at my house and I'm using the internet that whole time and I don't notice any disconnections.
I've noticed that every time I'm down for maintenance and restart h@h, the max speed drops, while my server measured a max upload speed of 300Mbps/s when running speedtest
This should have nothing to do with my max upload speed


Also, I've noticed that the Code=502 I mentioned last time causes a backlog of requests, what used to be an average time period of 80 Connections is now backed up to 200+.

This is strange, maybe my ISP is playing me. (In China, the big 3 ISPs have a virtual monopoly on public IPs, and users have no bargaining power)

what is this app even doing? is this a crypto miner or what ?

what is this app even doing? is this a crypto miner or what ?

If you look closely at the opening post, there's an FAQ link which should answer basic questions about H@H:

For information on how to join Hentai@Home, check out The Hentai@Home Project FAQ.

My max speed has been dropping from 15000KB/s all the way down to 2517KB/s over the last month. and I've noticed that from time to time the speed drops to 0KB/s when I look at the visualization server, which is strange because the server is at my house and I'm using the internet that whole time and I don't notice any disconnections.
I've noticed that every time I'm down for maintenance and restart h@h, the max speed drops, while my server measured a max upload speed of 300Mbps/s when running speedtest
This should have nothing to do with my max upload speed
Also, I've noticed that the Code=502 I mentioned last time causes a backlog of requests, what used to be an average time period of 80 Connections is now backed up to 200+.

Your client does seem to be overloading a lot. You could look into using the --image-proxy options that were added in 1.6.3, from what you're saying it sounds like it's just stalling when downloading images from upstream servers. But you would need access to a proxy of some sort to use that.

Your client does seem to be overloading a lot. You could look into using the --image-proxy options that were added in 1.6.3, from what you're saying it sounds like it's just stalling when downloading images from upstream servers. But you would need access to a proxy of some sort to use that.

It's a tragedy that I didn't purchase an agent that could be online 24/7

As previously announced, clients older than 1.6.2 have now been booted due to lack of WebP support. So if you didn't restart your client the last two months and ignored the multiple warnings about needing to update, your client now no longer works, and you have to update it in order to get it working again.

I noticed that H@H is still set to only support TLS1.2.
TLS1.3 has significantly improved handshake speed and support for middlebox is no longer a problem.
Is it possible to consider enabling TLS1.3 in the new version of the client?

I noticed that H@H is still set to only support TLS1.2.
TLS1.3 has significantly improved handshake speed and support for middlebox is no longer a problem.
Is it possible to consider enabling TLS1.3 in the new version of the client?

It was disabled for compatibility reasons (1.3 had twice the failure rate of 1.2), but I suppose it's been long enough that most old broken firewalls have been replaced or updated at this point, so I guess we could try re-enabling it and see if the failure rate changes.

delete not in static range dir

wow my hard drive space is clearing rapidly
I can mass now mass download blurays for christmas

I pushed some significant changes to how static ranges are assigned. This basically gets rid of the last parts of the legacy assignment mechanism where clients are assigned ranges that aren't actually being used (P5), which are later promoted to "active" (P1-P3) ranges.

Instead, active ranges are now assigned directly, which means that all ranges added to clients from now on will be P1-P3. (P2-P4 ranges can still be promoted, of course.)

Does this mean that P4 ranges should no longer be assigned? I have a relatively new client and was just assigned a single P4 range.

Does this mean that P4 ranges should no longer be assigned? I have a relatively new client and was just assigned a single P4 range.

You can still end up with P4 ranges, but P4 ranges aren't directly assigned as such. In most cases, unless your client had some extended downtime, it just means your client was assigned a higher-priority range, which was then demoted since the client that had that range priority originally came back online.

Due to a quirk with how high-capacity ranges are stored, it also can't assign you *just* a HC range, since all ranges need to have a priority. So if it wants to assign your client a HC range for a range it doesn't already have, it will add it as a P4 + HC range. (The way this is stored might be changed at some point, but there aren't really any practical downsides in doing this.)

Today I finished the movement of the cache files.

When I start the client, I find that there are a lot of debug message.
Time [debug] CacheHandler: The file file_path was not in an active static range.


Is that normal in current version?

Today I finished the movement of the cache files.

When I start the client, I find that there are a lot of debug message.
Time [debug] CacheHandler: The file file_path was not in an active static range.
Is that normal in current version?

That's expected if you have an old cache from before September 2023.