proxychains4 throws error where proxychains3 works without issue (related to dehydrated)

Hello everybody.

I tried to find some more issues about this online but failed. Sorry if it has been addressed already.

I found out about proxychains4 few days ago. So far I've been using the default proxychains deployment from Raspbian (Debian for Raspberry Pi) Buster, which is 3.1-8.1. I started working on some scripts in which I wanted to parse the responses from the proxified and direct connections in the same way so I realized that only proxychains4 actually has a -q switch to help me achieve that easily. I am currently running proxychains4 version 4.13-4.

Anyway, everything else works fine except one (important) thing.
Since this is running on Raspberry Pi constantly connected to the internet via VPN, I am using proxychains to renew my letsencrypt certificate via public IP assigned to me by my ISP (I am running SSH server on another device in my home network through which proxychains tunnels the request outside).
I use dehydrated (https://github.com/lukas2511/dehydrated) for letsencrypt renewal and it worked fine for more than a year via proxychains3 but when I try to use it via proxychains4 there is an error message.

root@raspberrypi:/opt/dehydrated # proxychains /opt/dehydrated/dehydrated -c
[proxychains] config file found: /etc/proxychains.conf
[proxychains] preloading /usr/lib/arm-linux-gnueabihf/libproxychains.so.4
[proxychains] DLL init: proxychains-ng 4.13
[proxychains] DLL init: proxychains-ng 4.13
[proxychains] DLL init: proxychains-ng 4.13
[proxychains] DLL init: proxychains-ng 4.13
INFO: Using main config file /opt/dehydrated/config
[proxychains] DLL init: proxychains-ng 4.13
[proxychains] DLL init: proxychains-ng 4.13
[proxychains] DLL init: proxychains-ng 4.13
[proxychains] DLL init: proxychains-ng 4.13
[proxychains] DLL init: proxychains-ng 4.13
[proxychains] DLL init: proxychains-ng 4.13
[proxychains] DLL init: proxychains-ng 4.13
[proxychains] DLL init: proxychains-ng 4.13
[proxychains] DLL init: proxychains-ng 4.13
[proxychains] DLL init: proxychains-ng 4.13
[proxychains] DLL init: proxychains-ng 4.13
[proxychains] DLL init: proxychains-ng 4.13
[proxychains] Strict chain ... 127.0.0.1:7072 ... acme-staging-v02.api.letsencrypt.org:443 ... OK
[proxychains] DLL init: proxychains-ng 4.13
bash: src/allocator_thread.c:235: getmessage: Assertion `hdr->datalen <= MSG_LEN_MAX' failed.
Aborted
[proxychains] DLL init: proxychains-ng 4.13

When I rerun dehydrated with proxychains3 or without proxychains, it works fully without any issues.

root@raspberrypi:/opt/dehydrated # /opt/dehydrated/dehydrated -c
INFO: Using main config file /opt/dehydrated/config
Unknown hook this_hookscript_is_broken__dehydrated_is_working_fine__please_ignore_unknown_hooks_in_your_script
Processing mydomain.com with alternative names: myotherdomain.com
Unknown hook this_hookscript_is_broken__dehydrated_is_working_fine__please_ignore_unknown_hooks_in_your_script

• Checking domain name(s) of existing cert... unchanged.
• Checking expire date of existing cert...
• Valid till Feb 16 04:41:41 2020 GMT Certificate will not expire
  (Longer than 30 days). Skipping renew!

I would greatly appreciate if someone could help with this.

Thanks in advance!

Reproduce the failure with proxychains4 running /opt/dehydrated/dehydrated -c and compare it with proxychains3 or a direct run. Start at src/allocator_thread.c:235, where the MSG_LEN_MAX assertion aborts, and trace the reported interaction with dehydrated. Done means the proxychains4 command completes without this assertion failure in the reported setup.