[X] My Assistant

Debian 8 comes with systemd, I'm not sure if initd still works

It does, they basically created a systemd service that runs the initd scripts (IMG:[invalid] style_emoticons/default/smile.gif)

On the other hand am not sure if the update-rd.d script works on Debian 8. Or better, not sure if it comes with it by default as it did on earlier ones.

so the "proxy local" for client don't work any more thats why i cannot get it?

thats why i cannot get it?

What you cannot get?

sorry bad phrasing "get it to work" get to local proxy to work so i can load images trough the client ^^

Hi, a little question !

I cant update Java on the OS.. where my Client is running.. any reason to try updating H@H from 1.2.6 to 1.4.1 ?
Or is shutting it down.. the best option ?

You don't need to update java.

You don't need to update java.

Sure you do. 1.2 line could run with Java 6. For 1.3 and 1.4 line, Java 7 is required.

6 hasn't been supported for ages.

"Hentai@Home Local Network Host" option does not work for me anymore.
(It stopped working with h@h 1.4.0 AFAIR)

I'm using address 10.10.0.1:12345 in this field which is computer on my LAN*, but when browsing g.e-hentai or g.e-hentai site I got images from another IPs, not from 10.10.0.1.


[*] Actually it is not, it's VPS IP, that connected using OpenVPN.

"Local Network Host" is not the same as the old proxy setting, which was retired about.. three months ago?

"Local Network Host" is not the same as the old proxy setting, which was retired about.. three months ago?

I don't remember about old setting...
So "Local Network Host" feature does not inspect gallery browser to request all images from this IP:PORT?
If not, how this feature actually works?

If not, how this feature actually works?

Ekhmm, well

was retired

Ekhmm, well

I'm talking about "Hentai@Home Local Network Host" which is not retired and available on the settings page.

Oh OK, sorry. That setting is only left to deal with buggy routers. i.e. when you have problems in accessing images on your own H@H client through the public IP.

EH knows that your H@H is yours thank to the fact that both of you have the same public IP.

Oh OK, sorry. That setting is only left to deal with buggy routers. i.e. when you have problems in accessing images on your own H@H client through the public IP.

EH knows that your H@H is yours thank to the fact that both of you have the same public IP.

so the feature no longer in use?

so the feature no longer in use?

Which one?

proxy - retired.

local IP insetting - still present to allow for buggy routers (does not use proxy).

Hi, a little question !

I cant update Java on the OS.. where my Client is running.. any reason to try updating H@H from 1.2.6 to 1.4.1 ?
Or is shutting it down.. the best option ?

Frankly, nowadays you should be running Java 8 on a host, period.

H@H seems to be very slow since update. It takes forever to load gallery images with the new H@H 1.4.1. Image download just stalls.

2017-02-04T07:36:01Z [info] {175/70.55.76.130} Code=200 Bytes=173396 GET /h/a186246ab68e2bcc0cfebb875b710b0148fa7bb4-173396-1280-720-jpg/
2017-02-04T07:36:01Z [info] {175/70.55.76.130} Code=200 Bytes=173396 Finished processing request in 0.00 seconds
2017-02-04T07:36:02Z [info] {176/67.193.90.246} Code=400 Bytes=28 Finished processing request in 0.00 seconds
2017-02-04T07:36:02Z [info] {177/67.193.90.246} Code=200 Bytes=408230 GET /h/cf5d5c57aff3b1a12d8f749b4092e43fb5d5ef5d-408230-1075-1500-jpg
2017-02-04T07:36:02Z [info] {177/67.193.90.246} Code=200 Bytes=408230 Finished processing request in 0.03 seconds (16329.20 KB/s)
2017-02-04T07:36:07Z [info] {178/99.238.225.122} Code=200 Bytes=183165 GET /h/a18602715cb00a643b65e4e8d2ca678188a05dc6-183165-800-1035-jpg/
2017-02-04T07:36:07Z [info] {178/99.238.225.122} Code=200 Bytes=183165 Finished processing request in 0.02 seconds (8722.14 KB/s)

The download itself seems fast but the actual image to download is not. The above does not show the time between actual downloads which is very slow as the download for the next image keeps stalling.

This post has been edited by molitar: Feb 4 2017, 09:38

H@H seems to be very slow since update. It takes forever to load gallery images with the new H@H 1.4.1. Image download just stalls.

2017-02-04T07:36:01Z [info] {175/70.55.76.130} Code=200 Bytes=173396 GET /h/a186246ab68e2bcc0cfebb875b710b0148fa7bb4-173396-1280-720-jpg/
2017-02-04T07:36:01Z [info] {175/70.55.76.130} Code=200 Bytes=173396 Finished processing request in 0.00 seconds
2017-02-04T07:36:02Z [info] {176/67.193.90.246} Code=400 Bytes=28 Finished processing request in 0.00 seconds
2017-02-04T07:36:02Z [info] {177/67.193.90.246} Code=200 Bytes=408230 GET /h/cf5d5c57aff3b1a12d8f749b4092e43fb5d5ef5d-408230-1075-1500-jpg
2017-02-04T07:36:02Z [info] {177/67.193.90.246} Code=200 Bytes=408230 Finished processing request in 0.03 seconds (16329.20 KB/s)
2017-02-04T07:36:07Z [info] {178/99.238.225.122} Code=200 Bytes=183165 GET /h/a18602715cb00a643b65e4e8d2ca678188a05dc6-183165-800-1035-jpg/
2017-02-04T07:36:07Z [info] {178/99.238.225.122} Code=200 Bytes=183165 Finished processing request in 0.02 seconds (8722.14 KB/s)

The download itself seems fast but the actual image to download is not. The above does not show the time between actual downloads which is very slow as the download for the next image keeps stalling.

seems like the client no longer loads images if ur using fire fox thats the problem

H@H seems to be very slow since update. It takes forever to load gallery images with the new H@H 1.4.1. Image download just stalls.

2017-02-04T07:36:01Z [info] {175/70.55.76.130} Code=200 Bytes=173396 GET /h/a186246ab68e2bcc0cfebb875b710b0148fa7bb4-173396-1280-720-jpg/
2017-02-04T07:36:01Z [info] {175/70.55.76.130} Code=200 Bytes=173396 Finished processing request in 0.00 seconds
2017-02-04T07:36:02Z [info] {176/67.193.90.246} Code=400 Bytes=28 Finished processing request in 0.00 seconds
2017-02-04T07:36:02Z [info] {177/67.193.90.246} Code=200 Bytes=408230 GET /h/cf5d5c57aff3b1a12d8f749b4092e43fb5d5ef5d-408230-1075-1500-jpg
2017-02-04T07:36:02Z [info] {177/67.193.90.246} Code=200 Bytes=408230 Finished processing request in 0.03 seconds (16329.20 KB/s)
2017-02-04T07:36:07Z [info] {178/99.238.225.122} Code=200 Bytes=183165 GET /h/a18602715cb00a643b65e4e8d2ca678188a05dc6-183165-800-1035-jpg/
2017-02-04T07:36:07Z [info] {178/99.238.225.122} Code=200 Bytes=183165 Finished processing request in 0.02 seconds (8722.14 KB/s)

The download itself seems fast but the actual image to download is not. The above does not show the time between actual downloads which is very slow as the download for the next image keeps stalling.

I'm not seeing anything unusual or slow with that log. If you are talking about downloads being slow for *you*, that's a problem with Firefox 51, not H@H.

1.4.1 already works around the brokenness of Firefox 51 by quickly telling it to sod off with invalid requests and request the file the proper way. It will still be slower than a working browser, but not by more than half a second or so. At this point, about 65% of clients have updated.