[X] My Assistant

Megabytes not megabits right? This will be harder to achieve in some regions.

FWIW North America has a lower average tested speed than Asia. And it's not because of Canada.

Just watched 5 of my H@H clients as they one by one decided to commit sudoku.
Took a peak at the logs to see what happened, and eh, looks like all 5 was kinda just told by the server to kindly un-alive themselves?

Snippets below are from 2 of them. Figured posting the same thing 5 times would be overkill.

CODE

2023-10-17T23:29:33Z [debug] Finished download for
http://94.100
in 0 ms, writeoff=46, successful=yes
2023-10-17T23:29:33Z [debug] Received response: OK
2023-10-17T23:29:33Z [debug] And when you're dead I will be still alive.
2023-10-17T23:29:33Z [debug] Successfully performed a stillAlive test
for the server.
2023-10-17T23:29:33Z [info] Shutting down...
2023-10-17T23:29:33Z [debug] Connecting to 94.100
2023-10-17T23:29:34Z [debug] Reading 199 bytes from
http://94.100
2023-10-17T23:29:34Z [debug] Finished download for
http://94.100
in 0 ms, writeoff=199, successful=yes
2023-10-17T23:29:34Z [debug] Received response: OK
2023-10-17T23:29:34Z [debug] The enrichment center is committed to the
well being of all participants. Cake, and grief counseling will be
available at the conclusion of the test. Thank you for helping us help
you help us all.
2023-10-17T23:29:34Z [debug] Shutdown notification successful.
2023-10-17T23:29:34Z [info] Shutdown in progress - please wait up to 30
seconds
2023-10-17T23:29:39Z [info] Good-night
2023-10-17T23:29:39Z [info] ServerSocket was closed and will no longer
accept new connections.
2023-10-17T23:29:39Z [debug] Writing cache object data/pcache_ages
2023-10-17T23:29:39Z [debug] Wrote cache object data/pcache_ages with
size=400 hash=
2023-10-17T23:29:39Z [debug] Writing cache object data/pcache_lru
2023-10-17T23:29:39Z [debug] Wrote cache object data/pcache_lru with
size=2097179 hash=
2023-10-17T23:29:39Z [info] Logging ended.

CODE

2023-10-17T23:33:22Z [debug] Connecting to 94.100
2023-10-17T23:33:23Z [debug] Reading 199 bytes from
http://94.100
2023-10-17T23:33:23Z [debug] Finished download for
http://94.100
in 0 ms, writeoff=199, successful=yes
2023-10-17T23:33:23Z [debug] Received response: OK
2023-10-17T23:33:23Z [debug] The enrichment center is committed to the
well being of all participants. Cake, and grief counseling will be
available at the conclusion of the test. Thank you for helping us help
you help us all.
2023-10-17T23:33:23Z [debug] Shutdown notification successful.
2023-10-17T23:33:23Z [info] Shutdown in progress - please wait up to 30
seconds
2023-10-17T23:33:28Z [info] ServerSocket was closed and will no longer
accept new connections.
2023-10-17T23:33:28Z [info] No hard feelings
2023-10-17T23:33:28Z [debug] Writing cache object data/pcache_ages
2023-10-17T23:33:28Z [debug] Wrote cache object data/pcache_ages with
size=358 hash=
2023-10-17T23:33:28Z [debug] Writing cache object data/pcache_lru
2023-10-17T23:33:28Z [debug] Wrote cache object data/pcache_lru with
size=2097179 hash=
2023-10-17T23:33:28Z [info] Logging ended.

This post has been edited by eboclove: Oct 18 2023, 03:14

Note that I added a missing condition for the HC ranges above:

- Must not have a monthly bandwidth limit set

Just watched 5 of my H@H clients as they one by one decided to commit sudoku.
Took a peak at the logs to see what happened, and eh, looks like all 5 was kinda just told by the server to kindly un-alive themselves?

You didn't specify a client ID or give any details about your setup so it's hard to give you an answer, but that server message in the first log is not the "kindly un-alive yourself" one, and I'm not seeing any record of those being sent to any client recently, so these shutdowns were initiated by the client or OS. But your logs cut off so I can't really see if there's anything leading up to it.

Your clients all seem to be restarting frequently, so I'm curious if you are using systemd or something similar to control them? If you so should check the logs of whatever you're using to look for initiated restarts and make it stop doing that. Another alternative is that your system ran out of RAM which triggered the OOM killer, which you'd find records of in the system log.

It happened again a bit later, turns out the ssh files on the vps servers were the cause.
Ssh config was set to kill connections with which explains why they died one by one.
Fixed it now.


As for the restarts, total amount of restarts, yeah been a fair amount. But as of yesterday (or rather now thanks to the ssh config) they should have 24/7 uptime.

Had some hardware issues plaguing my proxmox server, overlapping with upgrading and setting up a new network equipment.
Network is now upgraded and configured, and swapped out the parts causing issues with the server as well as made some upgrades to it's specs (had a faulty ram stick up until 2 days ago, now has twice the amount, and bad sticks removed)

Ssh config was set to kill connections with which explains why they died one by one.
Fixed it now.

If you're running it directly from a SSH command shell, you generally want to run it though something like screen (or nohup) to prevent the process from terminating if the SSH session ends.

If you're running it directly from a SSH command shell, you generally want to run it though something like screen (or nohup) to prevent the process from terminating if the SSH session ends.

Yeah, I'm aware, but since ssh config had ClientAliveInterval set stupid low, the process would have ended up being killed regardless.
For the current session i just left an ubuntu VM running on proxmox with SSH sessions open. Proxmox isn't getting shut down and leaving it running isn't enough to cause any noticeable downside in terms of resources.
(If it does lose connection again or I for some reason decide to take it down I'll swap back to screen again though)

So to obtain an HC range, do you need to have it as a P5 or above range first (need to be promoted from an assigned range), or you can just gain one from nothing?

Hello,

my client report a lot of this warning/error. Is my configuration wrong or are related to some network connectivity problem? My Id is 25673. Thanks

CODE

2023-10-18T13:20:00Z [debug] {74704/116.163.41.7}    The connection was interrupted or closed by the remote host.
2023-10-18T13:20:00Z [debug] Remote host terminated the handshake
2023-10-18T13:20:01Z [info] {74702/58.217.226.234}  Code=200 Bytes=81993    GET /h/d6ef11e0e4aa88f55c5f58a229f51c0321d6acd6-81993-1280-1919-jpg/keystamp=1697635500-92b28ecc88;fileindex=135207675;xres=1280/JK2_34.jpg HTTP/1.1
2023-10-18T13:20:01Z [info] {74702/58.217.226.234}  Code=200 Bytes=81993    Finished processing request in 0,01 seconds
2023-10-18T13:20:01Z [debug] Memory total=40960kB free=30160kB max=927744kB
2023-10-18T13:20:07Z [info] {74705/83.97.154.179}   Code=200 Bytes=126560   GET /h/7c9c0bacb692998085e08bae3845d5a9259d1b45-126560-1280-720-jpg/keystamp=1697635800-f220a772a6;fileindex=101967313;xres=1280/Without_Text_014.jpg HTTP/1.1
2023-10-18T13:20:07Z [info] {74705/83.97.154.179}   Code=200 Bytes=126560   Finished processing request in 0,01 seconds (12656,00 KB/s)
2023-10-18T13:20:11Z [debug] Memory total=40960kB free=30078kB max=927744kB
2023-10-18T13:20:13Z [debug] {74706/8.142.64.24}     The requested URL is invalid or not supported.
2023-10-18T13:20:13Z [debug] Response Written:
2023-10-18T13:20:13Z [debug] An error has occurred. (404)
2023-10-18T13:20:13Z [info] {74706/8.142.64.24}     Code=404 Bytes=28       HEAD / HTTP/1.1
2023-10-18T13:20:13Z [info] {74706/8.142.64.24}     Code=404 Bytes=28       Finished processing request in 0,00 seconds
2023-10-18T13:20:16Z [debug] {74707/8.142.64.24}     Invalid request type 'dist
2023-10-18T13:20:16Z [debug] Response Written:
2023-10-18T13:20:16Z [debug] An error has occurred. (404)
2023-10-18T13:20:16Z [info] {74707/8.142.64.24}     Code=404 Bytes=28       GET /dist/images/mask/guide/cn/step1.jpg HTTP/1.1
2023-10-18T13:20:16Z [info] {74707/8.142.64.24}     Code=404 Bytes=28       Finished processing request in 0,00 seconds
2023-10-18T13:20:18Z [debug] {74708/8.142.64.24}     The requested URL is invalid or not supported.
2023-10-18T13:20:18Z [debug] Response Written:
2023-10-18T13:20:18Z [debug] An error has occurred. (404)
2023-10-18T13:20:18Z [info] {74708/8.142.64.24}     Code=404 Bytes=28       GET / HTTP/1.1
2023-10-18T13:20:18Z [info] {74708/8.142.64.24}     Code=404 Bytes=28       Finished processing request in 0,00 seconds
2023-10-18T13:20:21Z [debug] Memory total=40960kB free=30124kB max=927744kB
2023-10-18T13:20:26Z [info] {74709/185.146.232.243} Code=200 Bytes=261719   GET /h/75e6f9a0d4ec7dab53965857cd8102d139f3fac0-261719-1280-1813-jpg/keystamp=1697635800-b4416a3696;fileindex=129039613;xres=1280/5.jpg HTTP/1.1
2023-10-18T13:20:26Z [info] {74709/185.146.232.243} Code=200 Bytes=261719   Finished processing request in 0,02 seconds (14539,94 KB/s)
2023-10-18T13:20:31Z [debug] Memory total=40960kB free=30142kB max=927744kB
2023-10-18T13:20:31Z [info] {74710/91.196.223.199}  Code=200 Bytes=100741   GET /h/9d3483c68ee4e5c9fef275097288e54f59f01e61-100741-1095-730-jpg/keystamp=1697635800-a95af7aaf9;fileindex=134945794;xres=org/69.jpg HTTP/1.1
2023-10-18T13:20:31Z [info] {74710/91.196.223.199}  Code=200 Bytes=100741   Finished processing request in 0,01 seconds
2023-10-18T13:20:33Z [debug] {74712/172.68.0.78}     The connection was interrupted or closed by the remote host.
2023-10-18T13:20:33Z [debug] Remote host terminated the handshake
2023-10-18T13:20:33Z [debug] {74713/162.158.234.8}   The connection was interrupted or closed by the remote host.
2023-10-18T13:20:33Z [debug] Remote host terminated the handshake
2023-10-18T13:20:33Z [debug] {74714/172.69.253.71}   The connection was interrupted or closed by the remote host.
2023-10-18T13:20:33Z [debug] Remote host terminated the handshake
2023-10-18T13:20:33Z [debug] {74715/172.71.201.89}   The connection was interrupted or closed by the remote host.
2023-10-18T13:20:33Z [debug] Remote host terminated the handshake
2023-10-18T13:20:33Z [debug] {74716/162.158.191.91}  The connection was interrupted or closed by the remote host.
2023-10-18T13:20:33Z [debug] Remote host terminated the handshake
2023-10-18T13:20:33Z [debug] {74717/172.68.0.78}     The connection was interrupted or closed by the remote host.
2023-10-18T13:20:33Z [debug] Remote host terminated the handshake
2023-10-18T13:20:33Z [debug] {74718/172.68.91.75}    The connection was interrupted or closed by the remote host.
2023-10-18T13:20:33Z [debug] Remote host terminated the handshake
2023-10-18T13:20:33Z [debug] {74719/172.69.253.71}   The connection was interrupted or closed by the remote host.
2023-10-18T13:20:33Z [debug] Remote host terminated the handshake
2023-10-18T13:20:33Z [debug] {74720/172.69.145.36}   The connection was interrupted or closed by the remote host.
2023-10-18T13:20:33Z [debug] Remote host terminated the handshake
2023-10-18T13:20:33Z [debug] {74721/162.158.234.8}   The connection was interrupted or closed by the remote host.
2023-10-18T13:20:33Z [debug] Remote host terminated the handshake
2023-10-18T13:20:33Z [debug] {74722/172.71.201.89}   The connection was interrupted or closed by the remote host.
2023-10-18T13:20:33Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74723/162.158.191.91}  The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74724/172.69.253.71}   The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74725/172.68.0.78}     The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74726/162.158.234.8}   The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74727/172.68.91.75}    The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74728/172.69.213.71}   The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74729/172.71.201.89}   The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74730/172.69.145.36}   The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74731/172.69.253.71}   The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74732/162.158.191.91}  The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74733/162.158.234.8}   The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74734/172.68.91.75}    The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74735/172.71.201.89}   The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74736/172.68.0.78}     The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74737/172.69.253.71}   The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74738/172.69.213.71}   The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74739/172.69.145.36}   The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74740/162.158.234.8}   The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74741/172.71.201.89}   The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74742/162.158.191.91}  The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74743/172.68.91.75}    The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74744/172.68.0.78}     The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74745/172.69.145.36}   The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74746/175.6.13.142}    The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74747/172.69.213.71}   The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74748/162.158.191.91}  The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74749/172.68.91.75}    The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74750/172.69.145.36}   The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74751/172.69.213.71}   The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:34Z [debug] {74752/175.6.13.142}    The connection was interrupted or closed by the remote host.
2023-10-18T13:20:34Z [debug] Remote host terminated the handshake
2023-10-18T13:20:35Z [debug] {74753/172.69.213.71}   The connection was interrupted or closed by the remote host.
2023-10-18T13:20:35Z [debug] Remote host terminated the handshake
2023-10-18T13:20:35Z [debug] {74754/175.6.13.142}    The connection was interrupted or closed by the remote host.
2023-10-18T13:20:35Z [debug] Remote host terminated the handshake
2023-10-18T13:20:35Z [debug] {74755/175.6.13.142}    The connection was interrupted or closed by the remote host.
2023-10-18T13:20:35Z [debug] Remote host terminated the handshake
2023-10-18T13:20:41Z [debug] Memory total=40960kB free=29711kB max=927744kB
2023-10-18T13:20:41Z [debug] {74711/91.196.223.199}  The connection was interrupted or closed by the remote host.
2023-10-18T13:20:41Z [debug] Read timed out
2023-10-18T13:20:50Z [info] {74756/193.160.100.86}  Code=200 Bytes=340274   GET /h/75e6d5e25e2a22f12f8cd93521914ba2595f319a-340274-1280-1862-jpg/keystamp=1697635800-0238a368be;fileindex=135210596;xres=1280/004.jpg HTTP/1.1
2023-10-18T13:20:50Z [info] {74756/193.160.100.86}  Code=200 Bytes=340274   Finished processing request in 0,05 seconds (6672,04 KB/s)
2023-10-18T13:20:51Z [debug] Memory total=40960kB free=29987kB max=927744kB
2023-10-18T13:20:51Z [info] {74757/45.58.174.98}    Code=200 Bytes=267006   GET /h/7c9ccfb0662cc68ae81b2e2767d16eabf96191a2-267006-961-1399-jpg/keystamp=1697635800-c1d93b3976;fileindex=78115213;xres=org/045.jpg HTTP/1.1
2023-10-18T13:20:51Z [info] {74757/45.58.174.98}    Code=200 Bytes=267006   Finished processing request in 0,02 seconds (14833,67 KB/s)
2023-10-18T13:20:56Z [info] {74758/188.104.16.58}   Code=200 Bytes=306455   GET /h/6a95bfd2d4ff61bcdf22cbf0a6dc1b61c8f82f2f-306455-888-1243-jpg/keystamp=1697635800-3dcc4ff637;fileindex=135156775;xres=2400/MAMA_028.jpg HTTP/1.1
2023-10-18T13:20:56Z [info] {74758/188.104.16.58}   Code=200 Bytes=306455   Finished processing request in 0,05 seconds (6520,32 KB/s)
2023-10-18T13:20:57Z [info] {74759/83.159.230.129}  Code=200 Bytes=642389   GET /h/15c3c7d74676d35ced2cb311db3184eff8764a3e-642389-1200-1669-png/keystamp=1697635800-591e77c3a6;fileindex=78410957;xres=org/011.png HTTP/1.1
2023-10-18T13:20:57Z [info] {74759/83.159.230.129}  Code=200 Bytes=642389   Finished processing request in 0,53 seconds (1221,27 KB/s)
2023-10-18T13:21:01Z [debug] Memory total=40960kB free=30118kB max=927744kB
2023-10-18T13:21:11Z [debug] Memory total=40960kB free=30162kB max=927744kB
2023-10-18T13:21:20Z [debug] {74760/172.69.173.69}   The connection was interrupted or closed by the remote host.
2023-10-18T13:21:20Z [debug] Remote host terminated the handshake
2023-10-18T13:21:21Z [debug] {74761/172.69.173.69}   The connection was interrupted or closed by the remote host.
2023-10-18T13:21:21Z [debug] Remote host terminated the handshake
2023-10-18T13:21:21Z [debug] {74762/172.68.203.76}   The connection was interrupted or closed by the remote host.

So to obtain an HC range, do you need to have it as a P5 or above range first (need to be promoted from an assigned range), or you can just gain one from nothing?

The range would need to have been assigned to the client previously. But similar to how priority ranges works, the score calculated for each client is divided by how many HC ranges it has already been assigned, so if two qualifying clients have the same base score and one has 50 ranges while the other has 5000, if you divided 100 HC ranges between them it would assign 50 to each.

my client report a lot of this warning/error. Is my configuration wrong or are related to some network connectivity problem? My Id is 25673. Thanks

All the errors are from the same couple of IP ranges, so presumably it's either someone running some form of vulnerability scan. If your trust/quality is fine then there's nothing wrong with the client.

anyone willing to write up a detailed SNI L4 reverse proxy setup? (IMG:[invalid] style_emoticons/default/ph34r.gif)

Will that be possible now? Last time that I investigate it there were post that say they have low trust with SNI. Unless H@H is primary server, meaning server that is selected if client does not use SNI.

The code that assigns HC ranges is now live. These won't do anything until I write to code to actually use them, which won't happen until the initial assignment has completed, which will take about a week. Note that the minimum disk space to qualify for these was reduced to 100 GB.

A new way of calculating quality is also live. Unlike the old code which blindly compared client fail rates to some region-dependent hardcoded variables, quality is now a dynamic measure of how well your client does compared to every other client in the same region. Put simply, if your client's estimated fail rate is the same as the average estimated fail rate of the region, it would result in a quality of 9000. If it's better than the average, it would get a quality of over 9000, and if it's worse it would get less. This should eliminate any fluctuation caused by regional internet disturbances, which we see on a regular basis.

To get a quality of 10000 the client would need to have less than half the fail rate compared to the average, so a lot of currently maxed clients will see quality drop somewhat. This does not affect anything.

The code that assigns HC ranges is now live. These won't do anything until I write to code to actually use them, which won't happen until the initial assignment has completed, which will take about a week.

Has the no. of HC ranges been included in the range counts output on our end yet?

Has the no. of HC ranges been included in the range counts output on our end yet?

No.

To get a quality of 10000 the client would need to have less than half the fail rate compared to the average, so a lot of currently maxed clients will see quality drop somewhat. This does not affect anything.

Should I worry if my quality just dropped 3,000 from max and still getting worse? (IMG:[invalid] style_emoticons/default/unsure.gif)

My id is 46505 btw. Checking the log, I'm also not seeing any errors...

This post has been edited by shirayuki_meow: Oct 21 2023, 07:24

Should I worry if my quality just dropped 3,000 from max and still getting worse? (IMG:[invalid] style_emoticons/default/unsure.gif)

My id is 46505 btw. Checking the log, I'm also not seeing any errors...

That client is pretty new and doesn't have that much traffic yet. You should avoid restarting it so often since each restart delays the assignment of new ranges, but otherwise it looks fine.

One more requirement was added for HC ranges:

- The max number of HC ranges for a client is limited to 1 per 1 GiB of reserved disk space.

(IMG:[s2.loli.net] https://s2.loli.net/2023/10/21/ujP6nUs7St3aEQC.jpg)
after a ddos wave of my server's datacenter

I decided to remove the port 443 requirement for the HC ranges. Of the clients that fulfilled the other requirements, only one third or so run on the default port, so it was looking a bit iffy capacity-wise.

There will likely be another addition in the not too distant future that *will* require port 443, so it's still recommended to change it if possible.

Any chance you can not implement the 443 requirement?
Some home ISP doesn't allow port 443/website hosting
And I run H@H with a server that's also hosting my personal website and the website takes up port 443 as well....

Is there a way to check the number of HC assigned to a client?